From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-gpio@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>
Subject: Re: [PATCH v1 1/2] gpiolib: acpi: Add fwnode name to the GPIO interrupt label
Date: Thu, 18 Apr 2024 07:49:07 +0300 [thread overview]
Message-ID: <20240418044907.GO112498@black.fi.intel.com> (raw)
In-Reply-To: <20240417103829.2324960-2-andriy.shevchenko@linux.intel.com>
On Wed, Apr 17, 2024 at 01:37:27PM +0300, Andy Shevchenko wrote:
> It's ambiguous to have a device-related index in the GPIO interrupt
> label as most of the devices will have it the same or very similar.
> Extend label with fwnode name for better granularity. It significantly
> reduces the scope of searching among devices.
Can you add an example here how it looks like before and after the
patch?
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> drivers/gpio/gpiolib-acpi.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpio/gpiolib-acpi.c b/drivers/gpio/gpiolib-acpi.c
> index 909113312a1b..0b0c8729fc6e 100644
> --- a/drivers/gpio/gpiolib-acpi.c
> +++ b/drivers/gpio/gpiolib-acpi.c
> @@ -1035,6 +1035,7 @@ struct gpio_desc *acpi_find_gpio(struct fwnode_handle *fwnode,
> int acpi_dev_gpio_irq_wake_get_by(struct acpi_device *adev, const char *con_id, int index,
> bool *wake_capable)
> {
> + struct fwnode_handle *fwnode = acpi_fwnode_handle(adev);
> int idx, i;
> unsigned int irq_flags;
> int ret;
> @@ -1044,7 +1045,7 @@ int acpi_dev_gpio_irq_wake_get_by(struct acpi_device *adev, const char *con_id,
> struct gpio_desc *desc;
>
> /* Ignore -EPROBE_DEFER, it only matters if idx matches */
> - desc = __acpi_find_gpio(acpi_fwnode_handle(adev), con_id, i, true, &info);
> + desc = __acpi_find_gpio(fwnode, con_id, i, true, &info);
> if (IS_ERR(desc) && PTR_ERR(desc) != -EPROBE_DEFER)
> return PTR_ERR(desc);
>
> @@ -1064,7 +1065,7 @@ int acpi_dev_gpio_irq_wake_get_by(struct acpi_device *adev, const char *con_id,
> acpi_gpio_update_gpiod_flags(&dflags, &info);
> acpi_gpio_update_gpiod_lookup_flags(&lflags, &info);
>
> - snprintf(label, sizeof(label), "GpioInt() %d", index);
> + snprintf(label, sizeof(label), "%pfwP GpioInt(%d)", fwnode, index);
> ret = gpiod_configure_flags(desc, label, lflags, dflags);
> if (ret < 0)
> return ret;
> --
> 2.43.0.rc1.1336.g36b5255a03ac
next prev parent reply other threads:[~2024-04-18 4:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 10:37 [PATCH v1 0/2] gpiolib: acpi: Improve IRQ labeling Andy Shevchenko
2024-04-17 10:37 ` [PATCH v1 1/2] gpiolib: acpi: Add fwnode name to the GPIO interrupt label Andy Shevchenko
2024-04-18 4:49 ` Mika Westerberg [this message]
2024-04-18 9:23 ` Andy Shevchenko
2024-04-18 9:33 ` Mika Westerberg
2024-04-18 10:00 ` Andy Shevchenko
2024-04-17 10:37 ` [PATCH v1 2/2] gpiolib: acpi: Set label for IRQ only lines Andy Shevchenko
2024-04-18 4:49 ` Mika Westerberg
2024-04-18 9:24 ` Andy Shevchenko
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=20240418044907.GO112498@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox