[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zxn_Ye-JmxSKuhkq@smile.fi.intel.com>
Date: Thu, 24 Oct 2024 11:03:45 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Yoshihiro Furudera <fj5100bi@...itsu.com>
Cc: Jarkko Nikula <jarkko.nikula@...ux.intel.com>,
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 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>
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists