[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <82362ecb-2049-14f4-f176-36bfcbbf84ad@broadcom.com>
Date: Thu, 6 Jul 2023 13:08:38 -0700
From: Ray Jui <ray.jui@...adcom.com>
To: Wolfram Sang <wsa@...nel.org>, YE Chengfeng <cyeaa@...nect.ust.hk>,
"andi.shyti@...nel.org" <andi.shyti@...nel.org>,
"rjui@...adcom.com" <rjui@...adcom.com>,
"sbranden@...adcom.com" <sbranden@...adcom.com>,
"linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"bcm-kernel-feedback-list@...adcom.com"
<bcm-kernel-feedback-list@...adcom.com>
Subject: Re: [PATCH] i2c: bcm-iproc: Fix bcm_iproc_i2c_isr deadlock issue
Hi Wolfram,
On 7/6/2023 12:36 PM, Wolfram Sang wrote:
> On Sat, Jun 24, 2023 at 07:36:02PM +0000, YE Chengfeng wrote:
>> iproc_i2c_rd_reg and iproc_i2c_wr_reg are called from both
>> interrupt context (e.g. bcm_iproc_i2c_isr) and process context
>> (e.g. bcm_iproc_i2c_suspend). Therefore, interrupts should be
>> disabled to avoid potential deadlock. To prevent this deadlock,
>> use spin_lock_irqsave.
>>
>> Signed-off-by: Chengfeng Ye <cyeaa@...nect.ust.hk>
>
> I can't apply it, what version is this against? Also, if someone could
> supply a proper Fixes-tag, this would be much appreciated.
>
I'll let Chengfeng check the version.
For the fixes tag, it is:
Fixes: 9a1038728037 ("i2c: iproc: add NIC I2C support")
Thanks,
Ray
Download attachment "smime.p7s" of type "application/pkcs7-signature" (4194 bytes)
Powered by blists - more mailing lists