public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Jean Delvare <jdelvare@suse.de>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Wolfram Sang <wsa@kernel.org>,
	linux-i2c@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 5.14 088/252] i2c: i801: Fix handling SMBHSTCNT_PEC_EN
Date: Mon, 13 Sep 2021 12:55:42 -0400	[thread overview]
Message-ID: <YT+CjnAnkfL3Nh0D@sashalap> (raw)
In-Reply-To: <20210909151320.7bddd134@endymion>

On Thu, Sep 09, 2021 at 03:13:20PM +0200, Jean Delvare wrote:
>Hi Sascha,
>
>On Thu,  9 Sep 2021 07:38:22 -0400, Sasha Levin wrote:
>> From: Heiner Kallweit <hkallweit1@gmail.com>
>>
>> [ Upstream commit a6b8bb6a813a6621c75ceacd1fa604c0229e9624 ]
>>
>> Bit SMBHSTCNT_PEC_EN is used only if software calculates the CRC and
>> uses register SMBPEC. This is not supported by the driver, it supports
>> hw-calculation of CRC only (using bit SMBAUXSTS_CRCE). The chip spec
>> states the following, therefore never set bit SMBHSTCNT_PEC_EN.
>>
>> Chapter SMBus CRC Generation and Checking
>> If the AAC bit is set in the Auxiliary Control register, the PCH
>> automatically calculates and drives CRC at the end of the transmitted
>> packet for write cycles, and will check the CRC for read cycles. It will
>> not transmit the contents of the PEC register for CRC. The PEC bit must
>> not be set in the Host Control register. If this bit is set, unspecified
>> behavior will result.
>>
>> This patch is based solely on the specification and compile-tested only,
>> because I have no PEC-capable devices.
>>
>> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
>> Tested-by: Jean Delvare <jdelvare@suse.de>
>> Signed-off-by: Wolfram Sang <wsa@kernel.org>
>> Signed-off-by: Sasha Levin <sashal@kernel.org>
>> ---
>>  drivers/i2c/busses/i2c-i801.c | 27 +++++++++++----------------
>>  1 file changed, 11 insertions(+), 16 deletions(-)
>
>This patch fixes a theoretical problem nobody has ever complained
>about. I don't think it makes sense to backport it to stable kernel
>branches.

Sure, I'll drop it. Thanks.

-- 
Thanks,
Sasha

      reply	other threads:[~2021-09-13 16:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210909114106.141462-1-sashal@kernel.org>
2021-09-09 11:38 ` [PATCH AUTOSEL 5.14 088/252] i2c: i801: Fix handling SMBHSTCNT_PEC_EN Sasha Levin
2021-09-09 13:13   ` Jean Delvare
2021-09-13 16:55     ` Sasha Levin [this message]

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=YT+CjnAnkfL3Nh0D@sashalap \
    --to=sashal@kernel.org \
    --cc=hkallweit1@gmail.com \
    --cc=jdelvare@suse.de \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@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