1. 20 Oct, 2015 5 commits
  2. 16 Oct, 2015 3 commits
    • Tony Lindgren's avatar
      ARM: dts: Add basic support for isee igepv5 · 23c74bf5
      Tony Lindgren authored
      With omap5-board-common.dtsi, we can now easily add support for various omap5
      board variants. Let's add minimal support for isee igepv5.
      
      So far I've tested that basic things work, such as serial, USB Ethernet, HDMI
      and WLAN.
      
      Note that like omap5-uevm, these boards seem to need to reserve 16MB for a
      trap section as in commit 03178c66 ("ARM: dts: omap5-evm: Update
      available memory to 2032 MB") and also noted in a u-boot commit at
      http://marc.info/?l=u-boot&m=134376852603255 and also at
      http://patchwork.ozlabs.org/patch/159881/.
      
      Not sure why this is not needed for omap5-cm-t54.dts, maybe because of
      different u-boot configuration.
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      23c74bf5
    • Tony Lindgren's avatar
      ARM: dts: Move most of omap5-uevm.dts to omap5-board-common.dtsi · ee9a97db
      Tony Lindgren authored
      Looks like thevarious omap5-uevm models and igepv5 are very similar. So let's
      create omap5-board-common.dtsi to allow fixing up things properly for mainline
      kernel to support all these.
      
      Even if we eventually end up having only PMIC + MMC + eMMC + SDIO WLAN + SATA +
      USB + HDMI configuration in the omap5-board-common.dtsi, this is the easiest
      way to add support for other boards rather than diffing various versions of
      out of tree dts files.
      
      My guess is that also omap5-sbc-t54.dts can use this, but I don't have that
      board so that will need to be dealt with later on.
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      ee9a97db
    • Tony Lindgren's avatar
      ARM: dts: Fix WLAN regression on omap5-uevm · 0efc898a
      Tony Lindgren authored
      Commit 99f84cae ("ARM: dts: add wl12xx/wl18xx bindings") added
      device tree bindings for the TI WLAN SDIO on many omap variants.
      
      I recall wondering how come omap5-uevm did not have the WLAN
      added and this issue has been bugging me for a while now, and
      I finally tracked it down to a bad pinmux regression, and a missing
      deferred probe handling for the 32k clock from palmas that's
      requested by twl6040.
      
      Basically 392adaf7 ("ARM: dts: omap5-evm: Add mcspi data")
      added pin muxing for mcspi4 that conflicts with the onboard
      WLAN. While some omap5-uevm don't have WLAN populated, the
      pins are not reused for other devices. And as the SDIO bus
      should be probed, let's try to enable WLAN by default.
      
      Let's fix the regression and add the WLAN configuration as
      done for the other boards in 99f84cae ("ARM: dts: add
      wl12xx/wl18xx bindings"). And let's use the new MMC pwrseq for
      the 32k clock as suggested by Javier Martinez Canillas
      <javier@dowhile0.org>.
      
      Note that without a related deferred probe fix for twl6040,
      the 32k clock is not initialized if palmas-clk is a module
      and twl6040 is built-in.
      
      Let's also use the generic "non-removable" instead of the
      legacy "ti,non-removable" property while at it.
      
      And finally, note that omap5 seems to require WAKEUP_EN for
      the WLAN GPIO interrupt.
      
      Fixes: 392adaf7 ("ARM: dts: omap5-evm: Add mcspi data")
      Cc: Sourav Poddar <sourav.poddar@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      0efc898a
  3. 14 Oct, 2015 1 commit
  4. 12 Oct, 2015 31 commits