24 Jan, 2018
1 commit
27 Jun, 2017
1 commit
-
ROM stores the boot params information in a known location
and passes it to SPL. This information needs to be copied
very early during boot or else there is a chance of getting
corrupted by SPL. So move this boot device detection very early
during boot.Signed-off-by: Lokesh Vutla
22 May, 2017
1 commit
-
am335x supports various sysclk frequencies which can be determined
using sysboot pins. PLLs should be configures based on this
sysclk frequency. Add PLL configurations for all supported
frequencies.Signed-off-by: Lokesh Vutla
03 Mar, 2017
1 commit
-
Probe USB_DEV_GENERIC drivers during arch_misc_init(). This is required
in order for USB DM model based peripheral mode devices like DFU to work
in U-Boot.Signed-off-by: Vignesh R
16 Feb, 2017
1 commit
-
To keep a consistent MMC device mapping in SPL and in u-boot, let's
register the MMC controllers the same way in u-boot and in the SPL.
In terms of boot time, it doesn't hurt to register more controllers than
needed because the MMC device is initialized only prior being accessed for
the first time.
Having the same device mapping in SPL and u-boot allows us to use the
environment in SPL whatever the MMC boot device.Tested-by: Sekhar Nori
Signed-off-by: Jean-Jacques Hiblot
27 Jan, 2017
1 commit
-
commit ba7916c72f198506602287839a6445d0e96ade8d upstream.
Add usb ether gadget device with usb_ether_init() when
CONFIG_DM_ETH and CONFIG_USB_ETHER are defined.Signed-off-by: Mugunthan V N
Reviewed-by: Tom Rini
Signed-off-by: Grygorii Strashko
25 Jan, 2017
1 commit
-
commit 17fa032671f7981628fe16b30399638842a4b1bb upstream.
commit: 65f83802b7a5b "serial: 16550: Add getfcr accessor"
breaks u-boot commandline working with long commands
sending to the board.Since the above patch, you have to setup the fcr register.
For board/archs which enable OF_PLATDATA, the new field
fcr in struct ns16550_platdata is not filled with a
default value ...This leads in not setting up the uarts fifo, which ends
in problems, when you send long commands to u-boots
commandline.Detected this issue with automated tbot tests on am335x
based shc board.The error does not popup, if you type commands. You need
to copy&paste a long command to u-boots commandshell
(or send a long command with tbot)Possible boards/plattforms with problems:
./arch/arm/cpu/arm926ejs/lpc32xx/devices.c
./arch/arm/mach-tegra/board.c
./board/overo/overo.c
./board/quipos/cairo/cairo.c
./board/logicpd/omap3som/omap3logic.c
./board/logicpd/zoom1/zoom1.c
./board/timll/devkit8000/devkit8000.c
./board/lg/sniper/sniper.c
./board/ti/beagle/beagle.c
./drivers/serial/serial_rockchip.cSigned-off-by: Heiko Schocher
Signed-off-by: Ladislav Michl
Tested-by: Adam Ford
Reviewed-by: Tom Rini
Signed-off-by: Lokesh Vutla
18 Jan, 2017
2 commits
-
Changes since v1:
- Adding register mappings for prm_device_inst.
- Added macro for DEVOFF bit.
- Expanding on comments explaining why this is necessary.This inhibits the re-inititialization of DDR during an RTC-only resume. If
this is not done, an L3 NOC error is produced as the DDR gets accessed
before the re-init has time to complete. Tested on AM437x GP EVM.Signed-off-by: Russ Dill
Tested-by: Dave Gerlach
[j-keerthy@ti.com Ported to 2017.01 branch]
Signed-off-by: Keerthy -
Kernel stores information to the RTC_SCRATCH0 and RTC_SCRATCH1 registers
for wakeup from RTC-only mode. Parse these registers during SPL boot and
jump to the kernel resume vector if the device is waking up from RTC-only
mode.The RTC scratch register layout used is:
SCRATCH0 : bits00-31 : kernel resume address
SCRATCH1 : bits00-15 : RTC magic value used to detect valid config
SCRATCH1 : bits16-31 : board type information populated by bootloaderDuring the normal boot patch the SCRATCH1 : bits16-31 are updated with
the eeprom read board type data. In the rtc_only boot path the rtc
scratchpad register is read and the board type is determined and
correspondingly ddr dpll parameters are set. This is done so as to avoid
costly i2c read to eeprom.RTC-only mode support is currently only enabled for
am43xx_evm_rtconly_config.
This is not to be used with epos evm builds.Tested-by: Dave Gerlach
Signed-off-by: Tero Kristo
[j-keerthy@ti.com Ported to 2017.01 branch]
Signed-off-by: Keerthy
11 Jan, 2017
1 commit
-
Declare the size of ddr very early in spl, so that this can be
used to enable cache.Signed-off-by: Lokesh Vutla
03 Dec, 2016
3 commits
-
Currently all backend driver ops uses hard coded physical
address, so to adopt the driver to DM, add device pointer to ops
call backs so that drivers can get physical addresses from the
usb driver priv/plat data.Signed-off-by: Mugunthan V N
Reviewed-by: Tom Rini -
MUSB wrapper driver is bound as MISC device and underlying usb
devices are bind to usb drivers based on dr_mode, so probing the
MISC wrapper driver to register musb devices.Signed-off-by: Mugunthan V N
Reviewed-by: Tom Rini -
Do not register usb devices when CONFIG_DM_USB is define.
Signed-off-by: Mugunthan V N
Reviewed-by: Tom Rini
22 Nov, 2016
1 commit
-
This moves what was in arch/arm/cpu/armv7/omap-common in to
arch/arm/mach-omap2 and moves
arch/arm/cpu/armv7/{am33xx,omap3,omap4,omap5} in to arch/arm/mach-omap2
as subdirectories. All refernces to the former locations are updated to
the current locations. For the logic to decide what our outputs are,
consolidate the tests into a single config.mk rather than including 4.Signed-off-by: Tom Rini
