diff options
| author | Enric Balletbo i Serra <eballetbo@gmail.com> | 2014-01-25 22:52:22 +0100 |
|---|---|---|
| committer | Tom Rini <trini@ti.com> | 2014-03-06 11:21:37 -0500 |
| commit | dd1e8583ee533a349c03ed4d75446898fe8dbac6 (patch) | |
| tree | dd14fcfb0ee38e844acd3d2de123ebd8a9a39bcc /include/configs/mx6qarm2.h | |
| parent | 4b75fd510076f2261c5e21b9b8cf75c9f01ded3c (diff) | |
| download | talos-obmc-uboot-dd1e8583ee533a349c03ed4d75446898fe8dbac6.tar.gz talos-obmc-uboot-dd1e8583ee533a349c03ed4d75446898fe8dbac6.zip | |
OMAP3: igep00x0: Enable required clocks for GPIO that are used.
Enable required clocks for GPIO to fix a boot issue introduced by commit
f33b9bd3984fb11e1d8566a866adc5957b1e1c9d (arm: omap3: Enable clocks for
peripherals only if they are used).
Without this patch the u-boot freezes after the following messages
OMAP36XX/37XX-GP ES1.2, CPU-OPP2, L3-200MHz, Max CPU Clock 1 Ghz
IGEPv2 + LPDDR/NAND
I2C: ready
DRAM: 512 MiB
NAND: 512 MiB
MMC: OMAP SD/MMC: 0
Diving into the issue, the sequence that produces the u-boot freezes is
setup_net_chip
|--> gpio_direction_out
|--> _set_gpio_dataout
|--> __raw_writel
To avoid this we just need enable the clocks for GPIOs that are used, but it
would be interesting implement a mechanism to protect these situations and
make sure that the clock is enabled when we request a GPIO.
Signed-off-by: Enric Balletbo i Serra <eballetbo@gmail.com>
Diffstat (limited to 'include/configs/mx6qarm2.h')
0 files changed, 0 insertions, 0 deletions
