From: Jamie Iles <jamie@jamieiles.com>
To: Rob Herring <robherring2@gmail.com>
Cc: Jamie Iles <jamie@jamieiles.com>,
linux-kernel@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org, grant.likely@secretlab.ca,
linus.walleij@stericsson.com,
broonie@opensource.wolfsonmicro.com,
Rob Herring <rob.herring@calxeda.com>
Subject: Re: [PATCHv5 1/4] of: document common interrupt controller details
Date: Thu, 5 Jan 2012 14:09:52 +0000 [thread overview]
Message-ID: <20120105140952.GE4641@page> (raw)
In-Reply-To: <4F05AE79.6050108@gmail.com>
On Thu, Jan 05, 2012 at 08:06:49AM -0600, Rob Herring wrote:
> On 01/04/2012 07:23 PM, Jamie Iles wrote:
> > It's common for interrupt controllers to need to encode interrupt
> > trigger types and the Linux specific types seem common. Document these
> > in a centralized place so that they don't get reinvented each time a new
> > controller is added.
> >
> > Suggested-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> > Cc: Grant Likely <grant.likely@secretlab.ca>
> > Cc: Rob Herring <rob.herring@calxeda.com>
> > Signed-off-by: Jamie Iles <jamie@jamieiles.com>
>
> I can take this if you want. Doesn't really matter as it is all going to
> Grant anyway.
OK, whatever is easiest for you. I guess it's too late for the GPIO
driver to go into 3.3(?) but this is probably fine to go in now for
other drivers to base on...
Jamie
next prev parent reply other threads:[~2012-01-05 14:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 1:23 [PATCHv5 0/4] Synopsys DesignWare APB GPIO Jamie Iles
[not found] ` <1325726619-31796-1-git-send-email-jamie-wmLquQDDieKakBO8gow8eQ@public.gmane.org>
2012-01-05 1:23 ` [PATCHv5 1/4] of: document common interrupt controller details Jamie Iles
2012-01-05 14:06 ` Rob Herring
2012-01-05 14:09 ` Jamie Iles [this message]
2012-01-05 1:23 ` [PATCHv5 2/4] gpio: add a driver for the Synopsys DesignWare APB GPIO block Jamie Iles
2012-01-05 1:23 ` [PATCHv5 3/4] gpio: dwapb: add support for GPIO interrupts Jamie Iles
2012-01-05 1:23 ` [PATCHv5 4/4] ARM: picoxcell: use new Synopsys Designware GPIO binding Jamie Iles
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=20120105140952.GE4641@page \
--to=jamie@jamieiles.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=robherring2@gmail.com \
/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).