From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jarkko Nikula Subject: Re: [PATCH v2] i2c: i801: Fix I2C Block Read on 8-Series/C220 and later Date: Tue, 11 Oct 2016 14:32:55 +0300 Message-ID: References: <20161011131327.0eabd227@endymion> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mga06.intel.com ([134.134.136.31]:40500 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751647AbcJKMRL (ORCPT ); Tue, 11 Oct 2016 08:17:11 -0400 In-Reply-To: <20161011131327.0eabd227@endymion> Sender: linux-i2c-owner@vger.kernel.org List-Id: linux-i2c@vger.kernel.org To: Jean Delvare , Linux I2C Cc: Mika Westerberg , Wolfram Sang On 10/11/2016 02:13 PM, Jean Delvare wrote: > Starting with the 8-Series/C220 PCH (Lynx Point), the SMBus > controller includes a SPD EEPROM protection mechanism. Once the SPD > Write Disable bit is set, only reads are allowed to slave addresses > 0x50-0x57. > > However the legacy implementation of I2C Block Read since the ICH5 > looks like a write, and is therefore blocked by the SPD protection > mechanism. This causes the eeprom and at24 drivers to fail. > > So assume that I2C Block Read is implemented as an actual read on > these chipsets. I tested it on my Q87 chipset and it seems to work > just fine. > > Signed-off-by: Jean Delvare > Cc: Jarkko Nikula > Cc: Mika Westerberg > Cc: Wolfram Sang > --- > Changes since v1: > * Rebased on Linus' latest tree. > > Jarkko, still no information about this from your Windows or hardware > folks? > No update, in fact some of the contacts have left the company :-( -- Jarkko