linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 01/12] ARM: Orion: DT support for IRQ and GPIO Controllers
Date: Thu, 5 Jul 2012 11:02:51 +0200	[thread overview]
Message-ID: <20120705110251.596331e0@skate> (raw)
In-Reply-To: <1341325365-21393-2-git-send-email-andrew@lunn.ch>

Hello Andrew,

Le Tue,  3 Jul 2012 16:22:34 +0200,
Andrew Lunn <andrew@lunn.ch> a ?crit :

> Both IRQ and GPIO controllers can now be represented in DT.  The IRQ
> controllers are setup first, and then the GPIO controllers. Interrupts
> for GPIO lines are placed directly after the main interrupts in the
> interrupt space.
> 
> Signed-off-by: Andrew Lunn <andrew@lunn.ch>

I have started working on a pinctrl driver for mvebu, which would
handle pin muxing (MPP) + gpio + gpio interrupts.

So far, the pin muxing part is working (needs some polishing, but the
foundation is here), with device tree bindings. I think the pin muxing
could be used for Orion as well.

Now, I'm planning to start working on the gpio + gpio interrupts parts
of the driver, and I'm wondering how to interact with your work on the
matter. My understanding is that the new way of doing a pinmux+gpio
driver is to implement it in drivers/pinctrl/, which I have started
doing.

Should I continue working on a drivers/pinctrl/ driver for mvebu for
Armada 370/XP, and then we see together if it makes sense to extend to
Orion, and if so, what changes are needed?

Thanks,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2012-07-05  9:02 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-03 14:22 [PATCH v2 00/12] IRQ, GPIO SPI, I2C, etc DTC support Andrew Lunn
2012-07-03 14:22 ` [PATCH v2 01/12] ARM: Orion: DT support for IRQ and GPIO Controllers Andrew Lunn
2012-07-05  8:15   ` Andrew Lunn
2012-07-05  9:02   ` Thomas Petazzoni [this message]
2012-07-05  9:48     ` Andrew Lunn
2012-07-05 10:10       ` Thomas Petazzoni
2012-07-05 10:25         ` Andrew Lunn
2012-07-05 10:11       ` Arnaud Patard (Rtp)
2012-07-05 10:20         ` Thomas Petazzoni
2012-07-05 10:38           ` Arnaud Patard (Rtp)
2012-07-05 11:42             ` Thomas Petazzoni
2012-07-05 11:48               ` Andrew Lunn
2012-07-05 12:09                 ` Sebastian Hesselbarth
2012-07-05 12:58       ` Thomas Petazzoni
2012-07-05 13:15         ` Andrew Lunn
2012-07-05 13:28           ` Thomas Petazzoni
2012-07-05 13:33             ` Andrew Lunn
2012-07-05 13:36               ` Thomas Petazzoni
2012-07-05 12:25   ` Arnd Bergmann
2012-07-05 13:08     ` Andrew Lunn
2012-07-05 13:47       ` Arnd Bergmann
2012-07-05 13:54         ` Andrew Lunn
2012-07-05 15:47           ` Arnd Bergmann
2012-07-05 14:14       ` Sebastian Hesselbarth
2012-07-05 14:43         ` Andrew Lunn
2012-07-05 14:54         ` Arnd Bergmann
2012-07-05 15:51           ` Sebastian Hesselbarth
2012-07-05 16:30             ` Arnaud Patard (Rtp)
2012-07-05 16:16           ` Andrew Lunn
2012-07-06 20:08             ` Arnd Bergmann
2012-07-06 21:00               ` Andrew Lunn
2012-07-07  0:24                 ` Where to put a large bootloader-supplied device tree on ARM ? Mitch Bradley
2012-07-07  1:23                   ` David VomLehn (dvomlehn)
2012-07-07  1:59                     ` Mitch Bradley
2012-07-09  4:30                       ` Nicolas Pitre
2012-07-12  6:52                         ` Mitch Bradley
2012-07-12 18:16                           ` Nicolas Pitre
2012-07-12 20:34                           ` Rob Herring
2012-07-12 21:38                             ` [U-Boot] " Albert ARIBAUD
2012-07-12 21:47                               ` Wolfgang Denk
2012-07-13  1:28                                 ` Rob Herring
2012-07-13  6:45                                   ` Albert ARIBAUD
2012-07-05 18:36           ` [PATCH v2 01/12] ARM: Orion: DT support for IRQ and GPIO Controllers Mitch Bradley
2012-07-03 14:22 ` [PATCH v2 02/12] SPI: Refactor spi-orion to use SPI framework queue Andrew Lunn
2012-07-03 14:22 ` [PATCH v2 03/12] spi-orion: remove uneeded spi_info Andrew Lunn
2012-07-03 14:22 ` [PATCH v2 04/12] spi-orion: add device tree binding Andrew Lunn
2012-07-03 14:22 ` [PATCH v2 05/12] ARM: kirkwood: use devicetree for orion-spi Andrew Lunn
2012-07-03 14:22 ` [PATCH v2 06/12] ARM: kirkwood: use devicetree for SPI on dreamplug Andrew Lunn
2012-07-03 14:22 ` [PATCH v2 07/12] I2C: MV64XXX: Add Device Tree support Andrew Lunn
2012-07-03 15:59   ` Florian Fainelli
2012-07-03 16:58     ` Andrew Lunn
2012-07-04 19:49       ` Florian Fainelli
2012-07-05  6:52         ` Andrew Lunn
2012-07-03 14:22 ` [PATCH v2 08/12] Kirkwood: Add basic device tree support for QNAP TS219 Andrew Lunn
2012-07-03 15:47   ` Florian Fainelli
2012-07-03 17:09     ` Andrew Lunn
2012-07-03 14:22 ` [PATCH v2 09/12] ARM: Kirkwood: DTify the watchdog timer Andrew Lunn
2012-07-03 14:22 ` [PATCH v2 10/12] ATA: sata_mv: Add device tree support Andrew Lunn
2012-07-03 14:22 ` [PATCH v2 11/12] ARM: Kirkwood: Use DT to configure SATA device Andrew Lunn
2012-07-03 14:52   ` Josh Coombs
2012-07-03 15:32     ` Andrew Lunn
2012-07-03 14:22 ` [PATCH v2 12/12] Crypto: CESA: Add support for DT based instantiation Andrew Lunn
2012-07-03 15:50   ` Florian Fainelli
2012-07-03 17:03     ` Andrew Lunn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120705110251.596331e0@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).