From: Rob Herring <robh@kernel.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Linus Walleij" <linus.walleij@linaro.org>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Sean Wang" <sean.wang@kernel.org>,
"Rafał Miłecki" <rafal@milecki.pl>,
linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
"Chuanhong Guo" <gch981213@gmail.com>,
linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"Hsin-Yi Wang" <hsinyi@chromium.org>,
"Conor Dooley" <conor+dt@kernel.org>
Subject: Re: [PATCH 2/3] dt-bindings: pinctrl: mediatek: mt7622: add "antsel" function
Date: Wed, 10 Apr 2024 13:02:15 -0500 [thread overview]
Message-ID: <171277213295.820159.3023089832430236921.robh@kernel.org> (raw)
In-Reply-To: <20240408090506.21596-2-zajec5@gmail.com>
On Mon, 08 Apr 2024 11:05:05 +0200, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> MT7622 pinctrl has ANTSEL* pins. Linux support for those was added in
> the commit 19f599e83ac5 ("pinctrl: mediatek: mt7622: add antsel
> pins/groups"). Include them in binding.
>
> Cc: Chuanhong Guo <gch981213@gmail.com>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> ---
> .../pinctrl/mediatek,mt7622-pinctrl.yaml | 18 ++++++++++++++++--
> 1 file changed, 16 insertions(+), 2 deletions(-)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2024-04-10 18:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 9:05 [PATCH 1/3] dt-bindings: pinctrl: mediatek: mt7622: fix array properties Rafał Miłecki
2024-04-08 9:05 ` [PATCH 2/3] dt-bindings: pinctrl: mediatek: mt7622: add "antsel" function Rafał Miłecki
2024-04-10 18:02 ` Rob Herring [this message]
2024-04-08 9:05 ` [PATCH 3/3] dt-bindings: pinctrl: mediatek: mt7622: add "base" reg Rafał Miłecki
2024-04-08 16:59 ` Conor Dooley
2024-04-10 18:01 ` [PATCH 1/3] dt-bindings: pinctrl: mediatek: mt7622: fix array properties Rob Herring
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=171277213295.820159.3023089832430236921.robh@kernel.org \
--to=robh@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gch981213@gmail.com \
--cc=hsinyi@chromium.org \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=rafal@milecki.pl \
--cc=sean.wang@kernel.org \
--cc=zajec5@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).