08 May, 2017
7 commits
-
Add CONFIG_USB_STORAGE to the defconfig file.
Signed-off-by: Uri Mashiach
Reviewed-by: Tom Rini -
USB bus scan attempt:
----------------------------------cut----------------------------------
=> usb start
starting USB...
USB0: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... data abort
pc : [] lr : []
reloc pc : [] lr : []
sp : fdf42930 ip : fdf42960 fp : 00000000
r10: 00000001 r9 : fdf42ef0 r8 : 48890020
r7 : 00000002 r6 : fffa5840 r5 : fff8b140 r4 : fdf429c0
r3 : 00000000 r2 : 00000004 r1 : 00000000 r0 : 00000000
Flags: nZcv IRQs off FIQs off Mode SVC_32
Resetting CPU ...resetting ...
----------------------------------cut----------------------------------Fix by enabling USB configuration in the SPL.
Signed-off-by: Uri Mashiach
Reviewed-by: Tom Rini
Reviewed-by: Igor Grinberg -
Invoke enable_usb_clocks during board_usb_init and disable_usb_clocks
during board_usb_exit to enable and disable clocks respectively.Modifications:
* Enable USB clocks in the OMAP version of the function
board_usb_init.
* Disable USB clocks in the OMAP version of the function
board_usb_cleanup.Cc: Marek Vasut
Signed-off-by: Uri Mashiach
Reviewed-by: Marek Vasut
Reviewed-by: Tom Rini -
A weak version of the function board_usb_init is implemented in:
common/usb.c
drivers/usb/host/xhci-omap.cTo fix the double implementations:
* Convert the board_usb_init function in drivers/usb/host/xhci-omap.c
normal (not weak).
* The function board_usb_init in drivers/usb/host/xhci-omap.c calls to
the weak function omap_xhci_board_usb_init.
* Rename board version of the function board_usb_init to
omap_xhci_board_usb_init.
Done only for boards that defines CONFIG_USB_XHCI_OMAP.To achieve the same flexibility with the function board_usb_cleanup:
* Add a normal (not weak) implementation of the function
board_usb_cleanup in drivers/usb/host/xhci-omap.c
* The function board_usb_cleanup in drivers/usb/host/xhci-omap.c calls
to the weak function omap_xhci_board_usb_cleanup.
* Rename board version of the function board_usb_cleanup to
omap_xhci_board_usb_cleanup.
Done only for boards that defines CONFIG_USB_XHCI_OMAP.Cc: Lokesh Vutla
Signed-off-by: Uri Mashiach
Acked-by: Marek Vasut
Reviewed-by: Tom Rini
Reviewed-by: Roger Quadros -
Modify the determination of the base address of xHCI registers of DRA7XX
targets.
Before the commit: by the target.
After the commit: by the USB port index.Cc: Lokesh Vutla
Cc: Marek Vasut
Cc: Roger Quadros
Signed-off-by: Uri Mashiach
Reviewed-by: Marek Vasut
Reviewed-by: Tom Rini
Reviewed-by: Roger Quadros
Acked-by: Marek Vasut
Acked-by: Marek Vasut -
The symbol CONFIG_DRA7XX is needed for Kconfig conditions.
Cc: Lokesh Vutla
Signed-off-by: Uri Mashiach
Reviewed-by: Tom Rini -
Signed-off-by: Tom Rini
06 May, 2017
7 commits
-
The logical expression to check the dtb is incorrect in
load_devicetree.The problem was indicated by cppcheck.
The inconsistent variable name dtppart is changed to dtbpart.
Signed-off-by: Heinrich Schuchardt
Reviewed-by: Hannes Schmelzer
Acked-by: Hannes Schmelzer -
The evaluation of option -c is incorrect:
According to the C99 standard endptr in the first strtol is always
set as &endptr is not NULL.
So the first part of the or condition is always true.
If all digits in optarg are valid endptr will point to the closing \0
and the second strtol will read beyond the end of the string optarg
points to.Signed-off-by: Heinrich Schuchardt
Acked-by: Boris Brezillon -
va_start must always be matched by va_end.
The problem was indicated by cppcheck.
Signed-off-by: Heinrich Schuchardt
-
We should not first dereference p and afterwards assert that is
was not NULL. Instead do the assert first.The problem was indicated by cppcheck.
Signed-off-by: Heinrich Schuchardt
-
In dram_init_banksize there seems to be a typo concerning
a plausibility check of the fdt.
Testing sc > 2 twice does not make any sense.The problem was indicated by cppcheck.
Signed-off-by: Heinrich Schuchardt
-
A feature rich Linux kernel needs more than 8 MiB.
Hence enlarge CONFIG_SYS_BOOTM_LEN to 64 MiB for the GXBB systems.
As all known GXBB systems have at least 512 MiB of RAM this poses no problem.Cc: Andreas Färber
Signed-off-by: Heinrich Schuchardt
03 May, 2017
3 commits
-
.probe method has been assigned twice when declaring
a driver with U_BOOT_DRIVER(). Removed one of them.
Here is the last commit which had the duplicate entry:
"spi: omap3: Convert to driver model"
(sha1: 77b8d04854f486741471ad02b93b473b5b3d72f8)Signed-off-by: Suniel Mahesh
Reviewed-by: Jagan Teki -
This is not currently implemented. Add support for this so that the
Chrome OS EC can be used reliably.Signed-off-by: Moritz Fischer
Acked-by: Simon Glass
Reviewed-by: Jagan Teki -
Before using the cs_gpio, check if the GPIO is valid or not.
Signed-off-by: Wenyou Yang
Reviewed-by: Jagan Teki
02 May, 2017
3 commits
-
Signed-off-by: Tom Rini
-
Mention eMMC and microSD as supported devices.
They have been enabled with patch
d0c5c8d529f16fa88ab52a3b5dd2d4fc03664f19
odroid-c2: enable new Meson GX MMC driver in board defconfig
which was accepted for u-boot-mmc.git.Signed-off-by: Heinrich Schuchardt
-
0x10000000 is the start of a 2 MiB area used by the
ARM Trusted Firmware (BL31).See
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/tree/arch/arm64/boot/dts/amlogic/meson-gx.dtsi?id=refs/tags/v4.10.10So we should not load the ramdisk here.
The legacy Ubuntu image for the Odroid C2 comes with the
following line in boot.ini:
setenv initrd_loadaddr "0x13000000"See
http://odroid.in/ubuntu_16.04lts/ubuntu64-16.04-minimal-odroid-c2-20160815.img.xz
http://deb.odroid.in/c2/pool/main/u/u-boot/u-boot_20170226-752a100-8_arm64.debSo let's use the same address.
With the patch booting Linux with booti succeeds on an Odroid C2,
without the patch Linux hangs.Cc: Andreas Färber
Signed-off-by: Heinrich Schuchardt
Reviewed-by: Simon Glass
Tested-by: Vagrant Cascadian
01 May, 2017
20 commits
-
To enable automatic booting from SD card or eMMC the MMC
devices 0, 1, and 2 are added to the BOOT_TARGET_DEVICES.Booting from SD card, eMMC, and DHCP are tried in sequence.
A missing or failing device is gracefully handled.Cc: Andreas Färber
Signed-off-by: Heinrich Schuchardt
Tested-by: Vagrant Cascadian
Reviewed-by: Andreas Färber
Tested-by: Andreas Färber -
Signed-off-by: Tom Rini
-
Signed-off-by: Tom Rini
-
Add warp7_secure_defconfig entry to avoid the following warning:
WARNING: no maintainers for 'warp7_secure'
Signed-off-by: Fabio Estevam
-
With 3f66149d9fb4 we no longer have a common call fdt_fixup_ethernet.
This was fine to do on PowerPC as they largely had calls already in
ft_cpu_fixup. On ARM however we largely relied on this call. Rather
than introduce a large number of changes to ft_cpu_fixup /
ft_board_fixup we recognize that this is a common enough call that we
should be doing it in a central location. Do it early enough that we
can do any further updates in ft_cpu_fixup / ft_board_fixup.Cc: Gerd Hoffmann
Cc: Chen-Yu Tsai
Cc: Maxime Ripard
Cc: Thomas Chou (maintainer:NIOS)
Cc: York Sun (maintainer:POWERPC MPC85XX)
Cc: Stefan Roese (maintainer:POWERPC PPC4XX)
Cc: Simon Glass
Cc: Joakim Tjernlund
Fixes: 3f66149d9fb4 ("Remove extra fdt_fixup_ethernet() call")
Signed-off-by: Tom Rini
Acked-by: Stefan Roese
Acked-by: York Sun
Reviewed-by: Simon Glass -
Signed-off-by: Chris Packham
[trini: default y if DM_RTC, re-sync]
Signed-off-by: Tom Rini -
This is not used in U-Boot.
Signed-off-by: Simon Glass
-
This is not used in U-Boot. Drop it.
Signed-off-by: Simon Glass
-
This converts the following to Kconfig:
CONFIG_CMD_DISPLAYSigned-off-by: Simon Glass
-
This converts the following to Kconfig:
CONFIG_CMD_DIAGSigned-off-by: Simon Glass
[trini: imply CMD_DIAG on some keymile configs]
Signed-off-by: Tom Rini -
This option is not used in U-Boot. Drop it.
Signed-off-by: Simon Glass
-
This converts the following to Kconfig:
CONFIG_CMD_DEKBLOBNote: This option does not seem to actually be enabled by any board.
Signed-off-by: Simon Glass
[trini: imply under SECURE_BOOT for mx5/6/7]
Signed-off-by: Tom Rini -
This option does not exist in U-Boot. Drop it.
Signed-off-by: Simon Glass
-
Rather than using CMD_CRAMFS for both the filesystem and its command, we
should have a separate option for each. This allows us to enable CRAMFS
support without the command, if desired, which reduces U-Boot's size
slightly.Signed-off-by: Simon Glass
[trini: imply FS_CRAMFS for keymile]
Signed-off-by: Tom Rini -
This converts the following to Kconfig:
CONFIG_CMD_CRAMFSSigned-off-by: Simon Glass
[trini: imply CMD_CRAMFS for keymile]
Signed-off-by: Tom Rini -
This converts the following to Kconfig:
CONFIG_CMD_CLKSigned-off-by: Simon Glass
[trini: imply CMD_CLK on ARCH_ZYNQ]
Signed-off-by: Tom Rini -
This option is not used in U-Boot. Drop it.
Signed-off-by: Simon Glass
-
This converts the following to Kconfig:
CONFIG_CMD_CHIP_CONFIGSigned-off-by: Simon Glass
-
Rather than using CMD_CBFS for both the filesystem and its command, we
should have a separate option for each. This allows us to enable CBFS
support without the command, if desired, which reduces U-Boot's size
slightly.Signed-off-by: Simon Glass
[trini: imply FS_CBFS on SYS_COREBOOT]
Signed-off-by: Tom Rini -
This converts the following to Kconfig:
CONFIG_CMD_CBFSSigned-off-by: Simon Glass
[trini: imply CMD_CBFS on SYS_COREBOOT]
Signed-off-by: Tom Rini
