From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Hardik Prakash <hardikprakash.official@gmail.com>
Cc: linux-i2c@vger.kernel.org, linux-gpio@vger.kernel.org,
wsa@kernel.org, mario.limonciello@amd.com, brgl@bgdev.pl,
basavaraj.natikar@amd.com, linusw@kernel.org, nathan@kernel.org,
chaitanya.kumar.borah@intel.com
Subject: Re: [PATCH v12] i2c: designware: defer probe if child GpioInt controllers are not bound
Date: Thu, 16 Jul 2026 21:55:25 +0300 [thread overview]
Message-ID: <alkpHdM0wBw6_DiX@ashevche-desk.local> (raw)
In-Reply-To: <20260716113055.41319-1-hardikprakash.official@gmail.com>
On Thu, Jul 16, 2026 at 05:00:55PM +0530, Hardik Prakash wrote:
> I2C controllers may have child devices with GpioInt resources that
> depend on GPIO controllers being fully initialized. If the I2C
> controller probes and enumerates children before the referenced GPIO
> controller has completed probe, GPIO interrupts may not be properly
> configured, leading to device failures.
>
> On Lenovo Yoga 7 14AGP11, the WACF2200 touchscreen (child of
> AMDI0010:02) has a GpioInt resource pointing to GPIO 157 on the
> pinctrl-amd controller (AMDI0030:00). When i2c-designware probes
> AMDI0010:02 before pinctrl-amd finishes initializing, I2C transactions
> fail with lost arbitration errors:
>
> 0.285952 amd_gpio_probe: registering gpiochip <- GPIO chip visible
> 0.287121 amd_gpio_probe: requesting parent IRQ <- probe still running
> 0.301454 AMDI0010:02 dw_i2c_plat_probe: start <- races here
> 2.348157 lost arbitration
>
> Add a dependency check that walks ACPI child devices and defers probe
> until any referenced GPIO controller is bound.
It's utterly wrong patch. Actually this whole saga shows how AI wastes
more time than gains a productivity.
...
> gpio_dev = gpio_device_to_device(gdev)->parent;
> - scoped_guard(device, gpio_dev) {
> - if (!device_is_bound(gpio_dev))
> - return -EPROBE_DEFER; /* controller not bound yet: abort walk */
> - }
> + guard(device)(gpio_dev);
When use guard()(), make sure it has a blank lines before and after, so it's
visible as a separate entity.
> + if (!device_is_bound(gpio_dev))
> + return -EPROBE_DEFER; /* controller not bound yet: abort walk */
>
...
So, make sure v13 is a real patch.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-07-16 18:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 11:30 [PATCH v12] i2c: designware: defer probe if child GpioInt controllers are not bound Hardik Prakash
2026-07-16 14:10 ` Bartosz Golaszewski
2026-07-16 18:50 ` Andy Shevchenko
2026-07-17 7:40 ` Bartosz Golaszewski
2026-07-16 18:55 ` Andy Shevchenko [this message]
2026-07-17 4:48 ` Hardik Prakash
2026-07-17 6:36 ` 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=alkpHdM0wBw6_DiX@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=basavaraj.natikar@amd.com \
--cc=brgl@bgdev.pl \
--cc=chaitanya.kumar.borah@intel.com \
--cc=hardikprakash.official@gmail.com \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=nathan@kernel.org \
--cc=wsa@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