From: Alexander Sverdlin <alexander.sverdlin@gmail.com>
To: Jean Delvare <jdelvare@suse.de>,
"Zakowski, Piotr" <piotr.zakowski@intel.com>
Cc: andi.shyti@kernel.org, linux-i2c@vger.kernel.org, "Shepon,
Oren" <oren.shepon@intel.com>,
"Kozlowski, Pawel" <pawel.kozlowski@intel.com>,
"Usyskin, Alexander" <alexander.usyskin@intel.com>,
"Radtke, Jakub" <jakub.radtke@intel.com>
Subject: Re: Potential bug in SMBus kernel module
Date: Tue, 13 Feb 2024 12:49:34 +0100 [thread overview]
Message-ID: <28430e65f50749bf446ed621d116ba8fb895add7.camel@gmail.com> (raw)
In-Reply-To: <20240213120553.7b0ab120@endymion.delvare>
Hi Jean, thanks for including me!
On Tue, 2024-02-13 at 12:05 +0100, Jean Delvare wrote:
> > 4. Observed bug
> >
> > In the "Block Write-Block Read Process Call", the FIFO index should be cleared twice.
> > Testing of the Linux driver for the above scenario has shown that it only clears once during the write part (writing data to the FIFO buffer) and does not clear before the read part (reading data
> > from the FIFO buffer).
> > As a result, the command only returns a portion of the data (N-M) and leaves behind residual data from previous SMBus commands that used the FIFO buffer.
>
> Support for the Block Write-Block Read Process Call command was added
> to the i2c-i801 driver by Alexander Sverdlin in June 2019. I'm adding
> him to Cc, but he changed addresses meanwhile, so I hope I got the
> right Alexander.
While I'm trying to remember the details of the story ;-), could
you please point me to the full bug report? I suspect it has not actually
been posted to linux-i2c?
--
Alexander Sverdlin.
next prev parent reply other threads:[~2024-02-13 11:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <SJ0PR11MB5133C098821363F292316A0088482@SJ0PR11MB5133.namprd11.prod.outlook.com>
2024-02-13 11:05 ` Potential bug in SMBus kernel module Jean Delvare
2024-02-13 11:49 ` Alexander Sverdlin [this message]
2024-02-14 18:11 ` Alexander Sverdlin
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=28430e65f50749bf446ed621d116ba8fb895add7.camel@gmail.com \
--to=alexander.sverdlin@gmail.com \
--cc=alexander.usyskin@intel.com \
--cc=andi.shyti@kernel.org \
--cc=jakub.radtke@intel.com \
--cc=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.org \
--cc=oren.shepon@intel.com \
--cc=pawel.kozlowski@intel.com \
--cc=piotr.zakowski@intel.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