From: Bai Ping <b51503@freescale.com>
To: shawnguo@kernel.org, kernel@pengutronix.de
Cc: l.stach@pengutronix.de, robh+dt@kernel.org, pawel.moll@arm.com,
mturquette@baylibre.com, sboyd@codeaurora.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-clk@vger.kernel.org
Subject: [PATCH 2/3] ARM: dts: imx: modify the clocks used by cpufreq driver
Date: Tue, 24 Nov 2015 18:25:15 +0800 [thread overview]
Message-ID: <1448360716-1741-2-git-send-email-b51503@freescale.com> (raw)
In-Reply-To: <1448360716-1741-1-git-send-email-b51503@freescale.com>
As on i.MX7D, we using a virtual arm clk for CPU frequency
scaling, so correct the clocks info used by the cpufreq driver.
Signed-off-by: Bai Ping <b51503@freescale.com>
---
arch/arm/boot/dts/imx7d.dtsi | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/arch/arm/boot/dts/imx7d.dtsi b/arch/arm/boot/dts/imx7d.dtsi
index ebc053a..489604a 100644
--- a/arch/arm/boot/dts/imx7d.dtsi
+++ b/arch/arm/boot/dts/imx7d.dtsi
@@ -85,9 +85,7 @@
792000 975000
>;
clock-latency = <61036>; /* two CLK32 periods */
- clocks = <&clks IMX7D_ARM_A7_ROOT_CLK>, <&clks IMX7D_ARM_A7_ROOT_SRC>,
- <&clks IMX7D_PLL_ARM_MAIN_CLK>, <&clks IMX7D_PLL_SYS_MAIN_CLK>;
- clock-names = "arm", "arm_root_src", "pll_arm", "pll_sys_main";
+ clocks = <&clks IMX7D_CLK_ARM>;
};
cpu1: cpu@1 {
--
1.9.1
next prev parent reply other threads:[~2015-11-24 10:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 10:25 [PATCH 1/3] clk: imx: Add a virtual arm clk on i.mx7d Bai Ping
2015-11-24 10:25 ` Bai Ping [this message]
2015-11-24 10:25 ` [PATCH 3/3] ARM: imx: enable cpufreq device " Bai Ping
[not found] ` <1448360716-1741-1-git-send-email-b51503-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2015-11-25 10:53 ` [PATCH 1/3] clk: imx: Add a virtual arm clk " Lucas Stach
2015-12-02 5:40 ` Shawn Guo
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=1448360716-1741-2-git-send-email-b51503@freescale.com \
--to=b51503@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.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).