From: "Kumar, Udit" <u-kumar1@ti.com>
To: Akashdeep Kaur <a-kaur@ti.com>, <nm@ti.com>, <vigneshr@ti.com>,
<kristo@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <sebin.francis@ti.com>, <k-willis@ti.com>, <u-kumar1@ti.com>
Subject: Re: [PATCH v3] arm64: dts: ti: k3-pinctrl: Add virtual GPIO select mux macros
Date: Fri, 25 Sep 2026 21:45:03 +0530 [thread overview]
Message-ID: <09d30f40-f87b-4d33-af97-de8c1536f22e@ti.com> (raw)
In-Reply-To: <20260922102629.3707296-1-a-kaur@ti.com>
On 9/22/2026 3:56 PM, Akashdeep Kaur wrote:
> Add virtual GPIO select mux macros for configuring the vgpio_sel
> field in pad configuration registers. This field selects GPIO
> controller routing. The meaning of each value is SoC-specific -
> refer to the Technical Reference Manual for the specific SoC.
>
> For example, on AM62L, values 0 and 1 select GPIO controller 0 and 2
> respectively, while on J784S4, values 0-3 select different GPIO
> controller pairs based on the pin. Pad configuration register
> field details can be found in each SoC's Technical Reference
> Manual (example: section 14.2.1.2.1 of [1]).
>
> [1] AM62L TRM: https://www.ti.com/lit/ug/sprujb4a/sprujb4a.pdf
>
> Signed-off-by: Akashdeep Kaur <a-kaur@ti.com>
> ---
>
> K3 SoC vgpio_sel Field Audit:
> All supported SoCs use bits [5:4] for vgpio_sel field.
>
> Supported SoCs:
> - J721E, J721S2, J7200, J784S4: 4 options (0-3) for MAIN GPIO,
> 2 options (0-1) for WKUP GPIO
> - AM62L: 2 options (0-1)
>
> Not supported (field reserved):
> - AM62X, AM62AX, AM62PX, AM62D, AM64X, AM65X, J722S
>
> Changes in v3:
> - Use tabs for macro alignment
> - Add comment warning that field is SoC specific
> - Link to v2: https://lore.kernel.org/all/20260921063505.3986565-1-a-kaur@ti.com/
>
> Changes in v2:
> - Add all four PIN_VGPIO_SEL[0-3] macros instead of just two
> - Use generic value-based naming to support all K3 SoCs
> - Update commit message to clarify SoC-specific behavior
> - Link to v1: https://lore.kernel.org/all/20260917111539.3844577-1-a-kaur@ti.com/
>
> ---
> arch/arm64/boot/dts/ti/k3-pinctrl.h | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-pinctrl.h b/arch/arm64/boot/dts/ti/k3-pinctrl.h
> index 4491898d8294..e8ca69a97b65 100644
> --- a/arch/arm64/boot/dts/ti/k3-pinctrl.h
> +++ b/arch/arm64/boot/dts/ti/k3-pinctrl.h
> @@ -8,6 +8,7 @@
> #ifndef DTS_ARM64_TI_K3_PINCTRL_H
> #define DTS_ARM64_TI_K3_PINCTRL_H
>
> +#define VGPIO_SEL_SHIFT (4)
> #define WKUP_LVL_EN_SHIFT (7)
> #define WKUP_LVL_POL_SHIFT (8)
> #define DEBOUNCE_SHIFT (11)
> @@ -111,6 +112,15 @@
> #define PIN_WKUP_EN_LEVEL_HIGH (WKUP_ENABLE | WKUP_ON_LEVEL | WKUP_LEVEL_HIGH)
> #define PIN_WKUP_EN (WKUP_ENABLE | WKUP_ON_EDGE)
>
> +/*
> + * SoC-specific field - Refer to the SoC Technical Reference Manual to
> + * determine which GPIO controller each value selects.
> + */
> +#define PIN_VGPIO_SEL0 (0 << VGPIO_SEL_SHIFT)
> +#define PIN_VGPIO_SEL1 (1 << VGPIO_SEL_SHIFT)
> +#define PIN_VGPIO_SEL2 (2 << VGPIO_SEL_SHIFT)
> +#define PIN_VGPIO_SEL3 (3 << VGPIO_SEL_SHIFT)
Reviewed-by: Udit Kumar <u-kumar1@ti.com>
> +
> /* Default mux configuration for gpio-ranges to use with pinctrl */
> #define PIN_GPIO_RANGE_IOPAD (PIN_INPUT | 7)
>
next prev parent reply other threads:[~2026-09-25 16:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 10:26 [PATCH v3] arm64: dts: ti: k3-pinctrl: Add virtual GPIO select mux macros Akashdeep Kaur
2026-09-25 16:15 ` Kumar, Udit [this message]
2026-09-28 17:20 ` Nishanth Menon
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=09d30f40-f87b-4d33-af97-de8c1536f22e@ti.com \
--to=u-kumar1@ti.com \
--cc=a-kaur@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=k-willis@ti.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=sebin.francis@ti.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