From: "Rob Herring (Arm)" <robh@kernel.org>
To: Bryan Brattlof <bb@ti.com>
Cc: Nishanth Menon <nm@ti.com>, Conor Dooley <conor+dt@kernel.org>,
Tony Lindgren <tony@atomide.com>,
linux-gpio@vger.kernel.org, Andrew Davis <afd@ti.com>,
linux-arm-kernel@lists.infradead.org,
Sascha Hauer <s.hauer@pengutronix.de>,
Tero Kristo <kristo@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
devicetree@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 2/4] dt-bindings: pinctrl: pinctrl-single: add ti,am62l-padconf compatible
Date: Mon, 15 Sep 2025 21:53:36 -0500 [thread overview]
Message-ID: <175799121579.3582107.882281471207864281.robh@kernel.org> (raw)
In-Reply-To: <20250912-am62lx-v6-2-29d5a6c60512@ti.com>
On Fri, 12 Sep 2025 10:40:41 -0500, Bryan Brattlof wrote:
> Add the "ti,am62l-padconf" compatible to allow for some changes in the
> driver in the future when needed.
>
> Signed-off-by: Bryan Brattlof <bb@ti.com>
> ---
> Documentation/devicetree/bindings/pinctrl/pinctrl-single.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
Acked-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2025-09-16 2:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 15:40 [PATCH v6 0/4] arm64: dts: ti: introduce basic support for the AM62L Bryan Brattlof
2025-09-12 15:40 ` [PATCH v6 1/4] dt-bindings: arm: ti: Add binding for AM62L SoCs Bryan Brattlof
2025-10-15 12:14 ` Dhruva Gole
2025-09-12 15:40 ` [PATCH v6 2/4] dt-bindings: pinctrl: pinctrl-single: add ti,am62l-padconf compatible Bryan Brattlof
2025-09-16 2:53 ` Rob Herring (Arm) [this message]
2025-10-13 10:11 ` Linus Walleij
2025-09-12 15:40 ` [PATCH v6 3/4] arm64: dts: ti: k3-am62l: add initial infrastructure Bryan Brattlof
2025-09-12 17:19 ` Andrew Davis
2025-09-12 19:24 ` Bryan Brattlof
2025-09-12 15:40 ` [PATCH v6 4/4] arm64: dts: ti: k3-am62l: add initial reference board file Bryan Brattlof
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=175799121579.3582107.882281471207864281.robh@kernel.org \
--to=robh@kernel.org \
--cc=afd@ti.com \
--cc=bb@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.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-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=s.hauer@pengutronix.de \
--cc=tony@atomide.com \
--cc=vigneshr@ti.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