An error occurred fetching the project authors.
  1. 24 Feb, 2014 1 commit
  2. 30 Sep, 2013 1 commit
  3. 28 Aug, 2013 1 commit
  4. 12 Jun, 2013 2 commits
    • Tomi Valkeinen's avatar
      ARM: OMAP: add vdds_dsi supply for omapdss_dpi.0 · 1f92a1a4
      Tomi Valkeinen authored
      DPI driver gets currently the vdds_dsi regulator via omapdss device.
      This is not correct, and we'll change the DPI driver to get the
      regulator directly via omapdss_dpi.0 device.
      
      This patch changes the relevant board files to add vdds_dsi supply for
      omapdss_dpi.0 device.
      
      Note that the vdds_dsi supply for omapdss device is still left there, as
      the current display driver uses it. When both the board files and the
      display driver has been changed, we can remove the unused supply.
      Signed-off-by: default avatarTomi Valkeinen <tomi.valkeinen@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      1f92a1a4
    • Tomi Valkeinen's avatar
      ARM: OMAP: fix dsi regulator names · 1738ddbe
      Tomi Valkeinen authored
      board-cm-t35.c and board-ldp.c contain regulator supply entries for
      vdds_dsi. However, the given device name is wrong.
      
      This patch fixes the device name from omapdss_dsi1 to omapdss_dsi.0.
      
      Note that as far as I know, DSI driver is not used on these boards, so
      this should not have caused any problems. The DSI block can be used to
      generate clock for DPI, though, but that's not enabled for omap3 boards
      currently.
      Signed-off-by: default avatarTomi Valkeinen <tomi.valkeinen@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      1738ddbe
  5. 04 Apr, 2013 2 commits
  6. 03 Apr, 2013 1 commit
    • Archit Taneja's avatar
      OMAPDSS: panels: keep platform data of all panels in a single header · a0d8dde9
      Archit Taneja authored
      Structs for platform data of omapdss panels are found in headers in the
      'include/video/' path. Board files populate these structs with platform
      specific values, and the panel driver uses these to configure the panel.
      
      Currently, each panel has it's own header in the above path. Move all the
      omapdss panel platform data structs to a single header omap-panel-data.h.
      This is useful because:
      
      - All other omapdss panel drivers will be modified to use platform data. This
        would lead to a lot of panel headers usable only by omapdss. A lot of these
        platform data structs are trivial, and don't really need a separate header.
      - Platform data would be eventually removed, and platform information would be
        passed via device tree. Therefore, omapdss panel platform data structs are
        temporary, and will be easier to remove if they are all in the same header.
      - All board files will have to include the same header to configure a panel's
        platform data, that makes the board files more consistent.
      Signed-off-by: default avatarArchit Taneja <archit@ti.com>
      a0d8dde9
  7. 02 Apr, 2013 1 commit
  8. 14 Feb, 2013 1 commit
  9. 06 Feb, 2013 1 commit
  10. 22 Jan, 2013 1 commit
  11. 24 Dec, 2012 1 commit
  12. 14 Dec, 2012 1 commit
    • Tomi Valkeinen's avatar
      OMAP: board-files: fix i2c_bus for tfp410 · ca2e16fa
      Tomi Valkeinen authored
      The i2c handling in tfp410 driver, which handles converting parallel RGB
      to DVI, was changed in 958f2717
      (OMAPDSS: TFP410: pdata rewrite). The patch changed what value the
      driver considers as invalid/undefined.  Before the patch, 0 was the
      invalid value, but as 0 is a valid bus number, the patch changed this to
      -1.
      
      However, the fact was missed that many board files do not define the bus
      number at all, thus it's left to 0. This causes the driver to fail to
      get the i2c bus, exiting from the driver's probe with an error, meaning
      that the DVI output does not work for those boards.
      
      This patch fixes the issue by changing the i2c_bus number field in the
      driver's platform data from u16 to int, and setting the bus number to -1
      in the board files for the boards that did not define the bus. The
      exception is devkit8000, for which the bus is set to 1, which is the
      correct bus for that board.
      
      The bug exists in v3.5+ kernels.
      Signed-off-by: default avatarTomi Valkeinen <tomi.valkeinen@ti.com>
      Reported-by: default avatarThomas Weber <thomas@tomweber.eu>
      Cc: Thomas Weber <thomas@tomweber.eu>
      Cc: <stable@vger.kernel.org> # v3.5+
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      ca2e16fa
  13. 08 Nov, 2012 1 commit
  14. 02 Nov, 2012 1 commit
  15. 24 Oct, 2012 1 commit
    • Tony Lindgren's avatar
      ARM: OMAP2+: Introduce local usb.h · 54db6eee
      Tony Lindgren authored
      Let's move what we can from plat/usb.h to the local usb.h
      for ARM common zImage support.
      
      This is needed so we can remove plat/usb.h for ARM common
      zImage support.
      
      Cc: Samuel Ortiz <sameo@linux.intel.com>
      Cc: Alan Stern <stern@rowland.harvard.edu>
      Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
      Cc: Partha Basak <parthab@india.ti.com>
      Cc: Keshava Munegowda <keshava_mgowda@ti.com>
      Cc: linux-usb@vger.kernel.org
      Acked-by: default avatarFelipe Balbi <balbi@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      54db6eee
  16. 15 Oct, 2012 2 commits
    • Afzal Mohammed's avatar
      ARM: OMAP2+: gpmc: localize gpmc header · 3ef5d007
      Afzal Mohammed authored
      Requirement of gpmc header outside of mach-omap2 has been
      cutoff, move gpmc header file in plat-omap folder to local
      mach-omap2 folder
      
      Objective - common zImage participation of omap
      Signed-off-by: default avatarAfzal Mohammed <afzal@ti.com>
      3ef5d007
    • Afzal Mohammed's avatar
      ARM: OMAP2+: nand: header cleanup · bc3668ea
      Afzal Mohammed authored
      For common arm zImage existing nand header file
      in platform specific location was moved to generic
      platform data location, but it contained more than
      platform data, remove it. New local header has been
      created for exposing functions.
      
      Also move gpmc-nand platform data to platform header
      meant for nand from gpmc header file
      Signed-off-by: default avatarAfzal Mohammed <afzal@ti.com>
      bc3668ea
  17. 20 Sep, 2012 1 commit
  18. 19 Sep, 2012 1 commit
    • Arnd Bergmann's avatar
      ARM: omap: move platform_data definitions · 2203747c
      Arnd Bergmann authored
      Platform data for device drivers should be defined in
      include/linux/platform_data/*.h, not in the architecture
      and platform specific directories.
      
      This moves such data out of the omap include directories
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      Acked-by: default avatarMark Brown <broonie@opensource.wolfsonmicro.com>
      Acked-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      Acked-by: default avatarNicolas Pitre <nico@linaro.org>
      Acked-by: default avatarTony Lindgren <tony@atomide.com>
      Cc: Kevin Hilman <khilman@ti.com>
      Cc: "Benoît Cousson" <b-cousson@ti.com>
      Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
      Cc: David Woodhouse <dwmw2@infradead.org>
      Cc: Kyungmin Park <kyungmin.park@samsung.com>
      Cc: Ohad Ben-Cohen <ohad@wizery.com>
      Cc: Grant Likely <grant.likely@secretlab.ca>
      Cc: Omar Ramirez Luna <omar.ramirez@ti.com>
      Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>
      Cc: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
      Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>
      Cc: Jarkko Nikula <jarkko.nikula@bitmer.com>
      Cc: Liam Girdwood <lrg@ti.com>
      Cc: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
      Cc: Jean Pihet <j-pihet@ti.com>
      Cc: J Keerthy <j-keerthy@ti.com>
      Cc: linux-omap@vger.kernel.org
      2203747c
  19. 13 Sep, 2012 2 commits
  20. 10 Sep, 2012 1 commit
  21. 15 Aug, 2012 1 commit
  22. 02 Jul, 2012 2 commits
  23. 09 May, 2012 4 commits
  24. 08 May, 2012 1 commit
  25. 03 Apr, 2012 1 commit
  26. 24 Feb, 2012 1 commit
  27. 20 Feb, 2012 1 commit
    • Tony Lindgren's avatar
      ARM: OMAP2+: Split omap2_hsmmc_init() to properly support I2C GPIO pins · 3b972bf0
      Tony Lindgren authored
      Otherwise omap_device_build() and omap_mux related functions
      can't be marked as __init when twl is build as a module.
      
      If a board is using GPIO pins or regulators configured by an
      external chip, such as TWL PMIC on I2C bus, the board must
      mark those MMC controllers as deferred. Additionally both
      omap_hsmmc_init() and omap_hsmmc_late_init() must be called
      by the board.
      
      For MMC controllers using internal GPIO pins for card
      detect and regulators the slots don't need to be marked
      deferred. In this case calling omap_hsmmc_init() is sufficient.
      
      Only mark the MMC slots using gpio_cd or gpio_wd as deferred
      as noted by Igor Grinberg <grinberg@compulab.co.il>.
      
      Note that this patch does not change the behaviour for
      board-4430sdp.c board-omap4panda.c. These boards wrongly
      rely on the omap_hsmmc.c init function callback to configure
      the PMIC GPIO interrupt lines on external chip. If the PMIC
      interrupt lines are not configured during init, they will
      fail.
      Reported-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      Signed-off-by: default avatarRajendra Nayak <rnayak@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      3b972bf0
  28. 08 Feb, 2012 1 commit
  29. 05 Jan, 2012 1 commit
  30. 13 Dec, 2011 3 commits