linux-kernel - Re: [PATCH v2] i2c: designware: Add ACPI HID for DWAPB I2C controller on FUJITSU-MONAKA

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] [day] [month] [year] [list]

Message-ID: <2c5a8b81-7841-4b5f-84ae-2a34120aa242@linux.intel.com>
Date: Fri, 25 Oct 2024 16:09:09 +0300
From: Jarkko Nikula <jarkko.nikula@...ux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
 Yoshihiro Furudera <fj5100bi@...itsu.com>
Cc: Mika Westerberg <mika.westerberg@...ux.intel.com>,
 Jan Dabros <jsd@...ihalf.com>, Andi Shyti <andi.shyti@...nel.org>,
 linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] i2c: designware: Add ACPI HID for DWAPB I2C controller
 on FUJITSU-MONAKA

On 10/24/24 11:03 AM, Andy Shevchenko wrote:
> On Thu, Oct 24, 2024 at 07:15:53AM +0000, Yoshihiro Furudera wrote:
>> Enable DWAPB I2C controller support on FUJITSU-MONAKA.
>> This will be used in the FUJITSU-MONAKA server scheduled
>> for shipment in 2027.
>>
>> The DSDT information obtained when verified using an
>> in-house simulator is presented below.
>>
>>       Device (SMB0)
>>       {
>>           Name (_HID, "FUJI200B")  // _HID: Hardware ID
>>           Name (_UID, Zero)  // _UID: Unique ID
>>           ...
>>           Name (_CRS, ResourceTemplate ()
>>           {
>>               Memory32Fixed (ReadWrite,
>>                   0x2A4B0000,         // Address Base
>>                   0x00010000,         // Address Length
>>                   )
>>               Interrupt (ResourceConsumer, Level, ActiveHigh, Exclusive, ,, )
>>               {
>>                   0x00000159,
>>               }
>>           })
>>           ...
>>       }
>>
>> The expression SMB0 is used to indicate SMBus HC#0,
>> a string of up to four characters.
>>
>> Created the SMB0 object according to the following
>> specifications:
>>
>> ACPI Specification
>> 13.2. Accessing the SMBus from ASL Code
>> https://uefi.org/htmlspecs/ACPI_Spec_6_4_html/13_ACPI_System_Mgmt_Bus_Interface_Spec/accessing-the-smbus-from-asl-code.html
>>
>> IPMI Specification
>> Example 4: SSIF Interface(P574)
>> https://www.intel.co.jp/content/www/jp/ja/products/docs/servers/ipmi/ipmi-second-gen-interface-spec-v2-rev1-1.html
> 
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
> 
Acked-by: Jarkko Nikula <jarkko.nikula@...ux.intel.com>