From: Linus Walleij <linus.walleij@linaro.org>
To: Daniel Machon <daniel.machon@microchip.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Lars Povlsen <lars.povlsen@microchip.com>,
Horatiu Vultur <horatiu.vultur@microchip.com>,
Steen Hegelund <Steen.Hegelund@microchip.com>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] pinctrl: ocelot: add support for lan969x SoC
Date: Tue, 1 Oct 2024 13:58:44 +0200 [thread overview]
Message-ID: <CACRpkdZWp8W5W0BLzCJ6hHoqMUwCr4oZ7XZS3RbZ4YYNp__h2Q@mail.gmail.com> (raw)
In-Reply-To: <20240917-lan969x-pinctrl-v2-0-ea02cbc56831@microchip.com>
On Tue, Sep 17, 2024 at 2:46 PM Daniel Machon
<daniel.machon@microchip.com> wrote:
> This series adds support for lan969x SoC pinctrl by reusing the existing
> Ocelot pinctrl driver.
>
> There are 66 General Purpose I/O pins that are individually configurable
> to multiple interfaces. The matrix of available GPIO alternate functions
> is detailed in the pinmuxing table of patch #2.
>
> Patch #1 adds compatible strings for lan969x in the dt-bindings.
> Patch #2 adds support for lan969x SoC pinctrl.
>
> Signed-off-by: Daniel Machon <daniel.machon@microchip.com>
Bindings ACKed and no reaction from other maintainers for two
weeks, so patches applied!
Yours,
Linus Walleij
prev parent reply other threads:[~2024-10-01 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 12:45 [PATCH v2 0/2] pinctrl: ocelot: add support for lan969x SoC Daniel Machon
2024-09-17 12:45 ` [PATCH v2 1/2] dt-bindings: ocelot: document lan969x-pinctrl Daniel Machon
2024-09-17 21:10 ` Conor Dooley
2024-09-17 12:45 ` [PATCH v2 2/2] pinctrl: ocelot: add support for lan969x SoC pinctrl Daniel Machon
2024-10-01 11:58 ` Linus Walleij [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=CACRpkdZWp8W5W0BLzCJ6hHoqMUwCr4oZ7XZS3RbZ4YYNp__h2Q@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=Steen.Hegelund@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=daniel.machon@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=horatiu.vultur@microchip.com \
--cc=krzk+dt@kernel.org \
--cc=lars.povlsen@microchip.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).