From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Shenwei Wang <shenwei.wang@nxp.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Peng Fan <peng.fan@nxp.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
dl-linux-imx <linux-imx@nxp.com>
Subject: Re: [EXT] Re: [PATCH RESEND v3 3/3] arm64: dts: imx: add imx8dxl support
Date: Tue, 19 Jul 2022 22:50:09 +0200 [thread overview]
Message-ID: <4b104418-6dfd-2254-957b-7f5d603e9288@linaro.org> (raw)
In-Reply-To: <AM9PR04MB82743D98F111A5DE3DC7832E898F9@AM9PR04MB8274.eurprd04.prod.outlook.com>
On 19/07/2022 22:33, Shenwei Wang wrote:
>>
>> I understand, it's the same on many other boards. Still the clock is not part of
>> SoC design. It is always on the board. iMX is not special here, so why would you
>> expect here an exception?
>
> Actually you cannot simply say that the clock is not part of SoC design, but this is not important. As long as it is a reasonable and consistent rule, we just follow it. However, it seems the rule is changing again here? This is just following what the current upstreaming implementation does like iMX8QXP, iMX8MM, ... etc. Are you taking iMX8DXL as a special one? Or are we going to change all the current implementations to follow this rule?
All implementations should follow this rule.
Best regards,
Krzysztof
prev parent reply other threads:[~2022-07-19 20:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 23:12 [PATCH RESEND v3 0/3] add imx8dxl evk support Shenwei Wang
2022-07-15 23:12 ` [PATCH RESEND v3 1/3] dt-bindings: firmware: add missing resource IDs for imx8dxl Shenwei Wang
2022-07-15 23:12 ` [PATCH RESEND v3 2/3] dt-bindings: arm: imx: update fsl.yaml " Shenwei Wang
2022-07-15 23:12 ` [PATCH RESEND v3 3/3] arm64: dts: imx: add imx8dxl support Shenwei Wang
2022-07-18 13:00 ` Krzysztof Kozlowski
2022-07-18 18:50 ` [EXT] " Shenwei Wang
2022-07-19 6:36 ` Krzysztof Kozlowski
2022-07-19 19:28 ` Shenwei Wang
2022-07-19 20:14 ` Krzysztof Kozlowski
2022-07-19 20:33 ` Shenwei Wang
2022-07-19 20:50 ` Krzysztof Kozlowski [this message]
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=4b104418-6dfd-2254-957b-7f5d603e9288@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-imx@nxp.com \
--cc=peng.fan@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=shenwei.wang@nxp.com \
/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).