From: Sven Van Asbroeck <thesven73@gmail.com>
To: shawnguo@kernel.org, s.hauer@pengutronix.de
Cc: linux-kernel@vger.kernel.org, NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 5/5] ARM: dts: imx6qp: support improved enet clocking on QuadPlus
Date: Sun, 12 Jul 2020 20:25:12 -0400 [thread overview]
Message-ID: <20200713002512.28742-6-TheSven73@gmail.com> (raw)
In-Reply-To: <20200713002512.28742-1-TheSven73@gmail.com>
Board designers are now able to choose between all three supported
enet clocking methods, by changing the clocktree via the devicetree:
a) route enet_ref externally from pad to pad (the default):
no clock tree changes required
b) route internally on SoC from enet_ref
&fec {
assigned-clocks = <&clks IMX6QDL_CLK_ENET_PTP>,
<&clks IMX6QDL_CLK_ENET_REF>;
assigned-clock-parents = <&clks IMX6QDL_CLK_ENET_REF>;
assigned-clock-rates = <0>, <125000000>;
};
c) route external clock (from PHY or oscillator) via pad
/ {
clocks {
phy_osc: anaclk3 {
compatible = "fixed-clock";
#clock-cells = <0>;
clock-frequency = <125000000>;
};
};
};
&fec {
assigned-clocks = <&clks IMX6QDL_CLK_ENET_PTP>,
<&clks IMX6QDL_CLK_ENET_PAD>;
assigned-clock-parents = <&clks IMX6QDL_CLK_ENET_PAD>,
<&clks IMX6QDL_CLK_ANACLK3>;
};
Signed-off-by: Sven Van Asbroeck <TheSven73@gmail.com>
---
Tree: v5.8-rc4
To: Shawn Guo <shawnguo@kernel.org>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Pengutronix Kernel Team <kernel@pengutronix.de>
Cc: Fabio Estevam <festevam@gmail.com>
Cc: NXP Linux Team <linux-imx@nxp.com>
Cc: linux-kernel@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org
Cc: linux-clk@vger.kernel.org
arch/arm/boot/dts/imx6qp.dtsi | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/boot/dts/imx6qp.dtsi b/arch/arm/boot/dts/imx6qp.dtsi
index b310f13a53f2..7f81d35f56c9 100644
--- a/arch/arm/boot/dts/imx6qp.dtsi
+++ b/arch/arm/boot/dts/imx6qp.dtsi
@@ -79,6 +79,9 @@
&fec {
interrupts = <0 118 IRQ_TYPE_LEVEL_HIGH>,
<0 119 IRQ_TYPE_LEVEL_HIGH>;
+ clocks = <&clks IMX6QDL_CLK_ENET>,
+ <&clks IMX6QDL_CLK_ENET>,
+ <&clks IMX6QDL_CLK_ENET_PTP>;
};
&gpc {
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-07-13 0:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 0:25 [PATCH v1 0/5] imx6qp QuadPlus: support improved enet clocking Sven Van Asbroeck
2020-07-13 0:25 ` [PATCH v1 1/5] ARM: mach-imx6q: do not select enet PTP clock source on QuadPlus Sven Van Asbroeck
2020-07-13 0:25 ` [PATCH v1 2/5] clk: imx: add simple regmap-backed clock mux Sven Van Asbroeck
2020-07-13 0:25 ` [PATCH v1 3/5] dt-bindings: imx6qdl-clock: add QuadPlus enet clocks Sven Van Asbroeck
2020-07-13 0:25 ` [PATCH v1 4/5] clk: imx6q: support improved enet clocking on QuadPlus Sven Van Asbroeck
2020-07-13 0:25 ` Sven Van Asbroeck [this message]
2020-08-17 7:17 ` [PATCH v1 0/5] imx6qp QuadPlus: support improved enet clocking Shawn Guo
2020-08-17 7:26 ` [EXT] " Andy Duan
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=20200713002512.28742-6-TheSven73@gmail.com \
--to=thesven73@gmail.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--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=s.hauer@pengutronix.de \
--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).