From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: "Bartosz Golaszewski" <brgl@kernel.org>,
"Bartosz Golaszewski" <bartosz.golaszewski@oss.qualcomm.com>,
"Linus Walleij" <linusw@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Arnd Bergmann" <arnd@kernel.org>,
"Hans de Goede" <hansg@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Dan Carpenter" <dan.carpenter@linaro.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] gpio: swnode: restore the swnode-name-against-chip-label matching
Date: Thu, 19 Feb 2026 08:53:36 +0200 [thread overview]
Message-ID: <aZazcDYdoZBzuH6f@smile.fi.intel.com> (raw)
In-Reply-To: <aZYPv1_kWQd9OdHD@google.com>
On Wed, Feb 18, 2026 at 11:22:07AM -0800, Dmitry Torokhov wrote:
> On Wed, Feb 18, 2026 at 07:08:22PM +0100, Bartosz Golaszewski wrote:
> > On Wed, Feb 18, 2026 at 6:15 PM Dmitry Torokhov
> > <dmitry.torokhov@gmail.com> wrote:
> > > On Wed, Feb 18, 2026 at 09:42:28AM +0100, Bartosz Golaszewski wrote:
> > > > On Wed, Feb 18, 2026 at 1:31 AM Dmitry Torokhov
> > > > <dmitry.torokhov@gmail.com> wrote:
> > > > > On Wed, Feb 11, 2026 at 09:53:13AM +0100, Bartosz Golaszewski wrote:
> > > > > > Using the remote firmware node for software node lookup is the right
> > > > > > thing to do. The GPIO controller we want to resolve should have the
> > > > > > software node we scooped out of the reference attached to it. However,
> > > > > > there are existing users who abuse the software node API by creating
> > > > > > dummy swnodes whose name is set to the expected label string of the GPIO
> > > > > > controller whose pins they want to control and use them in their local
> > > > > > swnode references as GPIO properties.
> > > > > >
> > > > > > This used to work when we compared the software node's name to the
> > > > > > chip's label. When we switched to using a real fwnode lookup, these
> > > > > > users broke down because the firmware nodes in question were never
> > > > > > attached to the controllers they were looking for.
> > > > > >
> > > > > > Restore the label matching as a fallback to fix the broken users but add
> > > > > > a big FIXME urging for a better solution.
> > > > > >
> > > > > > Cc: stable@vger.kernel.org # v6.18, v6.19
> > > > > > Fixes: 216c12047571 ("gpio: swnode: allow referencing GPIO chips by firmware nodes")
> > > > > > Link: https://lore.kernel.org/all/aYkdKfP5fg6iywgr@jekhomev/
> > > > > > Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > > > > > Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
> > > > > > ---
> > > > > > Changes in v2:
> > > > > > - check if gdev_node and gdev_node->name are not NULL before trying to
> > > > > > match the label (Hans & Dan)
> > > > > > - use the right link
> > > > > > - collect tags
> > > > > >
> > > > > > drivers/gpio/gpiolib-swnode.c | 19 +++++++++++++++++++
> > > > > > 1 file changed, 19 insertions(+)
> > > > > >
> > > > > > diff --git a/drivers/gpio/gpiolib-swnode.c b/drivers/gpio/gpiolib-swnode.c
> > > > > > index 21478b45c127d..0d7f3f09a0b4b 100644
> > > > > > --- a/drivers/gpio/gpiolib-swnode.c
> > > > > > +++ b/drivers/gpio/gpiolib-swnode.c
> > > > > > @@ -42,6 +42,25 @@ static struct gpio_device *swnode_get_gpio_device(struct fwnode_handle *fwnode)
> > > > > >
> > > > > > fwnode_lookup:
> > > > > > gdev = gpio_device_find_by_fwnode(fwnode);
> > > > >
> > > > > By the way, should we extend gpio_device_find_by_fwnode() to use both
> > > > > primary and secondary nodes?
> > > > >
> > > >
> > > > That's already done on a higher lever for all fwnodes in gpiod_fwnode_lookup().
> > >
> > > How exactly? I am not talking about checking secondary node for the
> > > fwnode that is used in the reference, I am talking about secondary
> > > fwnode that might be assigned to the gpio chip and you need to check
> > > both primary and secondary if they match with the fwnode that you call
> > > gpio_device_find_by_fwnode() with.
> > >
> >
> > Right, I didn't quite get it. I was surprised to find out
> > device_match_fwnode() - which we use in gpiolib - does not do it
> > already. I'm wondering if this is something we should change in device
> > core or only locally.
>
> Yes, I think so (change in driver core). There is only a handful of
> calls to device_match_fwnode() that they can be audited to make sure the
> conversion is safe.
I believe there was already similar discussion and IIRC conclusion was to
distinguish current device_match_fwnode() with something new that will check
also secondary one. This way we can in a usual way convert drivers one-by-one
if even required.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-02-19 6:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 8:53 [PATCH v2] gpio: swnode: restore the swnode-name-against-chip-label matching Bartosz Golaszewski
2026-02-11 11:57 ` Hans de Goede
2026-02-18 0:31 ` Dmitry Torokhov
2026-02-18 8:42 ` Bartosz Golaszewski
2026-02-18 17:15 ` Dmitry Torokhov
2026-02-18 18:08 ` Bartosz Golaszewski
2026-02-18 19:22 ` Dmitry Torokhov
2026-02-19 6:53 ` Andy Shevchenko [this message]
2026-02-18 8:43 ` Bartosz Golaszewski
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=aZazcDYdoZBzuH6f@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=arnd@kernel.org \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.