From: Richard Weinberger <richard@sigma-star.at>
To: Richard Weinberger <richard@nod.at>, devicetree@vger.kernel.org
Cc: robh@kernel.org, saravanak@google.com,
linux-kernel@vger.kernel.org, upstream+devicetree@sigma-star.at,
Krzysztof Kozlowski <krzk@kernel.org>
Subject: Re: [PATCH] [RFC] of: Add debug aid to find unused device tree properties
Date: Mon, 14 Oct 2024 10:51:51 +0200 [thread overview]
Message-ID: <3247761.5fSG56mABF@somecomputer> (raw)
In-Reply-To: <7aq4nedii5jgrlg54kzyi3plri6ivheeo2kpxxg7q6ofr3wfsc@acsrg5rzzmzg>
Krzysztof,
Am Montag, 14. Oktober 2024, 09:49:14 CEST schrieb 'Krzysztof Kozlowski' via upstream:
> 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.
I agree with you, sorry for being imprecise.
> What's more, writing bindings mentions this explicit: make binding
> complete, even if it is not used.
Yes, with this aid, it is IMHO easier to find bindings that need attention.
Just as an example, lately the device tree of a vendor used the property "timers",
but in mainline it is "ti,timers". With this debug feature, it is easy to see that
"timers" is not being used, and somebody has to decide whether the property is
really not used by a driver, or if the binding needs more work.
Thanks,
//richard
--
sigma star gmbh | Eduard-Bodem-Gasse 6, 6020 Innsbruck, AUT
UID/VAT Nr: ATU 66964118 | FN: 374287y
next prev parent reply other threads:[~2024-10-14 8:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-13 20:07 [PATCH] [RFC] of: Add debug aid to find unused device tree properties Richard Weinberger
2024-10-14 2:37 ` Saravana Kannan
2024-10-14 6:52 ` Richard Weinberger
2024-10-14 7:49 ` Krzysztof Kozlowski
2024-10-14 8:51 ` Richard Weinberger [this message]
2024-10-14 14:41 ` Rob Herring
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=3247761.5fSG56mABF@somecomputer \
--to=richard@sigma-star.at \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
--cc=robh@kernel.org \
--cc=saravanak@google.com \
--cc=upstream+devicetree@sigma-star.at \
/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;
as well as URLs for NNTP newsgroup(s).