From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Hans de Goede <johannes.goede@oss.qualcomm.com>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Bartosz Golaszewski" <brgl@kernel.org>,
"Linus Walleij" <linusw@kernel.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH] platform/x86: x86-android-tablets: fix gpio_secondary_fwnode_init() not working
Date: Mon, 31 Aug 2026 13:22:32 -0700 [thread overview]
Message-ID: <apXgib0baybxwWSc@google.com> (raw)
In-Reply-To: <20260831201157.36397-1-johannes.goede@oss.qualcomm.com>
On Mon, Aug 31, 2026 at 10:11:57PM +0200, Hans de Goede wrote:
> acpi_bus_find_device_by_name() call returns a pointer to the device object
> on the ACPI bus, aka the ACPI companion device.
>
> gpio_secondary_fwnode_init() then continues with setting the secondary
> fwnode on this device. But this is not the actual physical device for
> the GPIO controller (e.g. the GPIO controller platform bus device).
>
> This mismatch is causing GPIO lookups by secondary fwnode to not work.
>
> Modify gpio_secondary_fwnode_init() to instead set the secondary fwnode
> of the first physical device associated with the ACPI companion device.
>
> This fixes the GPIO lookups not working.
Nice find, thank you!
>
> Fixes: 1448c2d2ca5c ("platform/x86: x86-android-tablets: enable fwnode matching of GPIO chips")
> Signed-off-by: Hans de Goede <johannes.goede@oss.qualcomm.com>
> ---
> drivers/platform/x86/x86-android-tablets/core.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/platform/x86/x86-android-tablets/core.c b/drivers/platform/x86/x86-android-tablets/core.c
> index b028af1c9942..1706287fd136 100644
> --- a/drivers/platform/x86/x86-android-tablets/core.c
> +++ b/drivers/platform/x86/x86-android-tablets/core.c
> @@ -417,9 +417,15 @@ static int gpio_secondary_fwnode_init(struct device *parent,
> if (WARN_ON(!fwnode))
> return -ENOENT;
>
> - set_secondary_fwnode(dev, fwnode);
> + struct device *phys_dev = acpi_get_first_physical_node(to_acpi_device(dev));
> + if (!phys_dev)
> + return dev_err_probe(parent,
> + -ENODEV, "No physical device for ACPI GPIO dev: %s\n",
> + (*swnode)->name);
>
> - ret = devm_add_action_or_reset(parent, gpio_secondary_unset, get_device(dev));
> + set_secondary_fwnode(phys_dev, fwnode);
> +
> + ret = devm_add_action_or_reset(parent, gpio_secondary_unset, get_device(phys_dev));
I am surprised that acpi_get_first_physical_node() does not bump up
refcount of the device...
> if (ret)
> return ret;
This leaks refcount on error though...
> }
Thanks.
--
Dmitry
next prev parent reply other threads:[~2026-08-31 20:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 20:11 [PATCH] platform/x86: x86-android-tablets: fix gpio_secondary_fwnode_init() not working Hans de Goede
2026-08-31 20:22 ` Dmitry Torokhov [this message]
2026-08-31 20:28 ` Hans de Goede
2026-08-31 20:34 ` Dmitry Torokhov
[not found] ` <apcRAvoHkh9blDwK@black.igk.intel.com>
2026-09-03 11:54 ` Ilpo Järvinen
2026-09-08 17:51 ` Hans de Goede
2026-09-08 19:04 ` Ilpo Järvinen
2026-09-09 14:11 ` 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=apXgib0baybxwWSc@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=andy@kernel.org \
--cc=brgl@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=johannes.goede@oss.qualcomm.com \
--cc=linusw@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael@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.