From: Robert Hancock <robert.hancock@calian.com>
To: "michal.simek@amd.com" <michal.simek@amd.com>,
"ben-linux@fluff.org" <ben-linux@fluff.org>,
"andi.shyti@kernel.org" <andi.shyti@kernel.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
Robert Hancock <robert.hancock@calian.com>
Subject: [PATCH v2 0/2] Xilinx I2C driver fixes
Date: Tue, 21 Nov 2023 18:10:52 +0000 [thread overview]
Message-ID: <20231121180855.1278717-1-robert.hancock@calian.com> (raw)
A couple of fixes for the Xilinx I2C driver.
Changed since v1:
-Fixed an issue in first patch where an additional message could still have
been written to the TX FIFO without waiting for it to empty.
Robert Hancock (2):
i2c: xiic: Wait for TX empty to avoid missed TX NAKs
i2c: xiic: Try re-initialization on bus busy timeout
drivers/i2c/busses/i2c-xiic.c | 61 +++++++++++++++++++++--------------
1 file changed, 36 insertions(+), 25 deletions(-)
--
2.42.0
next reply other threads:[~2023-11-21 18:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 18:10 Robert Hancock [this message]
2023-11-21 18:11 ` [PATCH v2 1/2] i2c: xiic: Wait for TX empty to avoid missed TX NAKs Robert Hancock
2023-11-21 18:11 ` [PATCH v2 2/2] i2c: xiic: Try re-initialization on bus busy timeout Robert Hancock
2023-11-23 5:53 ` [PATCH v2 0/2] Xilinx I2C driver fixes Shubhrajyoti Datta
2023-11-23 16:40 ` Robert Hancock
2023-11-26 19:26 ` Andi Shyti
2024-03-01 9:19 ` Guntupalli, Manikanta
2024-03-01 9:22 ` Michal Simek
-- strict thread matches above, loose matches on Subject: below --
2024-03-01 6:53 Guntupalli, Manikanta
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=20231121180855.1278717-1-robert.hancock@calian.com \
--to=robert.hancock@calian.com \
--cc=andi.shyti@kernel.org \
--cc=ben-linux@fluff.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=michal.simek@amd.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).