From: Abel Vesa <abel.vesa@linaro.org>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: linux-kernel@vger.kernel.org, angelo@amarulasolutions.com,
michael@amarulasolutions.com,
tommaso.merciai@amarulasolutions.com,
Chen-Yu Tsai <wenst@chromium.org>,
linux-amarula@amarulasolutions.com, anthony@amarulasolutions.com,
jagan@amarulasolutions.com, Abel Vesa <abelvesa@kernel.org>,
Adam Ford <aford173@gmail.com>,
Fabio Estevam <festevam@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Li Jun <jun.li@nxp.com>, Lucas Stach <l.stach@pengutronix.de>,
Marek Vasut <marex@denx.de>,
Markus Niebel <Markus.Niebel@ew.tq-group.com>,
Michael Turquette <mturquette@baylibre.com>,
NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>, Stephen Boyd <sboyd@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-clk@vger.kernel.org
Subject: Re: [RFC PATCH v2 11/11] arm64: dts: imx8mn: add clocks description
Date: Mon, 16 Jan 2023 16:35:59 +0200 [thread overview]
Message-ID: <Y8VgzyNxGpqSvJ2b@linaro.org> (raw)
In-Reply-To: <20230101175740.1010258-12-dario.binacchi@amarulasolutions.com>
On 23-01-01 18:57:40, Dario Binacchi wrote:
> The patch creates a unique node for each clock in the imx8mn clock
> control module (CCM).
>
> To ensure backwards compatibility it was not possible to separate the
> changes to the device tree from those applied to the clocks setup code.
> In doing so, all clocks are initialized from the device tree and the
> legacy setup code with hardwired parameters is removed.
>
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
>
> ---
>
> (no changes since v1)
>
> .../boot/dts/freescale/imx8mn-clocks.dtsi | 1885 +++++++++++++++++
> arch/arm64/boot/dts/freescale/imx8mn.dtsi | 54 +-
> drivers/clk/imx/clk-imx8mn.c | 714 ++-----
> 3 files changed, 2086 insertions(+), 567 deletions(-)
> create mode 100644 arch/arm64/boot/dts/freescale/imx8mn-clocks.dtsi
>
> diff --git a/arch/arm64/boot/dts/freescale/imx8mn-clocks.dtsi b/arch/arm64/boot/dts/freescale/imx8mn-clocks.dtsi
> new file mode 100644
> index 000000000000..21e02ea996d0
> --- /dev/null
> +++ b/arch/arm64/boot/dts/freescale/imx8mn-clocks.dtsi
> @@ -0,0 +1,1885 @@
> +// SPDX-License-Identifier: GPL-2.0-only
> +/*
> + * Device Tree Source for imx8mn clock data
> + *
> + * Copyright (c) 2022 Amarula Solutions
> + *
> + * Dario Binacchi <dario.binacchi@amarulasolutions.com>
> + */
> +
> +/ {
> + osc_32k: clock-osc-32k {
> + compatible = "fixed-clock";
> + #clock-cells = <0>;
> + clock-frequency = <32768>;
> + clock-output-names = "osc_32k";
> + };
> +
[...]
> +
> + clk_audio_pll2_bypass: clock-audio-pll2-bypass@14 {
> + compatible = "fsl,imx8mn-mux-clock";
> + #clock-cells = <0>;
> + clocks = <&clk_audio_pll2>, <&clk_audio_pll2_ref_sel>;
> + fsl,anatop = <&anatop 0x14>;
> + fsl,bit-shift = <16>;
> + fsl,set-rate-parent;
NACK. I'm sorry, but this creates a huge effort on maintaining the
bindings. Plus the vendor specific properties will keep increasing.
I don't think Rob and Krzysztof will be OK with this either.
> + clock-output-names = "audio_pll2_bypass";
> + };
> +
> + clk_audio_pll2_out: clock-audio-pll2-out@14 {
> + compatible = "fsl,imx8mn-gate-clock";
> + #clock-cells = <0>;
> + clocks = <&clk_audio_pll2_bypass>;
> + fsl,anatop = <&anatop 0x14>;
> + fsl,bit-shift = <13>;
> + clock-output-names = "audio_pll2_out";
> + };
> +
[...]
> --
> 2.32.0
>
next prev parent reply other threads:[~2023-01-16 14:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-01 17:57 [RFC PATCH v2 00/11] clk: imx8mn: setup clocks from the device tree Dario Binacchi
2023-01-01 17:57 ` [RFC PATCH v2 10/11] arm64: dts: imx8mn: add dumy clock Dario Binacchi
2023-01-01 17:57 ` [RFC PATCH v2 11/11] arm64: dts: imx8mn: add clocks description Dario Binacchi
2023-01-16 14:35 ` Abel Vesa [this message]
2023-01-20 17:47 ` Dario Binacchi
2023-01-02 23:04 ` [RFC PATCH v2 00/11] clk: imx8mn: setup clocks from the device tree Marek Vasut
2023-01-04 16:09 ` Dario Binacchi
2023-01-25 21:10 ` Stephen Boyd
2023-01-26 10:49 ` Michael Nazzareno Trimarchi
2023-02-10 22:49 ` Stephen Boyd
2023-02-11 9:19 ` Michael Nazzareno Trimarchi
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=Y8VgzyNxGpqSvJ2b@linaro.org \
--to=abel.vesa@linaro.org \
--cc=Markus.Niebel@ew.tq-group.com \
--cc=abelvesa@kernel.org \
--cc=aford173@gmail.com \
--cc=angelo@amarulasolutions.com \
--cc=anthony@amarulasolutions.com \
--cc=dario.binacchi@amarulasolutions.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=jagan@amarulasolutions.com \
--cc=jun.li@nxp.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=l.stach@pengutronix.de \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=michael@amarulasolutions.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=shawnguo@kernel.org \
--cc=tommaso.merciai@amarulasolutions.com \
--cc=wenst@chromium.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).