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:14:13 +0200 [thread overview]
Message-ID: <1bc74bc7-22e8-3fef-b4e2-a5570cfa93c2@linaro.org> (raw)
In-Reply-To: <AM9PR04MB82743C17EADBFB1CD970BFB0898F9@AM9PR04MB8274.eurprd04.prod.outlook.com>
On 19/07/2022 21:28, Shenwei Wang wrote:
>>>>
>>>> Didn't you ignore (again) comments?
>>>
>>> The SoC requires two Crystal clock inputs, one is 24MHz and the other is 32KHz.
>> The board design doesn't have an option to change the values. That's why we
>> keep the nodes here.
>>
>> It's the same everywhere, nothing new here. Where is the clock? On the board.
>> Not in the Soc. For convenience clock could be here, but at least the frequency
>> by convention is put to the board.
>
> It is a little different here. Although the XTAL itself is on the board, a user has no choice here to select the clock frequency. It must use the 24MHz and 32KHz XTALs, and the two frequencies can't be changed. This is the mandatory requirement.
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?
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-07-19 20:14 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 [this message]
2022-07-19 20:33 ` Shenwei Wang
2022-07-19 20:50 ` 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=1bc74bc7-22e8-3fef-b4e2-a5570cfa93c2@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).