imx.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: E Shattow <e@freeshell.de>
To: Peng Fan <peng.fan@nxp.com>,
	Marek Vasut <marek.vasut@mailbox.org>,
	"Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	Abel Vesa <abelvesa@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"imx@lists.linux.dev" <imx@lists.linux.dev>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>
Subject: Re: [PATCH v1] dts: arm64: freescale: move imx9*-clock.h imx9*-power.h into dt-bindings
Date: Wed, 1 Oct 2025 22:27:26 -0700	[thread overview]
Message-ID: <694a3d9e-4096-4782-a918-42d033737fbd@freeshell.de> (raw)
In-Reply-To: <PAXPR04MB845970863A16718967270D1A880EA@PAXPR04MB8459.eurprd04.prod.outlook.com>



On 9/10/25 00:07, Peng Fan wrote:
> Hi Marek,
> 
>> 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 ?
> 
> DT maintainers suggested to keep the files under
> arch/arm64/boot/dts/freescale/
> 
> https://lore.kernel.org/all/75ab9162-ed02-479d-92a1-7cfabff6b32e@linaro.org/
> 
> Regards
> Peng

Follow up FYI to all this is resolved from U-Boot [1] as not using the
header and duplicating the information.

1:
https://lore.kernel.org/u-boot/20250923-imx94-v1-5-cb3b65169048@oss.nxp.com/

There was yet some IRC discussion about what justification can be for
avoiding this maintenance and duplication.

I am dropping this suggestion to move imx9*-clock.h imx9*-power.h into
dt-bindings. There is some better way of doing this, maybe a future
dt-firmware includes? That is not at all my area of interest or
expertise, however. I just noticed something out-of-place and bring it
to our attention.

My great appreciation is due for the reviews and discussion about this.
Thanks, everyone!

-E

  reply	other threads:[~2025-10-02  5:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-31 20:04 [PATCH v1] dts: arm64: freescale: move imx9*-clock.h imx9*-power.h into dt-bindings E Shattow
2025-09-01  3:22 ` Peng Fan
2025-09-01  2:22   ` Marek Vasut
2025-09-01  3:33     ` Krzysztof Kozlowski
2025-09-01  6:09       ` Peng Fan
2025-09-01 10:30       ` Marek Vasut
2025-09-01 10:54         ` Krzysztof Kozlowski
2025-09-01 11:07           ` E Shattow
2025-09-01 12:15             ` Krzysztof Kozlowski
2025-09-01 23:32           ` Marek Vasut
2025-09-04  9:34             ` Peng Fan
2025-09-08 23:39               ` Marek Vasut
2025-09-10  7:07                 ` Peng Fan
2025-10-02  5:27                   ` E Shattow [this message]
2025-11-02 17:42                   ` Marek Vasut
2025-09-01  3:32 ` Krzysztof Kozlowski

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=694a3d9e-4096-4782-a918-42d033737fbd@freeshell.de \
    --to=e@freeshell.de \
    --cc=abelvesa@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marek.vasut@mailbox.org \
    --cc=mturquette@baylibre.com \
    --cc=peng.fan@nxp.com \
    --cc=peng.fan@oss.nxp.com \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=sboyd@kernel.org \
    --cc=shawnguo@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 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).