[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230928145128.tjflbgvena4apivs@zenone.zhora.eu>
Date: Thu, 28 Sep 2023 16:51:28 +0200
From: Andi Shyti <andi.shyti@...nel.org>
To: Jian Zhang <zhangjian.3032@...edance.com>
Cc: brendan.higgins@...ux.dev, benh@...nel.crashing.org,
joel@....id.au, andrew@...id.au, zhangjian3032@...il.com,
yulei.sh@...edance.com, xiexinnan@...edance.com,
Tommy Huang <tommy_huang@...eedtech.com>,
Wolfram Sang <wsa@...nel.org>,
"open list:ARM/ASPEED I2C DRIVER" <linux-i2c@...r.kernel.org>,
"moderated list:ARM/ASPEED I2C DRIVER" <openbmc@...ts.ozlabs.org>,
"moderated list:ARM/ASPEED MACHINE SUPPORT"
<linux-arm-kernel@...ts.infradead.org>,
"moderated list:ARM/ASPEED MACHINE SUPPORT"
<linux-aspeed@...ts.ozlabs.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] i2c: aspeed: Fix i2c bus hang in slave read
Hi Jian,
On Wed, Sep 27, 2023 at 11:42:43PM +0800, Jian Zhang wrote:
> When the `CONFIG_I2C_SLAVE` option is enabled and the device operates
> as a slave, a situation arises where the master sends a START signal
> without the accompanying STOP signal. This action results in a
> persistent I2C bus timeout. The core issue stems from the fact that
> the i2c controller remains in a slave read state without a timeout
> mechanism. As a consequence, the bus perpetually experiences timeouts.
>
> In this case, the i2c bus will be reset, but the slave_state reset is
> missing.
>
> Fixes: fee465150b45 ("i2c: aspeed: Reset the i2c controller when timeout occurs")
> Signed-off-by: Jian Zhang <zhangjian.3032@...edance.com>
Why I'm failing to find your v1 patch? And where is the
changelog?
Andi
Powered by blists - more mailing lists