From: Michal Simek <michal.simek@amd.com>
To: Abdurrahman Hussain <abdurrahman@nexthop.ai>,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: Andi Shyti <andi.shyti@kernel.org>,
linux-arm-kernel@lists.infradead.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: xiic: add ACPI support
Date: Fri, 16 Jan 2026 08:30:19 +0100 [thread overview]
Message-ID: <4c3f28e1-69a2-410b-abe7-ed163e97eedd@amd.com> (raw)
In-Reply-To: <AAB5CE7A-9264-4CE1-8A49-2FD3043B0A80@nexthop.ai>
On 1/15/26 20:04, Abdurrahman Hussain wrote:
>
>
>> On Jan 15, 2026, at 5:02 AM, Wolfram Sang <wsa+renesas@sang-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@nexthop.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
next prev parent reply other threads:[~2026-01-16 7:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 0:28 [PATCH] i2c: xiic: add ACPI support Abdurrahman Hussain
2026-01-15 13:02 ` Wolfram Sang
2026-01-15 19:04 ` Abdurrahman Hussain
2026-01-16 7:30 ` Michal Simek [this message]
2026-01-16 20:12 ` Abdurrahman Hussain
2026-01-21 8:36 ` Andy Shevchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4c3f28e1-69a2-410b-abe7-ed163e97eedd@amd.com \
--to=michal.simek@amd.com \
--cc=abdurrahman@nexthop.ai \
--cc=andi.shyti@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox