[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4c3f28e1-69a2-410b-abe7-ed163e97eedd@amd.com>
Date: Fri, 16 Jan 2026 08:30:19 +0100
From: Michal Simek <michal.simek@....com>
To: Abdurrahman Hussain <abdurrahman@...thop.ai>,
Wolfram Sang <wsa+renesas@...g-engineering.com>
Cc: Andi Shyti <andi.shyti@...nel.org>, linux-arm-kernel@...ts.infradead.org,
linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] i2c: xiic: add ACPI support
On 1/15/26 20:04, Abdurrahman Hussain wrote:
>
>
>> On Jan 15, 2026, at 5:02 AM, Wolfram Sang <wsa+renesas@...g-engineering.com> wrote:
>>
>> On Thu, Jan 15, 2026 at 12:28:46AM +0000, Abdurrahman Hussain wrote:
>>> Use generic device property accessors.
>>> Make the clock optional assuming it's managed by firmware.
>>>
>>> Signed-off-by: Abdurrahman Hussain <abdurrahman@...thop.ai>
>>
>> On which hardware has this been tested?
>>
>
> This was tested on nexthop.ai data-center NH-4010 switch with Xilinx based FPGA.
>
> The following ACPI ASL fragment was used to describe the device:
>
> Device (I2C2) {
> Name (_HID, "PRP0001")
> Name (_CRS, ResourceTemplate () {
> Memory32Fixed (ReadWrite, 0x80a40400, 0x00000200)
> GpioInt (Level, ActiveHigh, Exclusive, PullNone, 0,
> "\\_SB.PCI0.GPP5.FPGA") { 10 }
> })
> Name (_DSD, Package () {
> ToUUID ("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
> Package () {
> Package () { "compatible", "xlnx,axi-iic-2.1" },
> Package () { "single-master", 1 },
> }
> })
> }
can you share more details about cpu and bootflow?
Thanks,
Michal
Powered by blists - more mailing lists