diff options
author | Tony Lindgren <tony@atomide.com> | 2014-11-04 03:48:16 +0300 |
---|---|---|
committer | Tony Lindgren <tony@atomide.com> | 2014-11-04 03:48:16 +0300 |
commit | 13aec8e419ac1b02610fd7d550121bf286a3cf24 (patch) | |
tree | bd8a5b9aaa062f3e6fdaf643d07005e7d5c5ce6d /arch/arm/boot/dts/omap3-igep0020.dts | |
parent | b5399ea8453ac1ffe5c1515ba63afc978e242e7f (diff) | |
download | linux-13aec8e419ac1b02610fd7d550121bf286a3cf24.tar.xz |
ARM: dts: Use better omap GPMC timings for LAN9220
With the GPMC warnings now enabled, I noticed the LAN9220 timings
can overflow the GPMC registers with 200MHz L3 speed. Earlier we
were just skipping the bad timings and would continue with the
bootloader timings. Now we no longer allow to continue with bad
timings as we have the timings in the .dts files.
We could start using the GPMC clock divider, but let's instead
use the u-boot timings that are known to be working and a bit
faster. These are basically the u-boot NET_GPMC_CONFIG[1-6]
defines deciphered. Except that we don't set gpmc,burst-length
as that's only partially configured and does not seem to work
if fully enabled.
[tony@atomide.com: updated to remove gpmc,burst-length]
Signed-off-by: Tony Lindgren <tony@atomide.com>
Diffstat (limited to 'arch/arm/boot/dts/omap3-igep0020.dts')
0 files changed, 0 insertions, 0 deletions