1. 17 12月, 2018 1 次提交
  2. 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
  3. 12 12月, 2017 2 次提交
  4. 18 8月, 2017 1 次提交
  5. 16 5月, 2017 1 次提交
  6. 29 6月, 2016 1 次提交
  7. 27 2月, 2016 2 次提交
  8. 23 2月, 2016 1 次提交
  9. 13 2月, 2016 4 次提交
  10. 22 12月, 2015 1 次提交
  11. 18 12月, 2015 3 次提交
  12. 01 12月, 2015 3 次提交
  13. 19 10月, 2015 1 次提交
    • T
      ARM: OMAP2+: Fix imprecise external abort caused by bogus SRAM init · 57df5380
      Tony Lindgren 提交于
      Some omaps are producing imprecise external aborts because we are
      wrongly trying to init SRAM for device tree based booting. Only
      omap3 is still using the legacy SRAM code, so we need to make it
      omap3 specific. Otherwise we can get errors like this on at least
      dm814x:
      
      Unhandled fault: imprecise external abort (0xc06) at 0xc08b156c
      ...
      (omap_rev) from [<c08b12e0>] (omap_sram_init+0xf8/0x3e0)
      (omap_sram_init) from [<c08aca0c>] (omap_sdrc_init+0x10/0xb0)
      (omap_sdrc_init) from [<c08b581c>] (pdata_quirks_init+0x18/0x44)
      (pdata_quirks_init) from [<c08b5478>] (omap_generic_init+0x10/0x1c)
      (omap_generic_init) from [<c08a57e0>] (customize_machine+0x1c/0x40)
      (customize_machine) from [<c00098a4>] (do_one_initcall+0x80/0x1dc)
      (do_one_initcall) from [<c08a2ec4>] (kernel_init_freeable+0x218/0x2e8)
      (kernel_init_freeable) from [<c063a554>] (kernel_init+0x8/0xec)
      (kernel_init) from [<c000f890>] (ret_from_fork+0x14/0x24)
      
      Let's fix the issue by making sure omap_sdrc_init only gets called for
      omap3. To do that, we need to have compatible "ti,omap3" in the dts
      files. And let's also use "ti,omap3630" instead of "ti,omap36xx" like
      we're supposed to.
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      57df5380
  14. 21 5月, 2015 1 次提交
    • T
      ARM: dts: Add minimal support for LogicPD Torpedo DM3730 devkit · 687c2767
      Tony Lindgren 提交于
      The LogicPD Torpedo DM3730 devkit consists of a base board and
      two processor boards. One of the processor boards has a WLAN and
      the other one does not.
      
      Let's set up basic dts file so we can move to device tree only
      based booting over next few merge windows. So far I've tested
      that UARTs, MMC1, USB OTG, smsc911x, and basic PM support works.
      
      Note that the wireless support in kernel for wl1283 seems to be
      broken, it tries to load wl127x-nvs.bin instead of wl128x-nvs.bin
      with firmware.
      
      Cc: Tim Nordell <tim.nordell@logicpd.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      687c2767