From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Huangzheng Lai <Huangzheng.Lai@unisoc.com>,
Andi Shyti <andi.shyti@kernel.org>
Cc: Orson Zhai <orsonzhai@gmail.com>,
Chunyan Zhang <zhang.lyra@gmail.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
huangzheng lai <laihuangzheng@gmail.com>,
Xiongpeng Wu <xiongpeng.wu@unisoc.com>
Subject: Re: [PATCH V2 6/7] i2c: sprd: Increase the waiting time for I2C transmission to avoid system crash issues
Date: Mon, 23 Oct 2023 19:39:24 +0800 [thread overview]
Message-ID: <c67fcc8b-4270-4b61-069c-b3afd4899fba@linux.alibaba.com> (raw)
In-Reply-To: <20231023081158.10654-7-Huangzheng.Lai@unisoc.com>
On 10/23/2023 4:11 PM, Huangzheng Lai wrote:
> Due to the relatively low priority of the isr_thread, when the CPU
> load is high, the execution of sprd_i2c_isr_thread will be delayed.
> After the waiting time is exceeded, the I2C driver will perform
> operations such as disabling the I2C controller. Later, when
> sprd_i2c_isr_thread is called by the CPU, there will be kernel panic
> caused by illegal access to the IIC register. After pressure testing,
> we found that increasing the IIC waiting time to 10 seconds can
> avoid this problem.
>
> Fixes: 0b884fe71f9e ("i2c: sprd: use a specific timeout to avoid system hang up issue")
> Cc: <stable@vger.kernel.org> # v5.11+
> Signed-off-by: Huangzheng Lai <Huangzheng.Lai@unisoc.com>
Looks reasonable to me.
Reviewed-by: Baolin Wang <baolin.wang@linux.alibaba.com>
> ---
> drivers/i2c/busses/i2c-sprd.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/i2c/busses/i2c-sprd.c b/drivers/i2c/busses/i2c-sprd.c
> index b65729ba7d5a..dbdac89ad482 100644
> --- a/drivers/i2c/busses/i2c-sprd.c
> +++ b/drivers/i2c/busses/i2c-sprd.c
> @@ -74,7 +74,7 @@
> /* timeout (ms) for pm runtime autosuspend */
> #define SPRD_I2C_PM_TIMEOUT 1000
> /* timeout (ms) for transfer message */
> -#define I2C_XFER_TIMEOUT 1000
> +#define I2C_XFER_TIMEOUT 10000
> /* dynamic modify clk_freq flag */
> #define I2C_3M4_FLAG 0x0100
> #define I2C_1M_FLAG 0x0080
next prev parent reply other threads:[~2023-10-23 11:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 8:11 [PATCH V2 0/7] i2c: sprd: Modification of UNISOC Platform I2C Driver Huangzheng Lai
2023-10-23 8:11 ` [PATCH V2 1/7] i2c: sprd: Add configurations that support 1Mhz and 3.4Mhz frequencies Huangzheng Lai
2023-10-23 11:19 ` Baolin Wang
2023-10-24 20:45 ` Andi Shyti
2023-10-23 8:11 ` [PATCH V2 2/7] i2c: sprd: Add I2C driver to use 'reset framework' function Huangzheng Lai
2023-10-23 11:27 ` Baolin Wang
2023-11-03 11:59 ` Krzysztof Kozlowski
2023-10-23 8:11 ` [PATCH V2 3/7] i2c: sprd: Use global variables to record I2C ack/nack status instead of local variables Huangzheng Lai
2023-10-23 11:32 ` Baolin Wang
2023-11-06 3:01 ` huangzheng lai
2023-10-24 21:20 ` Andi Shyti
2023-11-06 9:02 ` huangzheng lai
2023-11-03 11:59 ` Krzysztof Kozlowski
2023-10-23 8:11 ` [PATCH V2 4/7] i2c: sprd: Add I2C controller driver to support dynamic switching of 400K/1M/3.4M frequency Huangzheng Lai
2023-10-23 11:37 ` Baolin Wang
2023-10-24 21:28 ` Andi Shyti
2023-10-23 8:11 ` [PATCH V2 5/7] i2c: sprd: Configure the enable bit of the I2C controller before each transmission initiation Huangzheng Lai
2023-10-24 21:35 ` Andi Shyti
2023-10-23 8:11 ` [PATCH V2 6/7] i2c: sprd: Increase the waiting time for I2C transmission to avoid system crash issues Huangzheng Lai
2023-10-23 11:39 ` Baolin Wang [this message]
2023-10-24 21:38 ` Andi Shyti
2023-10-23 8:11 ` [PATCH V2 7/7] i2c: sprd: Add I2C_NACK_EN and I2C_TRANS_EN control bits Huangzheng Lai
2023-10-23 11:43 ` Baolin Wang
2023-10-23 11:44 ` [PATCH V2 0/7] i2c: sprd: Modification of UNISOC Platform I2C Driver Baolin Wang
2023-10-24 21:40 ` Andi Shyti
-- strict thread matches above, loose matches on Subject: below --
2023-09-21 8:54 Huangzheng Lai
2023-09-21 8:54 ` [PATCH V2 6/7] i2c: sprd: Increase the waiting time for I2C transmission to avoid system crash issues Huangzheng Lai
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=c67fcc8b-4270-4b61-069c-b3afd4899fba@linux.alibaba.com \
--to=baolin.wang@linux.alibaba.com \
--cc=Huangzheng.Lai@unisoc.com \
--cc=andi.shyti@kernel.org \
--cc=laihuangzheng@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=orsonzhai@gmail.com \
--cc=xiongpeng.wu@unisoc.com \
--cc=zhang.lyra@gmail.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
all inboxes | Powered by JetHome®