From: Tam Nguyen <tamnguyenchi@os.amperecomputing.com>
To: linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org
Cc: patches@amperecomputing.com, jarkko.nikula@linux.intel.com,
andriy.shevchenko@linux.intel.com,
mika.westerberg@linux.intel.com, jsd@semihalf.com,
tamnguyenchi@os.amperecomputing.com,
chuong@os.amperecomputing.com, darren@os.amperecomputing.com
Subject: [PATCH v2 0/2] i2c: designware: Handle invalid SMBus block data response length value
Date: Wed, 26 Jul 2023 14:59:59 +0700 [thread overview]
Message-ID: <20230726080001.337353-1-tamnguyenchi@os.amperecomputing.com> (raw)
This v2 patch series updates the I2C DesignWare driver to handle invalid
SMBus block data response length value that causes the bus is hang and
can not be recovered.
v2:
+ Create new commit to correct length byte validation logic [Quan]
+ Get right data length from IC_DATA_CMD register [Jarkko]
Quan Nguyen (1):
i2c: designware: Correct length byte validation logic
Tam Nguyen (1):
i2c: designware: Handle invalid SMBus block data response length value
drivers/i2c/busses/i2c-designware-master.c | 16 ++++++++++++++--
1 file changed, 14 insertions(+), 2 deletions(-)
--
2.25.1
next reply other threads:[~2023-07-26 8:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 7:59 Tam Nguyen [this message]
2023-07-26 8:00 ` [PATCH v2 1/2] i2c: designware: Correct length byte validation logic Tam Nguyen
2023-07-27 10:36 ` Jarkko Nikula
2023-08-14 13:29 ` Wolfram Sang
2023-07-26 8:00 ` [PATCH v2 2/2] i2c: designware: Handle invalid SMBus block data response length value Tam Nguyen
2023-07-27 10:49 ` Jarkko Nikula
2023-08-14 13:29 ` Wolfram Sang
2023-08-02 20:02 ` [PATCH v2 0/2] " Andi Shyti
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=20230726080001.337353-1-tamnguyenchi@os.amperecomputing.com \
--to=tamnguyenchi@os.amperecomputing.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=chuong@os.amperecomputing.com \
--cc=darren@os.amperecomputing.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jsd@semihalf.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=patches@amperecomputing.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