1. 22 11月, 2014 6 次提交
  2. 12 11月, 2014 13 次提交
  3. 11 11月, 2014 18 次提交
  4. 04 11月, 2014 2 次提交
    • T
      ARM: dts: Fix missing GPMC NAND device width for omap3 boards · 24f284af
      Tony Lindgren 提交于
      Looks like we have some GPMC NAND timings missing device
      width. This fixes "gpmc_cs_program_settings: invalid width 0!"
      errors during boot.
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      24f284af
    • T
      ARM: dts: Use better omap GPMC timings for LAN9220 · 13aec8e4
      Tony Lindgren 提交于
      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: NTony Lindgren <tony@atomide.com>
      13aec8e4
  5. 30 10月, 2014 1 次提交
    • T
      ARM: dts: Add GPMC timings for omap zoom serial port · b5399ea8
      Tony Lindgren 提交于
      The four port serial port on the zoom debug board uses a TL16CP754C
      with a single interrupt and GPMC chip select. The serial ports each
      use a 8 bytes for IO registers, and are 256 bytes apart on the GPMC
      line.
      
      Let's add timings for all four ports so we can remove the GPMC
      workarounds for using bootloader timings.
      
      Not caused by this patch, but looks like u-boot only properly
      initializes the fifo on the first serial port. Currently the other
      ports produce garbage at least with my version of u-boot. I suspect
      that TL16CP754C needs non-standard initialization added to 8250
      driver to properly fix this issue.
      
      Cc: Roger Quadros <rogerq@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      b5399ea8