Linux I2C development
 help / color / mirror / Atom feed
From: Bin Du <Bin.Du@amd.com>
To: Mukesh Savaliya <mukesh.savaliya@oss.qualcomm.com>,
	Guangshuo Li <lgs201920130244@gmail.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Nirujogi Pratap <pratap.nirujogi@amd.com>,
	Andi Shyti <andi.shyti@kernel.org>,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: designware: amdisp: balance genpd on probe failure
Date: Thu, 9 Jul 2026 15:26:06 +0800	[thread overview]
Message-ID: <e443ae59-c40d-49d2-aba6-dc9f6c8ee157@amd.com> (raw)
In-Reply-To: <54e814c8-c2b7-4414-aeba-469973a30b42@oss.qualcomm.com>



On 7/9/2026 2:04 PM, Mukesh Savaliya wrote:
> Looks fine to me, Have someone from AMD also Ack'ing this as requested
> by Andy Shevchenko.
> 
> On 7/8/2026 2:35 PM, Guangshuo Li wrote:
>> The change referenced by the Fixes tag avoids a runtime PM resume during
>> probe by powering the ISP domain directly with dev_pm_genpd_resume()
>> before calling i2c_dw_probe(). Runtime PM is enabled only after
>> i2c_dw_probe() has succeeded.
>>
>> However, the i2c_dw_probe() failure path still uses the old runtime PM
>> cleanup path. At that point pm_runtime_enable() has not been called yet,
>> so pm_runtime_disable() is not paired with any enable. The failure path
>> also skips the dev_pm_genpd_suspend() needed to balance the direct
>> dev_pm_genpd_resume() call.
>>
>> Suspend the genpd on the i2c_dw_probe() failure path instead of disabling
>> runtime PM. This keeps the direct genpd resume/suspend pairing symmetric
>> on both success and failure paths.
>>
>> Fixes: e2f1ada8e089 ("i2c: designware: amdisp: Fix resume-probe race
>> condition issue")
>> Signed-off-by: Guangshuo Li <lgs201920130244@gmail.com>
>> ---
>>   drivers/i2c/busses/i2c-designware-amdisp.c | 6 +++---
>>   1 file changed, 3 insertions(+), 3 deletions(-)
> 
> Acked-by: Mukesh Kumar Savaliya <mukesh.savaliya@oss.qualcomm.com>
> 

Acked-by: Bin Du <bin.du@amd.com>
Tested-by: Bin Du <bin.du@amd.com>

      reply	other threads:[~2026-07-09  7:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-08  9:05 [PATCH] i2c: designware: amdisp: balance genpd on probe failure Guangshuo Li
2026-07-08 14:24 ` Andy Shevchenko
2026-07-08 15:36 ` Nirujogi, Pratap
2026-07-09  6:04 ` Mukesh Savaliya
2026-07-09  7:26   ` Bin Du [this message]

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=e443ae59-c40d-49d2-aba6-dc9f6c8ee157@amd.com \
    --to=bin.du@amd.com \
    --cc=andi.shyti@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=lgs201920130244@gmail.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=mukesh.savaliya@oss.qualcomm.com \
    --cc=pratap.nirujogi@amd.com \
    /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