linux-kernel - Re: [PATCH] dt-bindings: firmware: coreboot: Document optional device specific properties

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: <d8f3eb00-c7a6-425a-9e69-a01bc3532f0c@kernel.org>
Date: Wed, 19 Nov 2025 09:12:56 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Chen-Yu Tsai <wenst@...omium.org>
Cc: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Conor Dooley <conor+dt@...nel.org>, devicetree@...r.kernel.org,
 chrome-platform@...ts.linux.dev, Julius Werner <jwerner@...omium.org>,
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dt-bindings: firmware: coreboot: Document optional device
 specific properties

On 19/11/2025 08:32, Chen-Yu Tsai wrote:
> On Wed, Nov 19, 2025 at 3:13 PM Krzysztof Kozlowski <krzk@...nel.org> wrote:
>>
>> On 19/11/2025 08:11, Chen-Yu Tsai wrote:
>>> Coreboot, or the ChromeOS second stage bootloader, depthcharge, will
>>> insert device specific properties into the coreboot firmware node when
>>> there are valid values.
>>>
>>> Document these properties in the binding.
>>>
>>> Signed-off-by: Chen-Yu Tsai <wenst@...omium.org>
>>> ---
>>>  Documentation/devicetree/bindings/firmware/coreboot.txt | 9 +++++++++
>>>  1 file changed, 9 insertions(+)
>>>
>>
>> TXT files cannot receive new properties. You need to first convert to DT
>> schema.
> 
> OK. Let me look into this.

After the conversion you will hit another problem - you need vendor
prefixes for these, because only generic properties can come without
them. Otherwise (without vendor prefix) these would define the type for
all other bindings, which probably is not what we want.

Best regards,
Krzysztof