lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0c895129-23af-2fc6-0c99-61348a69f961@hygon.cn>
Date:   Fri, 26 Apr 2019 22:23:22 +0800
From:   Pu Wen <puwen@...on.cn>
To:     Jean Delvare <jdelvare@...e.de>
CC:     "bp@...en8.de" <bp@...en8.de>,
        "linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: Re: [RFC PATCH RESEND] i2c-piix4: Add Hygon Dhyana SMBus support

On 2019/4/26 17:38, Jean Delvare wrote:
> Sorry for the late answer.

Thanks for the reply!

>> Cc: <stable@...r.kernel.org> # v5.0+
> 
> I object to adding this to stable. It's not fixing any bug, and it's
> far from being a one-liner. I'd rather let distributions backport it as
> they see fit.

Okay, will not add this patch to stable.

>> +	     PIIX4_dev->revision >= 0x49) ||
>> +	    (PIIX4_dev->vendor == PCI_VENDOR_ID_HYGON &&
>> +	     PIIX4_dev->device == PCI_DEVICE_ID_AMD_KERNCZ_SMBUS &&
>>   	     PIIX4_dev->revision >= 0x49))
>>   		smb_en = 0x00;
> 
> Does the compatibility with the original AMD chipset include the
> revision number?

The revision number may not be needed here, although it indeed larger 
than 0x49 on Hygon platform.

>> -		if (dev->vendor == PCI_VENDOR_ID_AMD &&
>> +		if ((dev->vendor == PCI_VENDOR_ID_AMD ||
>> +		     dev->vendor == PCI_VENDOR_ID_HYGON) &&
>>   		    dev->device == PCI_DEVICE_ID_AMD_KERNCZ_SMBUS) {
>>   			u8 imc;
>>   
> 
> Patch looks good. I assume you have tested it on real hardware?

Yes, I have tested it on Hygon hardware. It works well.

> I would like you to also document the new supported chipset in
> drivers/i2c/busses/Kconfig and Documentation/i2c/busses/i2c-piix4 as
> well as in the header comment of i2c-piix4.c itself. I know it seems
> redundant but it helps the user know which driver they need.

Because Hygon uses the same PCI device ID of AMD's, so is it appropriate 
to document with the name "Hygon CZ" or just "Hygon"?

-- 
Regards,
Pu Wen

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ