u-boot.git/board/armltd, branch v2012.04

ARMV7/Vexpress: add missing get_ticks() and get_tbclk()

2012-03-26T11:22:40Z

commit f31a911fe (arm, post: add missing post_time_ms for arm) enables get_ticks and get_tbclk for all arm based boards, arm/vexpress also needs these functions to work. Signed-off-by: Liming Wang Acked-by: Matt.Waddel@linaro.org

integrator: remove fragile delay loop from PCI code

2012-03-04T20:15:31Z

The reference implementation of the PCI initialization code almost everywhere contain this fragile loop of "a few usecs", and its use of volatile variables to delay a number of bus cycles is indeed uncertain. Reading the manual "Integrator/AP Users Guide", page 5-15 it is clearly stated: "Wait until 230ms after the end of the reset period before accessing V360EPC internal registers. The V360EPC supports the use of a serial configuration PROM and the software must wait for the device to detect the absence of this PROM before accessing any registers. The required delay is a function of the PCI Clock, but at the lower frequency (25MHz) is 230ms". So let's simply wait 230ms per the spec. This solves the compilation error that looked like this: pci.c: In function ‘pci_init_board’: pci.c:286:18: warning: variable ‘j’ set but not used Reported-by: Wolfgang Denk Signed-off-by: Linus Walleij

integrator: rewrite the AP PCI driver

2012-02-27T20:19:24Z

The PCI support for the Integrator AP has apparently never been finished and I strongly suspect that it has never worked, so let's fix it. This is a list of the more or less un-splittable changes done in this driver rewrite: - Replace the register definitions stashed into the config file (!) with a copy if the register file from the Linux kernels arch/arm/include/asm/hardware/pci_v3.h - Delete the unreadable gigantic macros that perform the config accesses and replace them with copyedited code from Linux arch/arm/mach-integrator/pci_v3.c - Rewrite the rest of the setup code to use the v3_[read|write][lwb]() accessors. - Enable PCI by default in the AP board configuration. - Fix checkpatch warnings and make code more conformant. Tested-by: Will Deacon Signed-off-by: Linus Walleij

integrator: stop calling pci_init() twice

2012-02-27T20:19:24Z

The U-Boot startup infrastructure already makes sure pci_init() is called at a proper time, calling it again from within the board setup code will not make things better. Signed-off-by: Linus Walleij

integrator: enable Vpp and disable flash protection

2011-11-10T14:27:22Z

This enables Vpp and disables the flash protection on the Integrator when starting U-Boot. The integrator/AP has double protection mechanisms: this one and the EBI protection bit (patch earlier), the Integrator/CP has only one line of protection in these registers. Signed-off-by: Linus Walleij

integrator: add system controller header

2011-11-10T14:27:18Z

Break out the AP system controller and CP "CP controller" registers into a header file, it gives better overview than hardcoding its values and other disturbing practices. Signed-off-by: Linus Walleij

integrator: make flash writeable on boot

2011-11-10T14:27:15Z

This reconfigures the EBI (External Bus Interface) on the integrator so that chip select 1, handling the flash memory, is set to writeable. Without this it is not possible for U-Boot to access flash memory and it crashes on startup since CFI won't work properly. Since this is the first time we use the EBI, we create a header file for its registers. Signed-off-by: Linus Walleij

integrator: use io-accessors for board init

2011-11-10T14:27:03Z

Casting around to *(volatile ulong *) doesn't look good, so include the macros and use good old readl() instead. Signed-off-by: Linus Walleij

integrator: move text offset to config

2011-11-10T14:26:58Z

Do away with the config.mk file and move the text offset to the config files to make things easier. Signed-off-by: Linus Walleij

integrator: do not test first part of the memory

2011-11-08T21:04:47Z

When booting from Flash, the Integrator remaps its flash memory from 0x24000000 to 0x00000000, and starts executing it at 0x00000000. This ROM thus hides the RAM underneath and first 0x40000 bytes of the memory cannot be tested by get_ram_size(). So let's test from 0x40000 to the end of detected memory instead. Signed-off-by: Linus Walleij