1. 19 10月, 2018 1 次提交
  2. 21 9月, 2018 1 次提交
  3. 03 7月, 2018 1 次提交
    • T
      ARM: dts: Improve omap l4per idling with wlcore edge sensitive interrupt · 572cf7d7
      Tony Lindgren 提交于
      The wl1835mod.pdf data sheet says this pretty clearly for WL_IRQ line:
      
      "WLAN SDIO out-of-band interrupt line. Set to rising edge (active high)
      by default."
      
      And it seems this interrupt can be optionally configured to use falling
      edge too since commit bd763482 ("wl18xx: wlan_irq: support platform
      dependent interrupt types").
      
      On omap4, if the wlcore interrupt is configured as level instead of edge,
      L4PER will stop doing hardware based idling after ifconfig wlan0 down is
      done and the WL_EN line is pulled down.
      
      The symptoms show up with L4PER status registers no longer showing the
      IDLEST bits as 2 but as 0 for all the active GPIO banks and for
      L4PER_CLKCTRL. Also the l4per_pwrdm RET count stops increasing in
      the /sys/kernel/debug/pm_debug/count.
      
      While there is also probably a GPIO related issue that needs to be
      still fixed, this change gets us to the point where we can have L4PER
      idling.
      
      I'm guessing wlcore was at some point configured to use level interrupts
      because of edge handling issues in gpio-omap. However, with the recent
      fixes to gpio-omap the edge interrupts seem to be working just fine.
      
      Let's change it for all omap boards with wlcore interrupt set as level.
      
      Cc: Dave Gerlach <d-gerlach@ti.com>
      Cc: Eyal Reizer <eyalr@ti.com>
      Cc: Grygorii Strashko <grygorii.strashko@ti.com>
      Cc: Kalle Valo <kvalo@codeaurora.org>
      Cc: Nishanth Menon <nm@ti.com>
      Cc: Tero Kristo <t-kristo@ti.com>
      [tony@atomide.com updated comments a bit for gpio issue]
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      572cf7d7
  4. 01 5月, 2018 1 次提交
  5. 12 12月, 2017 1 次提交
  6. 15 8月, 2017 1 次提交
    • F
      ARM: dts: am335x-evm: Enable NAND dma prefetch by default · 7d8fec20
      Franklin S Cooper Jr 提交于
      Currently the default method of prefetch polled shows the highest
      possible read and write speed when minimal non NAND background
      activity is being done. But it is also very CPU intensive to reach
      these high speeds (CPU load of 99% via mtd performance tests). While
      DMA prefetch only uses 50% of the CPU to achieve around 23% less in
      top read and write performance.
      
      However, as the non NAND CPU load increases the read and write
      performance takes a large hit when using polled prefetch. Therefore,
      prefetch dma mode ends up outperforming prefetch polled in general
      "system level" test. So switch to using dma prefetch by default since
      it is likely what most users would prefer.
      Signed-off-by: NFranklin S Cooper Jr <fcooper@ti.com>
      Acked-by: NRoger Quadros <rogerq@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      7d8fec20
  7. 21 1月, 2017 1 次提交
  8. 10 11月, 2016 1 次提交
  9. 20 9月, 2016 1 次提交
  10. 31 8月, 2016 1 次提交
  11. 16 8月, 2016 3 次提交
  12. 10 6月, 2016 1 次提交
  13. 13 4月, 2016 1 次提交
    • R
      ARM: dts: am335x: Provide NAND ready pin · 63015d73
      Roger Quadros 提交于
      On these boards NAND ready pin status is avilable over
      GPMC_WAIT0 pin.
      
      For NAND we don't use GPMC wait pin monitoring but
      get the NAND Ready/Busy# status using GPIOlib.
      GPMC driver provides the WAIT0 pin status over GPIOlib.
      
      Read speed increases from 7869 KiB/ to 8875 KiB/s
      and write speed was unchanged at 5100 KiB/s.
      
      Measured using mtd_speedtest.ko on am335x-evm.
      
      Cc: Teresa Remmet <t.remmet@phytec.de>
      Cc: Ilya Ledvich <ilya@compulab.co.il>
      Cc: Yegor Yefremov <yegorslists@googlemail.com>
      Cc: Rostislav Lisovy <lisovy@gmail.com>
      Cc: Enric Balletbo i Serra <eballetbo@iseebcn.com>
      Signed-off-by: NRoger Quadros <rogerq@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      63015d73
  14. 27 2月, 2016 2 次提交
    • R
      ARM: dts: am335x: Disable wait pin monitoring for NAND · db0f6852
      Roger Quadros 提交于
      The NAND Ready/Busy# line is connected to GPMC_WAIT0 pin and
      can't be used for wait state insertion for NAND I/O read/write.
      So disable read/write wait monitoring as per Reference Manual's
      suggestion [1].
      
      [1] AM335x TRM: SPRUH73L: 7.1.3.3.12.2 NAND Device-Ready Pin
      
      Cc: Teresa Remmet <t.remmet@phytec.de>
      Cc: Ilya Ledvich <ilya@compulab.co.il>
      Cc: Yegor Yefremov <yegorslists@googlemail.com>
      Cc: Rostislav Lisovy <lisovy@gmail.com>
      Cc: Enric Balletbo i Serra <eballetbo@iseebcn.com>
      Signed-off-by: NRoger Quadros <rogerq@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      db0f6852
    • R
      ARM: dts: am335x: Fix NAND device nodes · 03752148
      Roger Quadros 提交于
      Add compatible id, GPMC register resource and interrupt
      resource to NAND controller nodes.
      
      The GPMC node will provide an interrupt controller for the
      NAND IRQs.
      
      Cc: Teresa Remmet <t.remmet@phytec.de>
      Cc: Ilya Ledvich <ilya@compulab.co.il>
      Cc: Yegor Yefremov <yegorslists@googlemail.com>
      Cc: Rostislav Lisovy <lisovy@gmail.com>
      Cc: Enric Balletbo i Serra <eballetbo@iseebcn.com>
      Signed-off-by: NRoger Quadros <rogerq@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      03752148
  15. 18 12月, 2015 2 次提交
  16. 01 12月, 2015 1 次提交
  17. 02 11月, 2015 1 次提交
  18. 27 10月, 2015 1 次提交
  19. 13 10月, 2015 1 次提交
  20. 14 7月, 2015 4 次提交
  21. 22 5月, 2015 1 次提交
  22. 21 5月, 2015 1 次提交
  23. 04 2月, 2015 1 次提交
  24. 24 11月, 2014 1 次提交
  25. 07 11月, 2014 1 次提交
  26. 30 10月, 2014 1 次提交
    • T
      ARM: dts: Fix wrong GPMC size mappings for omaps · e2c5eb78
      Tony Lindgren 提交于
      The GPMC binding is obviously very confusing as the values
      are all over the place. People seem to confuse the GPMC partition
      size for the chip select, and the device IO size within the GPMC
      partition easily.
      
      The ranges entry contains the GPMC partition size. And the
      reg entry contains the size of the IO registers of the
      device connected to the GPMC.
      
      Let's fix the issue according to the following table:
      
      Device          GPMC partition size     Device IO size
      connected       in the ranges entry     in the reg entry
      
      NAND            0x01000000 (16MB)       4
      16550           0x01000000 (16MB)       8
      smc91x          0x01000000 (16MB)       0xf
      smc911x         0x01000000 (16MB)       0xff
      OneNAND         0x01000000 (16MB)       0x20000 (128KB)
      16MB NOR        0x01000000 (16MB)       0x01000000 (16MB)
      32MB NOR        0x02000000 (32MB)       0x02000000 (32MB)
      64MB NOR        0x04000000 (64MB)       0x04000000 (64MB)
      128MB NOR       0x08000000 (128MB)      0x08000000 (128MB)
      256MB NOR       0x10000000 (256MB)      0x10000000 (256MB)
      
      Let's also add comments to the fixed entries while at it.
      Acked-by: NRoger Quadros <rogerq@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      e2c5eb78
  27. 07 7月, 2014 1 次提交
  28. 15 5月, 2014 1 次提交
  29. 14 5月, 2014 1 次提交
  30. 07 5月, 2014 1 次提交
  31. 19 4月, 2014 2 次提交
  32. 06 3月, 2014 1 次提交