From: Aisheng Dong <aisheng.dong@nxp.com>
To: "linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>
Cc: Aisheng Dong <aisheng.dong@nxp.com>,
"sboyd@kernel.org" <sboyd@kernel.org>,
"mturquette@baylibre.com" <mturquette@baylibre.com>,
dl-linux-imx <linux-imx@nxp.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH 0/4] clk: imx: scu: add parsing clocks from device tree support
Date: Thu, 21 Feb 2019 18:03:39 +0000 [thread overview]
Message-ID: <1550771836-10014-1-git-send-email-aisheng.dong@nxp.com> (raw)
This patch series is a preparation for the MX8 Architecture improvement.
As for IMX SCU based platforms like MX8QM and MX8QXP, they are comprised
of a couple of SS(Subsystems) while most of them within the same SS
can be shared. e.g. Clocks, Devices and etc.
However, current device tree is heavily depends on Clocks IDs defined which
cause some troubles in writing the common <soc>-ss-xx.dtsi file.
This patch series adds a new binding to support parsing clocks from device tree
which can fully decouple the dependency of Clock IDs in device tree.
This can make the clock driver much easily to be maintained in the future and
avoid writing a lot of duplicated codes.
Dong Aisheng (4):
dt-bindings: firmware: imx-scu: new binding to parse clocks from
device tree
dt-bindings: clock: imx-lpcg: add support to parse clocks from device
tree
clk: imx: imx8qxp: add parsing clocks from device tree
clk: imx: imx8qxp-lpcg: add parsing clocks from device tree
.../devicetree/bindings/arm/freescale/fsl,scu.txt | 29 +++++--
.../devicetree/bindings/clock/imx8qxp-lpcg.txt | 14 ++++
drivers/clk/imx/clk-imx8qxp-lpcg.c | 90 ++++++++++++++++++++++
drivers/clk/imx/clk-imx8qxp.c | 43 +++++++++++
include/dt-bindings/firmware/imx/rsrc.h | 17 ++++
5 files changed, 185 insertions(+), 8 deletions(-)
--
2.7.4
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-02-21 18:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 18:03 Aisheng Dong [this message]
2019-02-21 18:03 ` [PATCH 1/4] dt-bindings: firmware: imx-scu: new binding to parse clocks from device tree Aisheng Dong
2019-03-26 13:47 ` Rob Herring
2019-03-27 14:35 ` Aisheng Dong
2019-04-02 14:47 ` Aisheng Dong
2019-04-09 14:04 ` Aisheng Dong
2019-04-10 15:32 ` Rob Herring
2019-04-10 17:35 ` [EXT] " Aisheng Dong
2019-02-21 18:03 ` [PATCH 2/4] dt-bindings: clock: imx-lpcg: add support " Aisheng Dong
2019-02-25 19:46 ` Stephen Boyd
2019-02-26 10:07 ` Aisheng Dong
2019-03-18 15:10 ` Aisheng Dong
2019-04-02 14:55 ` Aisheng Dong
2019-02-21 18:03 ` [PATCH 3/4] clk: imx: imx8qxp: add parsing " Aisheng Dong
2019-02-21 18:03 ` [PATCH 4/4] clk: imx: imx8qxp-lpcg: " Aisheng Dong
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=1550771836-10014-1-git-send-email-aisheng.dong@nxp.com \
--to=aisheng.dong@nxp.com \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--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).