From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Cc: "Peter Tyser" <ptyser@xes-inc.com>, "Lee Jones" <lee@kernel.org>,
"Hans de Goede" <hansg@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org, brgl@kernel.org
Subject: Re: [PATCH 0/2] platform/x86: meraki-mx100: create and use real software node links
Date: Fri, 13 Feb 2026 11:19:52 +0200 [thread overview]
Message-ID: <aY7suPDqjQYXKmTc@smile.fi.intel.com> (raw)
In-Reply-To: <20260213-meraki-swnodes-v1-0-8e032693456c@oss.qualcomm.com>
On Fri, Feb 13, 2026 at 09:25:23AM +0100, Bartosz Golaszewski wrote:
> Meraki-mx100 is one of the GPIOLIB users that abuses the software node
> API by setting up a dummy software node without any logical link to the
> GPIO controller it wants to use and uses the fact that the GPIO core
> matches the controller's label against the swnode's name to make the
> lookup work.
>
> We want to remove this behavior from GPIOLIB in favor of actual matching
> of firmware nodes but that would break this user. This series creates
> a real software node in the MFD driver and references it from the meraki
> driver.
Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> This can be done in two patches and stay bisectable as the software
> nodes, despite having the same name, will have different parents so
> there are no kobject issues.
>
> Merging: this should probably be acked by Hans or Ilpo and go through
> the MFD tree for v7.1.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-02-13 9:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 8:25 Bartosz Golaszewski
2026-02-13 8:25 ` [PATCH 1/2] mfd: lpc_ich: expose the GPIO controller cell's software node Bartosz Golaszewski
2026-02-13 9:16 ` Andy Shevchenko
2026-02-16 8:51 ` Bartosz Golaszewski
2026-02-16 9:17 ` Andy Shevchenko
2026-02-16 10:15 ` Bartosz Golaszewski
2026-02-17 7:56 ` Andy Shevchenko
2026-02-13 8:25 ` [PATCH 2/2] platform/x86: meraki-mx100: use real software node references Bartosz Golaszewski
2026-02-13 9:19 ` Andy Shevchenko [this message]
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=aY7suPDqjQYXKmTc@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=ptyser@xes-inc.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
Powered by JetHome