X86 platform drivers
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Andy Shevchenko <andy@kernel.org>,
	 Hans de Goede <johannes.goede@oss.qualcomm.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	 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: Thu, 3 Sep 2026 14:54:51 +0300 (EEST)	[thread overview]
Message-ID: <74f149f6-caa8-db4e-9ef4-5c15b7a5845f@linux.intel.com> (raw)
In-Reply-To: <apcRAvoHkh9blDwK@black.igk.intel.com>

On Tue, 1 Sep 2026, Andy Shevchenko wrote:

> 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.
> 
> ...
> 
> > 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));
> 
> It doesn't look like an auto cleaning pointer, so let's make a declaration
> outside of the code?
> 
> > +		if (!phys_dev)
> > +			return dev_err_probe(parent,
> > +					     -ENODEV, "No physical device for ACPI GPIO dev: %s\n",
> > +					     (*swnode)->name);
> 
> Hmm... Why not %pfwP?

Hi Hans,

I'm waiting for v2.

-- 
 i.


  parent reply	other threads:[~2026-09-03 11:55 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
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 [this message]
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=74f149f6-caa8-db4e-9ef4-5c15b7a5845f@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=andy@kernel.org \
    --cc=brgl@kernel.org \
    --cc=dmitry.torokhov@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox