[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <05D2CC15-DD6B-40F0-BFF0-3264D4FF96ED@nexthop.ai>
Date: Mon, 19 Jan 2026 09:15:40 -0800
From: Abdurrahman Hussain <abdurrahman@...thop.ai>
To: Mark Brown <broonie@...nel.org>
Cc: Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Michal Simek <michal.simek@....com>,
linux-spi@...r.kernel.org,
devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 3/3] spi: xilinx: use device property accessors.
> On Jan 19, 2026, at 8:50 AM, Mark Brown <broonie@...nel.org> wrote:
>
> On Mon, Jan 19, 2026 at 08:47:17AM -0800, Abdurrahman Hussain wrote:
>>> On Jan 19, 2026, at 8:32 AM, Mark Brown <broonie@...nel.org> wrote:
>>> On Mon, Jan 19, 2026 at 07:06:24AM +0000, Abdurrahman Hussain via B4 Relay wrote:
>
>>>> - of_property_read_u32(pdev->dev.of_node, "xlnx,num-ss-bits",
>>>> - &num_cs);
>>>> - ret = of_property_read_u32(pdev->dev.of_node,
>>>> - "xlnx,num-transfer-bits",
>>>> - &bits_per_word);
>>>> + device_property_read_u32(&pdev->dev, "xlnx,num-ss-bits",
>>>> + &num_cs);
>>>> + ret = device_property_read_u32(&pdev->dev,
>>>> + "xlnx,num-transfer-bits",
>>>> + &bits_per_word);
>
>>> Are these bindings appropraite for ACPI systems?
>
>> Yes, the Xilinx IP blocks are memory mapped and work exactly the same on ACPI as they do on DT.
>
> That does not answer the question at all. Is it appropriate to
> configure an ACPI system in this way?
I am not sure I understood your question. What do you mean by “appropriate”?
This is following the same guidelines as outlined in
https://www.kernel.org/doc/html/v6.7/firmware-guide/acpi/enumeration.html
Powered by blists - more mailing lists