1. 19 6月, 2013 1 次提交
  2. 03 6月, 2013 1 次提交
  3. 09 4月, 2013 4 次提交
    • N
      ARM: dts: omap4-panda: move generic sections to panda-common · 4b79197c
      Nishanth Menon 提交于
      PandaBoard, PandaBoard-A4 revisions use OMAP4430.
      PandaBoard-ES version of the board uses OMAP4460.
      
      Move the original panda dts file into a common dtsi used by all panda
      variants. This allows us to introduce SoC variation for PandaBoard ES
      without impacting other PandaBoard versions that are supported.
      As part of this change, since OMAP4460 adds on to OMAP4430, add
      omap4.dtsi to omap4460.dtsi.
      Signed-off-by: NNishanth Menon <nm@ti.com>
      Cc: Kevin Hilman <khilman@deeprootsystems.com>
      Cc: Jon Hunter <jon-hunter@ti.com>
      Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
      Cc: Shawn Guo <shawn.guo@linaro.org>
      Cc: Keerthy <j-keerthy@ti.com>
      Signed-off-by: NBenoit Cousson <benoit.cousson@linaro.org>
      4b79197c
    • N
      ARM: dts: OMAP443x: Add CPU OPP table · e77049bb
      Nishanth Menon 提交于
      Add DT OPP table for OMAP443x family of devices. This data is
      decoded by OF with of_init_opp_table() helper function.
      
      OPP data here is based on existing opp4xxx_data.c
      
      Since the omap4460 OPP tables would be different from OMAP443x,
      introduce an new omap443x.dtsi for 443x specific entries and use
      existing omap4.dtsi as the common dtsi file for all OMAP4 platforms.
      
      This is in preparation to use generic cpufreq-cpu0 driver for device
      tree enabled boot. Legacy non device tree enabled boot continues to
      use omap-cpufreq.c and opp4xxx_data.c.
      Signed-off-by: NNishanth Menon <nm@ti.com>
      Cc: Kevin Hilman <khilman@deeprootsystems.com>
      Cc: Jon Hunter <jon-hunter@ti.com>
      Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
      Cc: Shawn Guo <shawn.guo@linaro.org>
      Cc: Keerthy <j-keerthy@ti.com>
      Signed-off-by: NBenoit Cousson <benoit.cousson@linaro.org>
      e77049bb
    • K
      ARM: dts: OMAP: Add usb_otg and glue data to OMAP3+ boards · ad871c10
      Kishon Vijay Abraham I 提交于
      Add usb otg data node in omap4/omap3 device tree file. Also update
      the node with board specific setting in omapx-<board>.dts file.
      The dt data specifies among others the interface type (ULPI or UTMI),
      mode which is mostly OTG, power that specifies the amount of power
      this can supply when in host mode.
      
      The information about usb otg node is available @
      Documentation/devicetree/bindings/usb/omap-usb.txt
      Signed-off-by: NKishon Vijay Abraham I <kishon@ti.com>
      Acked-by: NFelipe Balbi <balbi@ti.com>
      Signed-off-by: NBenoit Cousson <benoit.cousson@linaro.org>
      ad871c10
    • S
      ARM: dts: omap4-panda: Add I2c pinctrl data · adb9e561
      Sourav Poddar 提交于
      Booting 3.8-rc6 on omap4 panda results in the following error
      
      [    0.444427] omap_i2c 48070000.i2c: did not get pins for i2c error: -19
      [    0.445770] omap_i2c 48070000.i2c: bus 0 rev0.11 at 400 kHz
      [    0.473937] omap_i2c 48072000.i2c: did not get pins for i2c error: -19
      [    0.474670] omap_i2c 48072000.i2c: bus 1 rev0.11 at 400 kHz
      [    0.474822] omap_i2c 48060000.i2c: did not get pins for i2c error: -19
      [    0.476379] omap_i2c 48060000.i2c: bus 2 rev0.11 at 100 kHz
      [    0.477294] omap_i2c 48350000.i2c: did not get pins for i2c error: -19
      [    0.477996] omap_i2c 48350000.i2c: bus 3 rev0.11 at 400 kHz
      [    0.483398] Switching to clocksource 32k_counter
      
      This happens because omap4 panda dts file is not adapted to use i2c through
      pinctrl framework. Populating i2c pinctrl data to get rid of the error.
      
      Tested on omap4460 panda with 3.8-rc6 kernel.
      Signed-off-by: NSourav Poddar <sourav.poddar@ti.com>
      Reported-by: NLuciano Coelho <coelho@ti.com>
      Signed-off-by: NBenoit Cousson <benoit.cousson@linaro.org>
      adb9e561
  4. 07 11月, 2012 1 次提交
  5. 29 10月, 2012 1 次提交
  6. 09 10月, 2012 2 次提交
  7. 08 9月, 2012 1 次提交
  8. 09 7月, 2012 1 次提交
  9. 21 6月, 2012 1 次提交
  10. 15 5月, 2012 1 次提交
  11. 10 5月, 2012 1 次提交
  12. 15 3月, 2012 1 次提交
  13. 07 3月, 2012 1 次提交
  14. 14 12月, 2011 1 次提交
  15. 05 10月, 2011 1 次提交