linux-kernel - Re: [PATCH v1] dts: arm64: freescale: move imx9*-clock.h imx9*-power.h into dt-bindings

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <afe58aa6-0c3e-4508-8133-8e7621a0484a@mailbox.org>
Date: Tue, 9 Sep 2025 01:39:13 +0200
From: Marek Vasut <marek.vasut@...lbox.org>
To: Peng Fan <peng.fan@....nxp.com>
Cc: Krzysztof Kozlowski <krzk@...nel.org>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
 <conor+dt@...nel.org>, Shawn Guo <shawnguo@...nel.org>,
 Sascha Hauer <s.hauer@...gutronix.de>,
 Pengutronix Kernel Team <kernel@...gutronix.de>,
 Fabio Estevam <festevam@...il.com>, Abel Vesa <abelvesa@...nel.org>,
 Peng Fan <peng.fan@....com>, Michael Turquette <mturquette@...libre.com>,
 Stephen Boyd <sboyd@...nel.org>, devicetree@...r.kernel.org,
 imx@...ts.linux.dev, linux-arm-kernel@...ts.infradead.org,
 linux-kernel@...r.kernel.org, linux-clk@...r.kernel.org,
 E Shattow <e@...eshell.de>
Subject: Re: [PATCH v1] dts: arm64: freescale: move imx9*-clock.h
 imx9*-power.h into dt-bindings

On 9/4/25 11:34 AM, Peng Fan wrote:

Hi,

sorry for my late reply.

>> Instead of playing this "I found this code somewhere, so I can do
>>> whatever the same" answer the first implied question - why these are
>>> bindings? Provide arguments what do they bind.
>>
>> I am not sure how to answer this, but what I can write is, that if I scramble
>> these IDs in either the DT or the firmware (which provides the SCMI clock
>> service), then the system cannot work. I am not sure if this is the answer
>> you are looking for.
> 
> Marek,
>    Some U-Boot code indeed directly use the IDs to configure the clock without
>    relying on any drivers. Since the SCMI IDs could not be moved to dt-bindings,

Why can they not be moved to DT bindings ?

They are part of the ABI.

This is the part I do not understand, the SCMI IDs are no different than 
any other clock IDs used in DT, is that not so ?

>    the possible method to do in U-Boot is to duplicate a copy of the file,

No.