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 0/5] imx6qp QuadPlus: support improved enet clocking
Date: Sun, 12 Jul 2020 20:25:07 -0400 [thread overview]
Message-ID: <20200713002512.28742-1-TheSven73@gmail.com> (raw)
On the imx6qp QuadPlus, the h/w designers have improved enet clocking.
This patchset extends the clock tree to reflect the situation on QuadPlus.
This allows board designers to choose the enet clocking method by making
simple clocktree changes in the devicetree.
Default setting: external routing of enet_ref from pad to pad.
Example, change the default to enet_ref @ 125MHz clock routed internally:
&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>;
};
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
Sven Van Asbroeck (5):
ARM: mach-imx6q: do not select enet PTP clock source on QuadPlus
clk: imx: add simple regmap-backed clock mux
dt-bindings: imx6qdl-clock: add QuadPlus enet clocks
clk: imx6q: support improved enet clocking on QuadPlus
ARM: dts: imx6qp: support improved enet clocking on QuadPlus
.../bindings/clock/imx6q-clock.yaml | 2 +
arch/arm/boot/dts/imx6qp.dtsi | 3 +
arch/arm/mach-imx/mach-imx6q.c | 4 +
drivers/clk/imx/Makefile | 1 +
drivers/clk/imx/clk-imx6q.c | 46 ++++++++
drivers/clk/imx/clk-mux-regmap.c | 110 ++++++++++++++++++
drivers/clk/imx/clk.h | 7 ++
include/dt-bindings/clock/imx6qdl-clock.h | 5 +-
include/linux/mfd/syscon/imx6q-iomuxc-gpr.h | 1 +
9 files changed, 178 insertions(+), 1 deletion(-)
create mode 100644 drivers/clk/imx/clk-mux-regmap.c
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next 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 Sven Van Asbroeck [this message]
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 ` [PATCH v1 5/5] ARM: dts: imx6qp: " Sven Van Asbroeck
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-1-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).