From: Hans de Goede <hansg@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: "Santosh Kumar Yadav" <santoshkumar.yadav@barco.com>,
"Peter Korsgaard" <peter.korsgaard@barco.com>,
"Bartosz Golaszewski" <bartosz.golaszewski@linaro.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Arnd Bergmann" <arnd@arndb.de>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/x86: barco-p50-gpio: use software nodes for gpio-leds/keys
Date: Mon, 11 Aug 2025 16:20:33 +0200 [thread overview]
Message-ID: <7c2d08e3-d1e2-433e-b726-307246ab17e9@kernel.org> (raw)
In-Reply-To: <aJnlnx2qF6P61jJN@smile.fi.intel.com>
Hi Andy, Dmitry,
On 11-Aug-25 2:44 PM, Andy Shevchenko wrote:
> On Sun, Aug 10, 2025 at 09:31:37PM -0700, Dmitry Torokhov wrote:
>> In preparation of dropping support for legacy GPIO API from gpio-keys
>> switch the driver to use software nodes/properties to describe
>> GPIO-connected LED and button.
>
> ...
>
>> #include <linux/delay.h>
>> +#include <linux/dev_printk.h>
>> #include <linux/dmi.h>
>> #include <linux/err.h>
>> #include <linux/io.h>
>
>> #include <linux/leds.h>
>> #include <linux/module.h>
>> #include <linux/platform_device.h>
>> -#include <linux/gpio_keys.h>
>> #include <linux/gpio/driver.h>
>> #include <linux/gpio/machine.h>
>> -#include <linux/input.h>
>
>> +#include <linux/gpio/property.h>
>> +#include <linux/input-event-codes.h>
>> +#include <linux/property.h>
>
> The idea of sorting here is to have more generic first and then more specific
> (per subsystem in use) groups of headers. So with your change it should look
> like
>
> #include <linux/delay.h>
> #include <linux/dev_printk.h>
> #include <linux/dmi.h>
> #include <linux/err.h>
> #include <linux/io.h>
> ...
> #include <linux/leds.h>
> #include <linux/module.h>
> #include <linux/platform_device.h>
> #include <linux/property.h>
>
> #include <linux/gpio/driver.h>
> #include <linux/gpio/machine.h>
> #include <linux/gpio/property.h>
>
> #include <linux/input-event-codes.h>
>
> (I also added blank lines to make it more explicit)
>
> ...
>
> Otherwise LGTM as here it looks like we establish platform device ourselves and
> hence no need some additional magic Hans mentioned in the other series.
Not entirely like with the x86-android-tablets patches this
declares a software-node for the gpiochip:
static const struct software_node gpiochip_node = {
.name = DRIVER_NAME,
};
and registers that node, but nowhere does it actually
get assigned to the gpiochip.
This is going to need a line like this added to probe():
p50->gc.fwnode = software_node_fwnode(&gpiochip_node);
note the software_node_fwnode() call MUST be made after
registering the software-nodes (group).
Other then needing this single line things are indeed
much easier when the code containing the software
properties / nodes is the same code as which is
registering the gpiochip.
Regards,
Hans
next prev parent reply other threads:[~2025-08-11 14:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 4:31 [PATCH] platform/x86: barco-p50-gpio: use software nodes for gpio-leds/keys Dmitry Torokhov
2025-08-11 12:44 ` Andy Shevchenko
2025-08-11 14:20 ` Hans de Goede [this message]
2025-08-11 15:45 ` Andy Shevchenko
2025-08-11 15:49 ` Dmitry Torokhov
2025-08-11 16:01 ` Andy Shevchenko
2025-08-11 16:11 ` Dmitry Torokhov
2025-08-11 17:40 ` Hans de Goede
2025-08-11 17:44 ` Hans de Goede
2025-08-11 17:59 ` Dmitry Torokhov
2025-08-12 9:47 ` Hans de Goede
2025-09-08 12:48 ` Ilpo Järvinen
2025-09-10 10:56 ` Hans de Goede
2025-08-11 19:58 ` Andy Shevchenko
2025-09-24 12:58 ` Ilpo Järvinen
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=7c2d08e3-d1e2-433e-b726-307246ab17e9@kernel.org \
--to=hansg@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=bartosz.golaszewski@linaro.org \
--cc=dmitry.torokhov@gmail.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.korsgaard@barco.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=santoshkumar.yadav@barco.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 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.