Skip to content
  1. Apr 03, 2013
    • Magnus Damm's avatar
      gpio: Renesas R-Car GPIO driver V3 · 119f5e44
      Magnus Damm authored
      
      
      This patch is V3 of a GPIO driver for the R-Car series of
      SoCs from Renesas. This driver is designed to be reusable
      between multiple SoCs that share the same basic building block,
      but so far it has only been used on R-Car H1 (r8a7779).
      
      Each driver instance handles 32 GPIOs with individually
      maskable IRQs. The driver operates on a single I/O memory
      range and the 32 GPIOs are hooked up a single interrupt.
      
      In the case of R-Car H1 either external IRQ pins or GPIOs
      with interrupts can be used for on-board interupts. For
      external IRQs 4 pins are supported, and in the case of GPIO
      there are 202 GPIOS as 202 interrupts hooked up via 6 driver
      instances and to the GIC and the Cortex-A9 Quad.
      
      At this point this driver is interfacing as a regular
      platform device driver. In the future DT support will be
      submitted as an incremental feature patch.
      
      Signed-off-by: default avatarMagnus Damm <damm@opensource.se>
      Reviewed-by: default avatarLinus Walleij <linus.walleij@linaro.org>
      Signed-off-by: default avatarSimon Horman <horms+renesas@verge.net.au>
      119f5e44
  2. Apr 02, 2013
  3. Mar 28, 2013
    • Bastian Hecht's avatar
      irqchip: intc-irqpin: Add support for shared interrupt lines · 427cc720
      Bastian Hecht authored
      
      
      On some hardware we don't have a 1-1 mapping from the external
      interrupts coming from INTC to the GIC SPI pins. We can however
      share lines to demux incoming IRQs on these SoCs.
      
      This patch enables the intc_irqpin driver to detect requests for shared
      interrupt lines and demuxes them properly by querying the INTC INTREQx0A
      registers.
      
      If you need multiple shared intc_irqpin device instances, be sure to mask
      out all interrupts on the INTC that share the one line before you start
      to register them. Else you run into IRQ floods that would be caused by
      interrupts for which no handler has been set up yet when the first
      intc_irqpin device is registered.
      
      Signed-off-by: default avatarBastian Hecht <hechtb+renesas@gmail.com>
      Acked-by: default avatarMagnus Damm <damm@opensource.se>
      Signed-off-by: default avatarSimon Horman <horms+renesas@verge.net.au>
      427cc720
  4. Mar 18, 2013