public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nirujogi, Pratap" <pnirujog@amd.com>
To: Mario Limonciello <mario.limonciello@amd.com>,
	Pratap Nirujogi <pratap.nirujogi@amd.com>,
	andi.shyti@kernel.org, mika.westerberg@linux.intel.com,
	andriy.shevchenko@linux.intel.com, jsd@semihalf.com
Cc: rafael.j.wysocki@intel.com, mlimonci@amd.com,
	benjamin.chan@amd.com, bin.du@amd.com, king.li@amd.com,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] i2c: designware: amdisp: Fix null pointer dereference in runtime resume
Date: Thu, 19 Mar 2026 17:09:55 -0400	[thread overview]
Message-ID: <61dbe8a1-6578-4690-8571-6b00c1850d34@amd.com> (raw)
In-Reply-To: <4527c72d-bc59-4f5d-af94-4b2f37d75a96@amd.com>

Hi Mario,

On 3/9/2026 9:29 PM, Mario Limonciello wrote:
> 
> 
> On 3/9/2026 5:00 PM, Pratap Nirujogi wrote:
>> Add NULL check for i_dev->map before calling i2c_dw_init() in the
>> runtime resume path. The regmap may not be initialized yet when
>> runtime PM tries to resume the device early in the probe sequence,
>> leading to a NULL pointer dereference. Skip the i2c_dw_init() call
>> if regmap is not yet created.
>>
>> This race condition occurs when runtime PM resume is triggered before
>> i2c_dw_probe() completes the regmap initialization and was observed in
>> kernel v7.0 where the order of device enumeration has changed because
>> of the changes in registering the device sources in the device hierarchy.
>>
>> Co-developed-by: Bin Du <Bin.Du@amd.com>
>> Fixes: 02c057ddefef ("ACPI: video: Convert the driver to a platform one")
> 
> Is this the right commit that introduced the race?  Did it change the 
> timing?
> 
> Or was the race always there and we just got lucky until that commit 
> went in?
> 
My apologies for mixing up this change along with other changes that 
were needed to fix the AMD ISP driver regressions in v7.0.

I investigated further and found that this issue was exposed by the 
below commit.

https://github.com/torvalds/linux/commit/38fa29b01a6a295aedb69d1bbdad70acd7d204c6

However, the resume‑probe race condition existed even earlier and had 
not surfaced because device initialization in resume is done only when 
init handle is valid.

Here is some background and context on this change:

The amdisp i2c device requires ISP to be in power on state for probe to 
succeed. To meet this requirement, we added this device, which is a 
amdgpu MFD child to the genpd, to control isp power using runtime PM. 
The pm_runtime_get_sync() call before probe triggers a PM resume, which 
powers on the ISP and also invokes the amdisp i2c runtime resume before 
the probe completes resulting in this race condition.

To fix this issue properly, I’m considering this change. Please review 
and share your feedback on whether this makes sense.

- Call dev_pm_genpd_resume() to Power ON ISP before probe
- Call dev_pm_genpd_suspend() to Power OFF ISP after probe
- Call pm_runtime_enable() after probe is successful to take care of 
system suspend/resume.

diff --git a/drivers/i2c/busses/i2c-designware-amdisp.c 
b/drivers/i2c/busses/i2c-designware-amdisp.c
index 19de518be30a4..9ce58522951cd 100644
--- a/drivers/i2c/busses/i2c-designware-amdisp.c
+++ b/drivers/i2c/busses/i2c-designware-amdisp.c
@@ -7,6 +7,7 @@

  #include <linux/module.h>
  #include <linux/platform_device.h>
+#include <linux/pm_domain.h>
  #include <linux/pm_runtime.h>
  #include <linux/soc/amd/isp4_misc.h>

@@ -76,9 +77,7 @@ static int amd_isp_dw_i2c_plat_probe(struct 
platform_device *pdev)

         device_enable_async_suspend(&pdev->dev);

-       pm_runtime_enable(&pdev->dev);
-       pm_runtime_get_sync(&pdev->dev);
-
+       dev_pm_genpd_resume(&pdev->dev);
         ret = i2c_dw_probe(isp_i2c_dev);
         if (ret) {
@@ -86,14 +85,14 @@ static int amd_isp_dw_i2c_plat_probe(struct 
platform_device *pdev)
                 goto error_release_rpm;
         }
-
-       pm_runtime_put_sync(&pdev->dev);
+       dev_pm_genpd_suspend(&pdev->dev);
+       pm_runtime_set_suspended(&pdev->dev);
+       pm_runtime_enable(&pdev->dev);

         return 0;

  error_release_rpm:
         amd_isp_dw_i2c_plat_pm_cleanup(isp_i2c_dev);
-       pm_runtime_put_sync(&pdev->dev);
         return ret;
  }

Thanks,
Pratap


>> Signed-off-by: Pratap Nirujogi <pratap.nirujogi@amd.com>
>> ---
>>   drivers/i2c/busses/i2c-designware-amdisp.c | 5 ++++-
>>   1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/i2c/busses/i2c-designware-amdisp.c b/drivers/i2c/ 
>> busses/i2c-designware-amdisp.c
>> index c48728ad9f6f2..cd7ee55fbe1ee 100644
>> --- a/drivers/i2c/busses/i2c-designware-amdisp.c
>> +++ b/drivers/i2c/busses/i2c-designware-amdisp.c
>> @@ -153,7 +153,10 @@ static int 
>> amd_isp_dw_i2c_plat_runtime_resume(struct device *dev)
>>           return -ENODEV;
>>       i2c_dw_prepare_clk(i_dev, true);
>> -    i2c_dw_init(i_dev);
>> +
>> +    /* Skip i2c_dw_init if regmap not yet created by i2c_dw_probe */
>> +    if (i_dev->map)
>> +        i2c_dw_init(i_dev);
>>       return 0;
>>   }
> 


  reply	other threads:[~2026-03-19 21:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09 22:00 [PATCH v1] i2c: designware: amdisp: Fix null pointer dereference in runtime resume Pratap Nirujogi
2026-03-10  1:29 ` Mario Limonciello
2026-03-19 21:09   ` Nirujogi, Pratap [this message]
2026-03-20  7:59     ` Andy Shevchenko
2026-03-20 15:38       ` Nirujogi, Pratap
2026-03-20 13:56     ` Mario Limonciello
2026-03-20 15:40       ` Nirujogi, Pratap
2026-03-10 11:21 ` Andy Shevchenko
2026-03-19 21:24   ` Nirujogi, Pratap

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=61dbe8a1-6578-4690-8571-6b00c1850d34@amd.com \
    --to=pnirujog@amd.com \
    --cc=andi.shyti@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=benjamin.chan@amd.com \
    --cc=bin.du@amd.com \
    --cc=jsd@semihalf.com \
    --cc=king.li@amd.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=mlimonci@amd.com \
    --cc=pratap.nirujogi@amd.com \
    --cc=rafael.j.wysocki@intel.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