From: Shawn Guo <shawnguo@kernel.org>
To: Anson Huang <Anson.Huang@nxp.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org, angus@akkea.ca,
ping.bai@nxp.com, ccaione@baylibre.com, andrew.smirnov@gmail.com,
daniel.baluta@nxp.com, s.hauer@pengutronix.de,
daniel.lezcano@linaro.org, linux-kernel@vger.kernel.org,
abel.vesa@nxp.com, robh+dt@kernel.org, Linux-imx@nxp.com,
kernel@pengutronix.de, l.stach@pengutronix.de,
leonard.crestez@nxp.com, festevam@gmail.com, agx@sigxcpu.org,
linux-arm-kernel@lists.infradead.org, jun.li@nxp.com
Subject: Re: [PATCH 1/3] arm64: dts: imx8mq: Use correct clock for usdhc's ipg clk
Date: Mon, 7 Oct 2019 20:12:05 +0800 [thread overview]
Message-ID: <20191007121204.GI7150@dragon> (raw)
In-Reply-To: <1568869559-28611-1-git-send-email-Anson.Huang@nxp.com>
On Thu, Sep 19, 2019 at 01:05:57PM +0800, Anson Huang wrote:
> On i.MX8MQ, usdhc's ipg clock is from IMX8MQ_CLK_IPG_ROOT,
> assign it explicitly instead of using IMX8MQ_CLK_DUMMY.
>
> Signed-off-by: Anson Huang <Anson.Huang@nxp.com>
Fixes tag?
Shawn
> ---
> arch/arm64/boot/dts/freescale/imx8mq.dtsi | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/freescale/imx8mq.dtsi b/arch/arm64/boot/dts/freescale/imx8mq.dtsi
> index fd42bee..e2c95ad 100644
> --- a/arch/arm64/boot/dts/freescale/imx8mq.dtsi
> +++ b/arch/arm64/boot/dts/freescale/imx8mq.dtsi
> @@ -850,7 +850,7 @@
> "fsl,imx7d-usdhc";
> reg = <0x30b40000 0x10000>;
> interrupts = <GIC_SPI 22 IRQ_TYPE_LEVEL_HIGH>;
> - clocks = <&clk IMX8MQ_CLK_DUMMY>,
> + clocks = <&clk IMX8MQ_CLK_IPG_ROOT>,
> <&clk IMX8MQ_CLK_NAND_USDHC_BUS>,
> <&clk IMX8MQ_CLK_USDHC1_ROOT>;
> clock-names = "ipg", "ahb", "per";
> @@ -867,7 +867,7 @@
> "fsl,imx7d-usdhc";
> reg = <0x30b50000 0x10000>;
> interrupts = <GIC_SPI 23 IRQ_TYPE_LEVEL_HIGH>;
> - clocks = <&clk IMX8MQ_CLK_DUMMY>,
> + clocks = <&clk IMX8MQ_CLK_IPG_ROOT>,
> <&clk IMX8MQ_CLK_NAND_USDHC_BUS>,
> <&clk IMX8MQ_CLK_USDHC2_ROOT>;
> clock-names = "ipg", "ahb", "per";
> --
> 2.7.4
>
_______________________________________________
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:[~2019-10-07 12:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 5:05 [PATCH 1/3] arm64: dts: imx8mq: Use correct clock for usdhc's ipg clk Anson Huang
2019-09-19 5:05 ` [PATCH 2/3] arm64: dts: imx8mm: " Anson Huang
2019-09-19 7:17 ` Schrempf Frieder
2019-09-19 9:31 ` Anson Huang
2019-09-19 10:04 ` Schrempf Frieder
2019-09-19 5:05 ` [PATCH 3/3] arm64: dts: imx8mn: " Anson Huang
2019-10-07 12:12 ` Shawn Guo [this message]
2019-10-08 0:58 ` [PATCH 1/3] arm64: dts: imx8mq: " Anson Huang
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=20191007121204.GI7150@dragon \
--to=shawnguo@kernel.org \
--cc=Anson.Huang@nxp.com \
--cc=Linux-imx@nxp.com \
--cc=abel.vesa@nxp.com \
--cc=agx@sigxcpu.org \
--cc=andrew.smirnov@gmail.com \
--cc=angus@akkea.ca \
--cc=ccaione@baylibre.com \
--cc=daniel.baluta@nxp.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=jun.li@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-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ping.bai@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
/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).