From: "Chanho Park" <chanho61.park@samsung.com>
To: "'Krzysztof Kozlowski'" <krzysztof.kozlowski@linaro.org>,
"'Rob Herring'" <robh+dt@kernel.org>,
"'Krzysztof Kozlowski'" <krzysztof.kozlowski+dt@linaro.org>,
"'Alim Akhtar'" <alim.akhtar@samsung.com>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-samsung-soc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] arm64: dts: exynos: move XTCXO clock frequency to board in Exynos Auto v9
Date: Tue, 3 May 2022 18:37:40 +0900 [thread overview]
Message-ID: <02a301d85ed1$6e942cd0$4bbc8670$@samsung.com> (raw)
In-Reply-To: <20220503092631.174713-1-krzysztof.kozlowski@linaro.org>
> -----Original Message-----
> From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Sent: Tuesday, May 3, 2022 6:27 PM
> To: Rob Herring <robh+dt@kernel.org>; Krzysztof Kozlowski
> <krzysztof.kozlowski+dt@linaro.org>; Alim Akhtar
<alim.akhtar@samsung.com>;
> devicetree@vger.kernel.org; linux-arm-kernel@lists.infradead.org; linux-
> samsung-soc@vger.kernel.org; linux-kernel@vger.kernel.org
> Cc: Chanho Park <chanho61.park@samsung.com>; Krzysztof Kozlowski
> <krzysztof.kozlowski@linaro.org>
> Subject: [PATCH] arm64: dts: exynos: move XTCXO clock frequency to board
> in Exynos Auto v9
>
> The external oscillator - XTCXO - is an input to the SoC. It is defined
> in the Exynos Auto v9 SoC DTSI, because all boards will provide it and
> clock controller bindings expect it, however the actual frequency of the
> clock should be determined by the board.
Thanks for the update.
Reviewed-by: Chanho Park <chanho61.park@samsung.com>
Best Regards,
Chanho Park
next prev parent reply other threads:[~2022-05-03 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220503092638epcas2p368d663b2d309b1fe8ed68b8465c5ff69@epcas2p3.samsung.com>
2022-05-03 9:26 ` [PATCH] arm64: dts: exynos: move XTCXO clock frequency to board in Exynos Auto v9 Krzysztof Kozlowski
2022-05-03 9:37 ` Chanho Park [this message]
2022-05-04 8:30 ` 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='02a301d85ed1$6e942cd0$4bbc8670$@samsung.com' \
--to=chanho61.park@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=robh+dt@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