mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sebastian Reichel <sebastian.reichel@collabora.co.uk>
To: Lars Poeschel <poeschel@lemonage.de>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	"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>
Subject: Re: [PATCH] dt-bindings: pinctrl: Move mcp23s08 from gpio
Date: Mon, 9 Oct 2017 12:33:57 +0200	[thread overview]
Message-ID: <20171009103357.kcj2uqse6yv2xepm@earth> (raw)
In-Reply-To: <8063886.6te7U6k3td@lem-wkst-02>

[-- Attachment #1: Type: text/plain, Size: 2117 bytes --]

Hi,

On Mon, Oct 09, 2017 at 11:39:02AM +0200, Lars Poeschel wrote:
> 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.

Yes, the driver supports being used as pin controller with the
"bias-pull-up;" property now. For example I use this with a RPi
to enable pull-ups for all pins:

gpio21: gpio@21 {
        compatible = "microchip,mcp23017";
        gpio-controller;
        #gpio-cells = <0x2>;
        reg = <0x21>;
        interrupt-parent = <&socgpio>;
        interrupts = <0x17 0x8>;
        interrupt-names = "mcp23017@21 irq";
        interrupt-controller;
        #interrupt-cells = <0x2>;
        microchip,irq-mirror;
        pinctrl-names = "default";
        pinctrl-0 = <&i2cgpio0irq &gpio21pullups>;

        gpio21pullups: pinmux {
                pins = "gpio0", "gpio1", "gpio2", "gpio3",
                       "gpio4", "gpio5", "gpio6", "gpio7",
                       "gpio8", "gpio9", "gpio10", "gpio11",
                       "gpio12", "gpio13", "gpio14", "gpio15";
                bias-pull-up;
        };  
};

-- Sebastian

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-10-09 10:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-05  7:50 Lars Poeschel
2017-10-07 23:58 ` Linus Walleij
2017-10-09  9:39   ` Lars Poeschel
2017-10-09 10:33     ` Sebastian Reichel [this message]
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=20171009103357.kcj2uqse6yv2xepm@earth \
    --to=sebastian.reichel@collabora.co.uk \
    --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=poeschel@lemonage.de \
    --cc=robh+dt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®