Linux GPIO subsystem development
 help / color / mirror / Atom feed
From: Mario Limonciello <superm1@kernel.org>
To: Bartosz Golaszewski <brgl@kernel.org>,
	Hardik Prakash <hardikprakash.official@gmail.com>
Cc: linux-gpio@vger.kernel.org, wsa@kernel.org,
	andriy.shevchenko@intel.com, brgl@bgdev.pl,
	basavaraj.natikar@amd.com, linus.walleij@linaro.org,
	linux-i2c@vger.kernel.org
Subject: Re: [PATCH v6 1/1] i2c: designware: defer probe if child GpioInt controllers are not bound
Date: Thu, 28 May 2026 22:24:03 +0100	[thread overview]
Message-ID: <63e6fdb6-1679-44f5-acfb-563ed3b56a54@kernel.org> (raw)
In-Reply-To: <CAMRc=Mc7KrsmB4Svjoj4WMRa-=D2xitqURVRJVWhDH9qyzOVhg@mail.gmail.com>



On 5/26/26 11:42, Bartosz Golaszewski wrote:
> On Sat, 23 May 2026 19:44:40 +0200, Hardik Prakash
> <hardikprakash.official@gmail.com> said:
>> 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>
>> Assisted-by: Claude:claude-sonnet-4-6
>> Assisted-by: GPT-Codex:gpt-5.2-codex
>> BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=221494
> 
> I don't think we use this tag anymore. Just make it Link:
> 
> Acked-by: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Reviewed-by: Mario Limonciello (AMD) <superm1@kernel.org>

Please make sure that we drop the now unnecessary patch that was 
committed from the earlier series when queuing this.  If that has 
already made it into a PR to linus (as part of -fixes or so) we should 
get it reverted.



  reply	other threads:[~2026-05-28 23:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-23 17:44 [PATCH v6 0/1] i2c: designware: defer probe if child GpioInt controllers are not bound Hardik Prakash
2026-05-23 17:44 ` [PATCH v6 1/1] " Hardik Prakash
2026-05-24  1:47   ` kernel test robot
2026-05-24  5:40     ` Hardik Prakash
2026-05-26 10:42   ` Bartosz Golaszewski
2026-05-28 21:24     ` Mario Limonciello [this message]
2026-05-29  6:56       ` Hardik Prakash
2026-05-29  7:23         ` Mario Limonciello
2026-05-23 17:57 ` [PATCH v6 0/1] " Mario Limonciello
2026-05-26  9:41 ` Bartosz Golaszewski
2026-05-26 10:05   ` Hardik Prakash

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=63e6fdb6-1679-44f5-acfb-563ed3b56a54@kernel.org \
    --to=superm1@kernel.org \
    --cc=andriy.shevchenko@intel.com \
    --cc=basavaraj.natikar@amd.com \
    --cc=brgl@bgdev.pl \
    --cc=brgl@kernel.org \
    --cc=hardikprakash.official@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-i2c@vger.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