From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Linus Walleij <linus.walleij@linaro.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH 3/3] gpio: pcf857x: Add OF support
Date: Tue, 20 Aug 2013 00:52:09 +0200 [thread overview]
Message-ID: <5668808.mMAAfXl8cc@avalon> (raw)
In-Reply-To: <CACRpkdarBoKge2Z5wFW46KAsd0N942TYzpoxCRt0AmcU8ad0Rw@mail.gmail.com>
Hi Linus,
On Friday 16 August 2013 17:00:29 Linus Walleij wrote:
> On Mon, Jul 29, 2013 at 8:39 PM, Laurent Pinchart wrote:
> > Add DT bindings for the pcf857x-compatible chips and parse the device
> > tree node in the driver.
> >
> > Signed-off-by: Laurent Pinchart
> > <laurent.pinchart+renesas@ideasonboard.com>
> > ---
> >
> > .../devicetree/bindings/gpio/gpio-pcf857x.txt | 69 +++++++++++++++++
>
> Do you think you can get one of the DT bindings mainatiners to ACK this
> part?
They're already CC'ed. I suppose vacations played a role in the lack of reply.
I'd like to avoid having to switch to stalker mode ;-)
> I am told we need to get more strict on binding review.
>
> It will be subject to timeout if it takes to long and you made a reasonable
> effort to get their consent though.
>
> > + - interrupt-controller: Identifies the node as an interrupt controller.
> > + - #interrupt-cells: Number of cells to encode an interrupt source,
> > shall be 2.
> > + - interrupt-parent: phandle of the parent interrupt controller.
> > + - interrupts: Interrupt specifier for the controllers interrupt.
>
> So this is another one of of those GPIO controller that are also interrupt
> controllers.
>
> So it will be subject to the same dilemma as the OMAP expander that has
> caused so much stir :-(
>
> Can you provide your input in the discussion regarding my patch with the
> subject:
> "RFC: interrupt consistency check for OF GPIO IRQs"
Done.
> This patch will affect this driver also, in a very direct way, by just
> stealing and setting as input any GPIO line used for an IRQ.
>
> > +Please refer to gpio.txt in this directory for details of the common GPIO
> > +bindings used by client devices.
> > +
> > +Example: PCF8575 I/O expander node
> > +
> > + pcf8575: gpio@20 {
> > + compatible = "nxp,pcf8575";
> > + reg = <0x20>;
> > + interrupt-parent = <&irqpin2>;
> > + interrupts = <3 0>;
> > + interrupt-controller;
> > + #interrupt-cells = <2>;
> > + };
>
> Not gpio-controller?
I've fixed that in my tree already, it seems I forgot to repost. I will do so
now.
> Apart from that it looks good, please help out with the gpio-controller vs
> interrupt-controller dilemma if you can because it's getting really
> frustrating...
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2013-08-19 22:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 18:39 [PATCH 0/3] pcf857x: Add OF support Laurent Pinchart
2013-07-29 18:39 ` [PATCH 1/3] gpio: pcf857x: Sort headers alphabetically Laurent Pinchart
2013-07-29 18:39 ` [PATCH 2/3] gpio: pcf857x: Remove pdata argument to pcf857x_irq_domain_init() Laurent Pinchart
2013-07-29 18:39 ` [PATCH 3/3] gpio: pcf857x: Add OF support Laurent Pinchart
2013-08-08 10:58 ` [3/3] " Laurent Pinchart
2013-08-16 15:00 ` [PATCH 3/3] " Linus Walleij
2013-08-19 22:52 ` Laurent Pinchart [this message]
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=5668808.mMAAfXl8cc@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.