From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Mario Limonciello <superm1@kernel.org>
Cc: Hardik Prakash <hardikprakash.official@gmail.com>,
linux-i2c@vger.kernel.org, linux-gpio@vger.kernel.org,
wsa@kernel.org, andriy.shevchenko@intel.com, brgl@bgdev.pl,
basavaraj.natikar@amd.com, linusw@kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v8 2/2] i2c: designware: defer probe if child GpioInt controllers are not bound
Date: Fri, 29 May 2026 16:42:42 +0200 [thread overview]
Message-ID: <ahml4iX_FpI7Arwb@shikoro> (raw)
In-Reply-To: <4de80fd6-007e-484f-a7c9-17838ee5b1da@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 2388 bytes --]
On Fri, May 29, 2026 at 12:12:31PM +0200, Mario Limonciello wrote:
>
>
> On 5/29/26 12:08, Hardik Prakash wrote:
> > I2C controllers may have child devices with GpioInt resources that
> > depend on GPIO controllers to be 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
> > occur before the GPIO IRQ quirk in amd_gpio_probe() has run, causing:
> >
> > i2c_designware AMDI0010:02: i2c_dw_handle_tx_abort: lost arbitration
> >
> > Add a generic dependency check in i2c-designware that walks ACPI child
> > devices, identifies any GpioInt resources, resolves the referenced GPIO
> > controllers, and defers probe if those controllers are not yet bound.
> >
> > This ensures GPIO controllers complete initialization (including IRQ
> > setup and quirks) before I2C child enumeration begins, fixing the race
> > without device-specific quirks or DMI matching.
> >
> > The probe ordering race was confirmed via dynamic debug tracing:
> >
> > 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
> >
> > Suggested-by: Mario Limonciello <mario.limonciello@amd.com>
> > Signed-off-by: Hardik Prakash <hardikprakash.official@gmail.com>
> > Acked-by: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
> > Reviewed-by: Mario Limonciello (AMD) <superm1@kernel.org>
> > Assisted-by: Claude:claude-sonnet-4-6
> > Assisted-by: GPT-Codex:gpt-5.2-codex
> > Reported-by: kernel test robot <lkp@intel.com>
> > Closes: https://lore.kernel.org/oe-kbuild-all/202605240959.Kcf1lIg4-lkp@intel.com/
> > Link: https://bugzilla.kernel.org/show_bug.cgi?id=221494
>
> Fixes: 3812a9e84265a ("pinctrl-amd: enable IRQ for WACF2200 touchscreen on
> Lenovo Yoga 7 14AGP11")
No Rev-by from you, Mario?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-05-29 14:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 10:08 [PATCH v8 0/2] i2c: designware: fix WACF2200 touchscreen probe ordering Hardik Prakash
2026-05-29 10:08 ` [PATCH v8 1/2] Revert "pinctrl-amd: enable IRQ for WACF2200 touchscreen on Lenovo Yoga 7 14AGP11" Hardik Prakash
2026-05-29 10:12 ` Mario Limonciello
2026-05-29 20:34 ` Linus Walleij
2026-05-29 10:08 ` [PATCH v8 2/2] i2c: designware: defer probe if child GpioInt controllers are not bound Hardik Prakash
2026-05-29 10:12 ` Mario Limonciello
2026-05-29 14:42 ` Wolfram Sang [this message]
2026-05-29 14:43 ` Mario Limonciello
2026-05-29 14:43 ` Wolfram Sang
2026-05-29 20:46 ` Linus Walleij
2026-05-29 20:55 ` Wolfram Sang
2026-05-29 21:59 ` Linus Walleij
2026-05-29 22:46 ` Wolfram Sang
2026-05-29 10:13 ` [PATCH v8 0/2] i2c: designware: fix WACF2200 touchscreen probe ordering Mario Limonciello
2026-05-29 14:42 ` Wolfram Sang
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=ahml4iX_FpI7Arwb@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=andriy.shevchenko@intel.com \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=basavaraj.natikar@amd.com \
--cc=brgl@bgdev.pl \
--cc=hardikprakash.official@gmail.com \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=lkp@intel.com \
--cc=superm1@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