From: Lars Poeschel <poeschel@lemonage.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Sebastian Reichel <sebastian.reichel@collabora.co.uk>
Subject: Re: [PATCH] dt-bindings: pinctrl: Move mcp23s08 from gpio
Date: Mon, 09 Oct 2017 11:39:02 +0200 [thread overview]
Message-ID: <8063886.6te7U6k3td@lem-wkst-02> (raw)
In-Reply-To: <CACRpkdY=r8XBqHKrVeZ34jR8FJM-zmOUxCSMhEROc6fOjfwX-A@mail.gmail.com>
On Sun, Oct 8, 2017 at 01:58:52 CEST Linus Walleij wrote:
CCing-in Sebastian Reichel who did the move to pinctrl and pinctrl support as
well.
> On Thu, Oct 5, 2017 at 9:50 AM, Lars Poeschel <poeschel@lemonage.de> wrote:
> > The mcp23s08 driver was moved from gpio to pinctrl. This moves it's
> > devicetree binding doc as well. So driver and binding doc are in sync
> > again.
> >
> > Signed-off-by: Lars Poeschel <poeschel@lemonage.de>
>
> Are there no new references to the generic pin control binding
> needed as well?
Well, yes there is one: As far as I can see it supports the bias-pull-up
property.
My first intention was to have the doc as we have it in the right place, but
you are right: It needs an update as well. I can do this, but Sebastian,
please keep an eye on that.
As there are already patches depending on this patch (https://marc.info/?
l=linux-gpio&m=150726650325394&w=4) I would suggest, that you pull in this
patch as is and I do the little update on the doc as a seperate patch.
Regards,
Lars
next prev parent reply other threads:[~2017-10-09 9:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 7:50 [PATCH] dt-bindings: pinctrl: Move mcp23s08 from gpio Lars Poeschel
[not found] ` <20171005075002.9901-1-poeschel-Xtl8qvBWbHwb1SvskN2V4Q@public.gmane.org>
2017-10-07 23:58 ` Linus Walleij
2017-10-09 9:39 ` Lars Poeschel [this message]
2017-10-09 10:33 ` Sebastian Reichel
2017-10-09 10:29 ` Sebastian Reichel
2017-10-11 8:01 ` Linus Walleij
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=8063886.6te7U6k3td@lem-wkst-02 \
--to=poeschel@lemonage.de \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=sebastian.reichel@collabora.co.uk \
/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