1. 13 9月, 2012 2 次提交
    • T
      ARM: OMAP2+: Prepare for irqs.h removal · 7d7e1eba
      Tony Lindgren 提交于
      As the interrupts should only be defined in the platform_data, and
      eventually coming from device tree, there's no need to define them
      in header files.
      
      Let's remove the hardcoded references to irqs.h and fix up the includes
      so we don't rely on headers included in irqs.h. Note that we're
      defining OMAP_INTC_START as 0 to the interrupts. This will be needed
      when we enable SPARSE_IRQ. For some drivers we need to add
      #include <plat/cpu.h> for now until these drivers are fixed to
      remove cpu_is_omapxxxx() usage.
      
      While at it, sort som of the includes the standard way, and add
      the trailing commas where they are missing in the related data
      structures.
      
      Note that for drivers/staging/tidspbridge we just define things
      locally.
      
      Cc: Paul Walmsley <paul@pwsan.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      7d7e1eba
    • T
      ARM: OMAP2+: Remove hardcoded twl4030 gpio_base, irq_base and irq_end · a940d9a1
      Tony Lindgren 提交于
      We can't use hardcoded interrupts for SPARSE_IRQ, and can replace
      the hardcoded gpio_base with twl_gpiochip.base after it's been
      allocated.
      
      Cc: Grant Likely <grant.likely@secretlab.ca>
      Cc: Samuel Ortiz <sameo@linux.intel.com>
      Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>
      Acked-by: NLinus Walleij <linus.walleij@linaro.org>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      a940d9a1
  2. 11 9月, 2012 1 次提交
  3. 09 7月, 2012 1 次提交
  4. 10 5月, 2012 2 次提交
  5. 09 5月, 2012 3 次提交
    • T
      OMAPDSS: DSI: implement generic DSI pin config · e4a9e94c
      Tomi Valkeinen 提交于
      In preparation for device tree, this patch changes how the DSI pins are
      configured. The current configuration method is only doable with board
      files and the configuration data is OMAP specific.
      
      This patch moves the configuration data to the panel's platform data,
      and the data can easily be given via DT in the future. The configuration
      data format is also changed to a generic one which should be suitable
      for all platforms.
      
      The new format is an array of pin numbers, where the array items start
      from clock + and -, then data1 + and -, and so on. For example:
      
      {
      	0,	// pin num for clock lane +
      	1,	// pin num for clock lane -
      	2,	// pin num for data1 lane +
      	3,	// pin num for data1 lane -
      	...
      }
      
      The pin numbers are translated by the DSI driver and used to configure
      the hardware appropriately.
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      Acked-by: NTony Lindgren <tony@atomide.com>
      e4a9e94c
    • T
      OMAPDSS: Taal: move reset gpio handling to taal driver · 3acc797c
      Tomi Valkeinen 提交于
      The reset GPIO for Taal panel driver is currently requested in the
      4430sdp board file. This patch moves the gpio request/free into the Taal
      driver, where it should be.
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      Acked-by: NTony Lindgren <tony@atomide.com>
      3acc797c
    • B
      ARM: OMAP4: hsmmc: check for null pointer · 1ee47b0a
      Balaji T K 提交于
      platform_device pdev can be NULL if CONFIG_MMC_OMAP_HS is not set.
      Add check for NULL pointer. while at it move the duplicated functions
      to omap4-common.c
      
      Fixes the following boot crash seen with omap4sdp and omap4panda
      when MMC is disabled.
      
      Unable to handle kernel NULL pointer dereference at virtual address 0000008c
      pgd = c0004000
      [0000008c] *pgd=00000000
      Internal error: Oops: 5 [#1] SMP ARM
      Modules linked in:
      CPU: 0    Not tainted  (3.4.0-rc1-05971-ga4dfa82 #4)
      PC is at omap_4430sdp_init+0x184/0x410
      LR is at device_add+0x1a0/0x664
      Signed-off-by: NBalaji T K <balajitk@ti.com>
      Reported-by: NSantosh Shilimkar <santosh.shilimkar@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      1ee47b0a
  6. 08 5月, 2012 1 次提交
  7. 16 4月, 2012 1 次提交
  8. 29 3月, 2012 1 次提交
  9. 22 3月, 2012 1 次提交
  10. 17 3月, 2012 1 次提交
  11. 06 3月, 2012 1 次提交
  12. 21 2月, 2012 1 次提交
    • T
      ARM: OMAP2+: Split omap2_hsmmc_init() to properly support I2C GPIO pins · 3b972bf0
      Tony Lindgren 提交于
      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: NRussell King <rmk+kernel@arm.linux.org.uk>
      Signed-off-by: NRajendra Nayak <rnayak@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      3b972bf0
  13. 13 2月, 2012 3 次提交
  14. 26 1月, 2012 6 次提交
  15. 05 1月, 2012 3 次提交
  16. 15 12月, 2011 1 次提交
    • G
      ARM: OMAP2+: UART: Add default mux for all uarts. · 7496ba30
      Govindraj.R 提交于
      Padconf wakeup is used to wakeup uart after uart fclks/iclks are gated.
      Rx-Pad wakeup was done by writing to rx-pad offset value populated in
      serial.c idle_init. Remove the direct reading and writing into rx pad.
      Remove the padconf field part of omap_uart_state struct and pad offsets
      populated.
      
      Now with mux framework support we can use mux_utilities
      along with hmwod framework to handle io-pad configuration and enable rx-pad
      wake-up mechanism.
      
      To avoid breaking any board support add default mux data for all uart's
      if mux info is not passed from board file.
      With the default pads populated in serial.c wakeup capability for
      rx pads is set, this can be used to enable uart_rx io-pad wakeup from
      hwmod framework. The pad values in 3430sdp/4430sdp/omap4panda board file
      are same as the default pad values populated in serial.c. Remove pad values
      from 3430sdp/4430sdp/omap4panda board file and use the default pads
      from serial.c file.
      Signed-off-by: NGovindraj.R <govindraj.raja@ti.com>
      Signed-off-by: NKevin Hilman <khilman@ti.com>
      7496ba30
  17. 14 12月, 2011 1 次提交
  18. 10 12月, 2011 1 次提交
  19. 18 11月, 2011 1 次提交
  20. 16 11月, 2011 1 次提交
  21. 04 10月, 2011 1 次提交
  22. 30 9月, 2011 4 次提交
  23. 27 9月, 2011 1 次提交
  24. 24 8月, 2011 1 次提交