linux-kernel - Re: [PATCH v3 3/3] spi: xilinx: use device property accessors.

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

Message-ID: <b9ad8ab8-7985-4c89-a82b-c7f31d32c167@sirena.org.uk>
Date: Mon, 19 Jan 2026 18:38:48 +0000
From: Mark Brown <broonie@...nel.org>
To: Abdurrahman Hussain <abdurrahman@...thop.ai>
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 Mon, Jan 19, 2026 at 09:47:11AM -0800, Abdurrahman Hussain wrote:
> > On Jan 19, 2026, at 9:32 AM, Mark Brown <broonie@...nel.org> wrote:

Please fix your mail client to word wrap within paragraphs at something
substantially less than 80 columns.  Doing this makes your messages much
easier to read and reply to.

> > You are just bindly making the DT properties available as _DSD
> > properties on ACPI systems, ACPI is a completely different firmware
> > interface with it's own idioms.  Does this interface make any sense on
> > ACPI?

> From the above link:

> "The special DT namespace link device ID, PRP0001, provides a means to
> use the existing DT-compatible device identification in ACPI…"

...

> Is this not appropriate?

This was specifically targetted at some embedded x86 systems where there
was a goal to reuse device tree bindings for things that just can't be
expressed well in ACPI.  _DSD is generally considered tasteless for more
server style systems, AIUI the general approach preferred by ACPI
forward OSs is to use some combination of DMI quirking and registering
with a per-device ID (like the per generation fake PCI IDs that Intel
uses for all IPs on their SoCs).  Just blindly accepting _DSD can end up
with something that's not used because it's not what the ecosystem
wants.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)