From: Krzysztof Kozlowski <krzk@kernel.org>
To: Peng Fan <peng.fan@nxp.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Stephen Boyd <sboyd@kernel.org>
Cc: "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, Frank Li <frank.li@nxp.com>
Subject: Re: Question: use nodename clock-<freq> for fixed-clock nodes
Date: Wed, 2 Jul 2025 14:02:32 +0200 [thread overview]
Message-ID: <9ecb8e5f-e78b-4bff-b3c6-d968d1944911@kernel.org> (raw)
In-Reply-To: <PAXPR04MB84593D0C225D85065C5F60078840A@PAXPR04MB8459.eurprd04.prod.outlook.com>
On 02/07/2025 13:47, Peng Fan wrote:
> Hi All,
>
> I am thinking to write a script to convert all the "fixed-clock"
> nodes that have clock-frequency property to use new node
> name "clock-<freq>".
>
> Then we could drop this from fixed-clock.yaml
> "
> - description: Any name allowed
> deprecated: true
> "
>
> I am not sure whether this work is preferred or this is
> an ABI break because of nodename change.
>
Pretty huge churn for little impact, IMO. Considering the node name is
relevant (it will not be ABI break... it will be just runtime break), if
there is no output names, you would need to get extensive testing, which
I think we both know you did not plan to.
So no...
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-07-02 12:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 11:47 Question: use nodename clock-<freq> for fixed-clock nodes Peng Fan
2025-07-02 12:02 ` Krzysztof Kozlowski [this message]
2025-07-02 13:37 ` Peng Fan
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=9ecb8e5f-e78b-4bff-b3c6-d968d1944911@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frank.li@nxp.com \
--cc=krzk+dt@kernel.org \
--cc=peng.fan@nxp.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.