linux-kernel - Re: [PATCH] [RFC] of: Add debug aid to find unused device tree 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: <7aq4nedii5jgrlg54kzyi3plri6ivheeo2kpxxg7q6ofr3wfsc@acsrg5rzzmzg>
Date: Mon, 14 Oct 2024 09:49:14 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Richard Weinberger <richard@....at>
Cc: devicetree@...r.kernel.org, robh@...nel.org, saravanak@...gle.com, 
	linux-kernel@...r.kernel.org, upstream+devicetree@...ma-star.at
Subject: Re: [PATCH] [RFC] of: Add debug aid to find unused device tree
 properties

On Sun, Oct 13, 2024 at 10:07:30PM +0200, Richard Weinberger wrote:
> This is a proof-of-concept patch that introduces a debug feature I find
> particularly useful.  I frequently encounter situations where I'm
> uncertain if my device tree configuration is correct or being utilized
> by the kernel.  This is especially common when porting device trees
> from vendor kernels, as some properties may have slightly different
> names in the upstream kernel, or upstream drivers may not use certain
> properties at all.

In general I don't mind, but I have a comment about above rationale.
It's just wrong. The point of DT is to describe hardware, not the one
given, fixed in time implementation.

What's more, writing bindings mentions this explicit: make binding
complete, even if it is not used.

Best regards,
Krzysztof