Skip to content
  1. Oct 16, 2015
    • 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
  2. Oct 14, 2015
  3. Oct 12, 2015
  4. Sep 24, 2015
  5. Sep 17, 2015
    • Roger Quadros's avatar
      ARM: dts: am57xx-beagle-x15: use palmas-usb for USB2 · 84ad1bab
      Roger Quadros authored
      
      
      The VBUS line of USB2 is connected to VBUS detect logic on
      the PMIC. Use the palmas-usb driver to report VBUS events
      to the USB driver.
      
      As the palmas-usb driver supports GPIO based ID reporting
      provide the GPIO for ID pin as well.
      
      Signed-off-by: default avatarRoger Quadros <rogerq@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      84ad1bab
    • Grazvydas Ignotas's avatar
      ARM: dts: omap5-uevm.dts: fix i2c5 pinctrl offsets · 1dbdad75
      Grazvydas Ignotas authored
      
      
      The i2c5 pinctrl offsets are wrong. If the bootloader doesn't set the
      pins up, communication with tca6424a doesn't work (controller timeouts)
      and it is not possible to enable HDMI.
      
      Fixes: 9be495c4 ("ARM: dts: omap5-evm: Add I2c pinctrl data")
      Signed-off-by: default avatarGrazvydas Ignotas <notasas@gmail.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      1dbdad75
    • Nishanth Menon's avatar
      ARM: dts: am57xx-beagle-x15: Update Phy supplies · 5005296e
      Nishanth Menon authored
      
      
      Originally, all the SoC PHY rails were supplied by LDO3. However, as a
      result of characterization, it was determined that this posed a risk in
      extreme load  conditions. Hence the PHY rails are split between two
      different LDOs. Update the related node as a result
      
      LDO3/VDDA_1V8_PHYA supplies vdda_usb1, vdda_usb2, vdda_sata, vdda_usb3
      LDO4/VDDA_1V8_PHYB supplies vdda_pcie1, vdda_pcie0, vdda_hdmi, vdda_pcie
      
      NOTE: We break compatibility with pre-production boards with this change
      since, the PMIC LDO4 is disabled at OTP level.
      
      The new configuration is the plan of record and all pre-production
      boards are supposed to be replaced with the latest boards matching the
      mentioned configuration.
      
      Some very few 10 something boards have been created and
      stopped production till the latest modifications were done (PMIC USB
      interrupt, LDO4 etc) - and all of those boards are now getting
      scrapped.. If there are any (as per tracking information, there should
      not be any), TI should be contacted to have them replaced.
      
      Signed-off-by: default avatarNishanth Menon <nm@ti.com>
      [tony@atomide.com: updated commit about these being TI internal protos]
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      5005296e
Loading