From: Michael Zavertkin <misha.zavertkin@mail.ru>
To: Bartosz Golaszewski <brgl@kernel.org>
Cc: Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Sander Vanheule <sander@svanheule.net>,
Bert Vermeulen <bert@biot.com>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/2] gpio: realtek-otto: add pinctrl support
Date: Wed, 2 Sep 2026 20:02:01 +0700 [thread overview]
Message-ID: <apgeSVMUQlwqFGEa@gamepc> (raw)
In-Reply-To: <CAMRc=Mf16PBE0=Udm+A--i2d1VoZCEC1=LNC2q=t8BwqtgZY0g@mail.gmail.com>
On Wed, Sep 02, 2026 at 11:27:50AM +0200, Bartosz Golaszewski wrote:
> On Thu, Aug 27, 2026 at 4:29 PM Michael Zavertkin
> <misha.zavertkin@mail.ru> wrote:
> >
> > RTL9607C relies on pinctrl to mux SoC pins. Use pinctrl to request pins
> > for GPIO.
> > pinctrl driver for other SoCs might be implemented later.
> >
>
> So for now shouldn't you make it conditional on the compatible for
> this one model?
>
> Bart
It might, but enabling it for all will spare time if/when pin
controllers for other SoCs will be implemented. And it doesn't change
anything if pinctrl not enabled/provided for them.
prev parent reply other threads:[~2026-09-02 13:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 14:29 [PATCH v4 0/2] gpio: realtek-otto: add pinctrl support Michael Zavertkin
2026-08-27 14:29 ` [PATCH v4 1/2] dt-bindings: gpio: otto-gpio: Add gpio-ranges Michael Zavertkin
2026-09-01 7:50 ` Krzysztof Kozlowski
2026-08-27 14:29 ` [PATCH v4 2/2] gpio: realtek-otto: add pinctrl support Michael Zavertkin
2026-08-27 14:54 ` sashiko-bot
2026-09-02 9:27 ` Bartosz Golaszewski
2026-09-02 13:02 ` Michael Zavertkin [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=apgeSVMUQlwqFGEa@gamepc \
--to=misha.zavertkin@mail.ru \
--cc=bert@biot.com \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sander@svanheule.net \
/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