From: <Conor.Dooley@microchip.com>
To: <wsa@kernel.org>, <Daire.McNamara@microchip.com>,
<linux-i2c@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<andreas.buerkler@enclustra.com>, <Lewis.Hanly@microchip.com>
Subject: Re: [PATCH] i2c: microchip-core: fix erroneous late ack send
Date: Thu, 11 Aug 2022 12:38:51 +0000 [thread overview]
Message-ID: <a79262e2-a190-677f-034b-56757a085280@microchip.com> (raw)
In-Reply-To: <YvT1/LOr4udX+jhP@shikoro>
On 11/08/2022 13:28, Wolfram Sang wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> On Fri, Aug 05, 2022 at 08:43:46AM +0100, Conor Dooley wrote:
>> A late ack is currently being sent at the end of a transfer due to
>> incorrect logic in mchp_corei2c_empty_rx(). Currently the Assert Ack
>> bit is being written to the controller's control reg after the last
>> byte has been received, causing it to sent another byte with the ack.
>> Instead, the AA flag should be written to to the contol register when
>> the penultimate byte is read so it is sent out for the last byte.
>>
>> Reported-by: Andreas Buerkler <andreas.buerkler@enclustra.com>
>> Fixes: 64a6f1c4987e ("i2c: add support for microchip fpga i2c controllers")
>> Tested-by: Lewis Hanly <lewis.hanly@microchip.com>
>> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
>
> Fixed these checkpatch warnings:
>
> WARNING: 'contol' may be misspelled - perhaps 'control'?
> WARNING: Possible repeated word: 'to'
Heh, that's what I get for editing the commit in send-email..
>
> and applied to for-current, thanks!
Thanks :)
>
>
next prev parent reply other threads:[~2022-08-11 12:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 7:43 [PATCH] i2c: microchip-core: fix erroneous late ack send Conor Dooley
2022-08-11 12:28 ` Wolfram Sang
2022-08-11 12:38 ` Conor.Dooley [this message]
2022-08-11 12:46 ` Wolfram Sang
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=a79262e2-a190-677f-034b-56757a085280@microchip.com \
--to=conor.dooley@microchip.com \
--cc=Daire.McNamara@microchip.com \
--cc=Lewis.Hanly@microchip.com \
--cc=andreas.buerkler@enclustra.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa@kernel.org \
/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