From: Yemike Abhilash Chandra <y-abhilashchandra@ti.com>
To: Linus Walleij <linusw@kernel.org>
Cc: <robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<nm@ti.com>, <vigneshr@ti.com>, <kristo@kernel.org>,
<brgl@kernel.org>, <linux-gpio@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<afd@ti.com>, <u-kumar1@ti.com>
Subject: Re: [PATCH 2/3] pinctrl: ti: Add TDA54 pin controller driver
Date: Tue, 13 Oct 2026 11:30:20 +0530 [thread overview]
Message-ID: <7f734f4a-d54a-46b0-947c-eb7cda00fafa@ti.com> (raw)
In-Reply-To: <CAD++jLm462gGw38acBk1VzwKZq0WE6xfFUKoMsoiVxy4iqfEtg@mail.gmail.com>
Hi Linus,
On 02/10/26 02:22, Linus Walleij wrote:
> Hi Yemike,
>
> thanks for your patch!
>
Thank you for the review and apologies for the delayed response.
> On Wed, Sep 30, 2026 at 11:21 AM Yemike Abhilash Chandra
> <y-abhilashchandra@ti.com> wrote:
>
>> The TDA54 pin controller splits the pad configuration across two registers:
>> PADCFGA holds the mux mode and the functional pin configuration, PADCFGB
>> holds the wakeup and retention configuration. The controller also supports
>> two proxy addressing regions and claiming of registers. A register claimed
>> through proxy 1 becomes read-only at proxy 0 and can only be written
>> through proxy 1.
>>
>> Add support for the pin controller in the TI TDA54 SoC.
>>
>> Signed-off-by: Yemike Abhilash Chandra <y-abhilashchandra@ti.com>
>
> Overall this looks pretty nice.
>
Thanks !!
> Check the Sashiko reviews, there is always something
> interesting there.
>
Yes, found a few interesting things there. Will reply to that
separately.
>> +config PINCTRL_TDA54
>> + tristate "TI TDA54 pinctrl driver"
>> + depends on OF && (ARCH_K3 || COMPILE_TEST)
>> + select GENERIC_PINCTRL_GROUPS
>> + select GENERIC_PINMUX_FUNCTIONS
>> + select GENERIC_PINCONF
>
> Just
>
> select GENERIC_PINCTRL
>
> and you get all three.
>
Done. Thanks.
>> +static int tda54_dt_node_to_map(struct pinctrl_dev *pctldev,
>> + struct device_node *np,
>> + struct pinctrl_map **maps,
>> + unsigned int *num_maps)
>
> What is so unique here that you need your own node to map function?
>
> Can't you use pinctrl_generic_pinmux_dt_node_to_map()?
>
I can, thanks for the pointer. I wasn't aware of the generic helper.
Switched to pinctrl_generic_pinmux_dt_node_to_map() and it works fine.
Thanks and regards,
Yemike Abhilash Chandra
> Please consult the code in drivers/pinctrl/pinctrl-generic.c.
>
> Yours,
> Linus Walleij
next prev parent reply other threads:[~2026-10-13 6:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 9:20 [PATCH 0/3] Add pin controller support for TI TDA54 SoC Yemike Abhilash Chandra
2026-09-30 9:20 ` [PATCH 1/3] dt-bindings: pinctrl: Add TI TDA54 pin controller Yemike Abhilash Chandra
2026-10-01 21:10 ` Linus Walleij
2026-10-01 21:26 ` Conor Dooley
2026-09-30 9:20 ` [PATCH 2/3] pinctrl: ti: Add TDA54 pin controller driver Yemike Abhilash Chandra
2026-10-01 20:52 ` Linus Walleij
2026-10-13 6:00 ` Yemike Abhilash Chandra [this message]
2026-10-11 23:11 ` Uwe Kleine-König
2026-10-13 6:09 ` Yemike Abhilash Chandra
2026-09-30 9:20 ` [PATCH 3/3] arm64: dts: ti: Add TDA54 pinctrl header Yemike Abhilash Chandra
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=7f734f4a-d54a-46b0-947c-eb7cda00fafa@ti.com \
--to=y-abhilashchandra@ti.com \
--cc=afd@ti.com \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.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=robh@kernel.org \
--cc=u-kumar1@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