From: peng.fan@nxp.com
To: shawnguo@kernel.org, fabio.estevam@nxp.com,
kernel@pengutronix.de, aisheng.dong@nxp.com, robh+dt@kernel.org,
sboyd@kernel.org
Cc: devicetree@vger.kernel.org, Peng Fan <peng.fan@nxp.com>,
linux-kernel@vger.kernel.org, linux-imx@nxp.com,
leonard.crestez@nxp.com, daniel.baluta@nxp.com,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
l.stach@pengutronix.de
Subject: [PATCH 0/3] imx8m: add mu support
Date: Wed, 20 May 2020 10:04:35 +0800 [thread overview]
Message-ID: <1589940278-3680-1-git-send-email-peng.fan@nxp.com> (raw)
From: Peng Fan <peng.fan@nxp.com>
patch 1,3 is to add mu node
Patch 2 is to add mu root clk for i.MX8MP
Patch 1,3 is not merged, since patch 3 depends on patch 2 to make mu work.
Peng Fan (3):
arm64: dts: imx8m: add mu node
clk: imx8mp: add mu root clk
arm64: dts: imx8mp: add mu node
arch/arm64/boot/dts/freescale/imx8mm.dtsi | 9 +++++++++
arch/arm64/boot/dts/freescale/imx8mn.dtsi | 9 +++++++++
arch/arm64/boot/dts/freescale/imx8mp.dtsi | 9 +++++++++
arch/arm64/boot/dts/freescale/imx8mq.dtsi | 9 +++++++++
drivers/clk/imx/clk-imx8mp.c | 1 +
5 files changed, 37 insertions(+)
--
2.16.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:[~2020-05-20 2:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 2:04 peng.fan [this message]
2020-05-20 2:04 ` [PATCH 1/3] arm64: dts: imx8m: add mu node peng.fan
2020-05-20 6:45 ` Aisheng Dong
2020-05-20 2:04 ` [PATCH 2/3] clk: imx8mp: add mu root clk peng.fan
2020-05-20 6:46 ` Aisheng Dong
2020-05-20 2:04 ` [PATCH 3/3] arm64: dts: imx8mp: add mu node peng.fan
2020-05-20 2:59 ` Fabio Estevam
2020-05-20 3:01 ` Peng Fan
2020-05-20 3:06 ` Fabio Estevam
2020-05-20 3:06 ` Peng Fan
2020-05-20 6:50 ` 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=1589940278-3680-1-git-send-email-peng.fan@nxp.com \
--to=peng.fan@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=leonard.crestez@nxp.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=robh+dt@kernel.org \
--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