Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: Khristine Andreea Barbulescu <khristineandreea.barbulescu@oss.nxp.com>
To: Linus Walleij <linusw@kernel.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Chester Lin <chester62515@gmail.com>,
	Matthias Brugger <mbrugger@suse.com>,
	Ghennadi Procopciuc <ghennadi.procopciuc@nxp.com>,
	Larisa Grigore <larisa.grigore@nxp.com>,
	Lee Jones <lee@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	Dong Aisheng <aisheng.dong@nxp.com>, Jacky Bai <ping.bai@nxp.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Srinivas Kandagatla <srini@kernel.org>,
	Alberto Ruiz <aruizrui@redhat.com>,
	Christophe Lizzi <clizzi@redhat.com>,
	devicetree@vger.kernel.org, Enric Balletbo <eballetb@redhat.com>,
	Eric Chanudet <echanude@redhat.com>,
	imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	NXP S32 Linux Team <s32@nxp.com>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Vincent Guittot <vincent.guittot@linaro.org>
Subject: Re: [PATCH v9 6/7] pinctrl: s32cc: implement GPIO functionality
Date: Fri, 8 May 2026 12:06:48 +0300	[thread overview]
Message-ID: <704e9e7b-0f45-4ed3-a686-9e20056eab2a@oss.nxp.com> (raw)
In-Reply-To: <CAD++jLnk4q7L_cFzz+1gKkAqwhv=TW1_XSepuii7b_PHF7EPqQ@mail.gmail.com>

On 5/5/2026 3:46 PM, Linus Walleij wrote:
> [You don't often get email from linusw@kernel.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
> 
> Hi Khristine,
> 
> thanks for your patch!
> 
> On Mon, May 4, 2026 at 3:12 PM Khristine Andreea Barbulescu
> <khristineandreea.barbulescu@oss.nxp.com> wrote:
> 
>> From: Andrei Stefanescu <andrei.stefanescu@oss.nxp.com>
>>
>> Add basic GPIO functionality (request, free, get, set) for
>> the existing pinctrl SIUL2 driver since the hardware for
>> pinctrl&GPIO is tightly coupled.
>>
>> The updated SIUL2 block groups pinctrl, GPIO data access
>> and interrupt control within the same hardware unit.
>> The SIUL2 driver is therefore structured as a monolithic
>> pinctrl/GPIO driver.
>>
>> This change came as a result of upstream review in the
>> following series:
>> https://lore.kernel.org/linux-gpio/20260120115923.3463866-4-khristineandreea.barbulescu@oss.nxp.com/T/#m543c9edbdde74bdc68b6a2364e8b975356c33043
>>
>> Support both SIUL2 DT layouts:
>> - legacy pinctrl-only binding
>> - extended pinctrl/GPIO/irqchip binding
>>
>> Also, remove pinmux_ops which are no longer needed.
>>
>> Signed-off-by: Andrei Stefanescu <andrei.stefanescu@oss.nxp.com>
>> Signed-off-by: Khristine Andreea Barbulescu <khristineandreea.barbulescu@oss.nxp.com>
> 
> Same comment about GPIO_REGMAP here.
> 
> Maybe this has been brought up before so it's just sigh rolleyes,
> but my memory is short.
> 
> Of course gpio regmap conversions can be done later, after this,
> but the problem with such things is that they tend to end up on
> the back burner and never actually get done then.
> 
> Yours,
> Linus Walleij


Hi Linus,

Thank you for the suggestion!

I think the gpio-regmap model could fit the SIUL2 PGPDO/PGPDI
data path, so the get/set operations could potentially be
refactored in that direction as a follow-up.

However, I don't think the current driver is a good fit for
a full gpio-regmap conversion. Direction and GPIO mux are
handled through MSCR/pinctrl state (IBE/OBE/SSS), and the GPIO
logic spans multiple register regions across two SIUL2 instances.

A conversion would require stronger separation between
GPIO and pinctrl, leaving mux restoration entirely
to the pinctrl subsystem.

Would it be reasonable to keep the current approach for now
and revisit gpio-regmap later if needed?

Best regards,
Khristine






  reply	other threads:[~2026-05-08  9:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-04 13:11 [PATCH v9 0/7] gpio: siul2-s32g2: add initial GPIO driver Khristine Andreea Barbulescu
2026-05-04 13:11 ` [PATCH v9 1/7] pinctrl: s32cc: use dev_err_probe() and improve error messages Khristine Andreea Barbulescu
2026-05-04 14:39   ` Bartosz Golaszewski
2026-05-04 13:11 ` [PATCH v9 2/7] pinctrl: s32cc: add/fix some comments Khristine Andreea Barbulescu
2026-05-04 14:41   ` Bartosz Golaszewski
2026-05-04 13:11 ` [PATCH v9 3/7] pinctrl: s32cc: remove inline specifiers Khristine Andreea Barbulescu
2026-05-04 14:41   ` Bartosz Golaszewski
2026-05-04 13:11 ` [PATCH v9 4/7] pinctrl: s32cc: change to "devm_pinctrl_register_and_init" Khristine Andreea Barbulescu
2026-05-04 13:11 ` [PATCH v9 5/7] dt-bindings: pinctrl: s32g2-siul2: describe GPIO and EIRQ resources Khristine Andreea Barbulescu
2026-05-05  6:36   ` Krzysztof Kozlowski
2026-05-08  9:09     ` Khristine Andreea Barbulescu
2026-05-04 13:11 ` [PATCH v9 6/7] pinctrl: s32cc: implement GPIO functionality Khristine Andreea Barbulescu
2026-05-04 14:49   ` Bartosz Golaszewski
2026-05-05 12:46   ` Linus Walleij
2026-05-08  9:06     ` Khristine Andreea Barbulescu [this message]
2026-05-04 13:11 ` [PATCH v9 7/7] arm64: dts: s32g: describe GPIO and EIRQ resources in SIUL2 pinctrl node Khristine Andreea Barbulescu

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=704e9e7b-0f45-4ed3-a686-9e20056eab2a@oss.nxp.com \
    --to=khristineandreea.barbulescu@oss.nxp.com \
    --cc=aisheng.dong@nxp.com \
    --cc=aruizrui@redhat.com \
    --cc=brgl@bgdev.pl \
    --cc=chester62515@gmail.com \
    --cc=clizzi@redhat.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=eballetb@redhat.com \
    --cc=echanude@redhat.com \
    --cc=festevam@gmail.com \
    --cc=ghennadi.procopciuc@nxp.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=larisa.grigore@nxp.com \
    --cc=lee@kernel.org \
    --cc=linus.walleij@linaro.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=mbrugger@suse.com \
    --cc=ping.bai@nxp.com \
    --cc=rafael@kernel.org \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=s32@nxp.com \
    --cc=shawnguo@kernel.org \
    --cc=srini@kernel.org \
    --cc=vincent.guittot@linaro.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