From: Loc Ho <lho@apm.com>
To: mturquette@baylibre.com, sboyd@codeaurora.org
Cc: linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
patches@apm.com, Loc Ho <lho@apm.com>
Subject: [PATCH v2 3/3] arm64: Update Merlin DT PCP PLL clock node for v2 hardware
Date: Tue, 19 Jan 2016 19:27:43 -0700 [thread overview]
Message-ID: <1453256863-15092-4-git-send-email-lho@apm.com> (raw)
In-Reply-To: <1453256863-15092-1-git-send-email-lho@apm.com>
Update Merlin DT PCP PLL clock node to reflect compatible
string change to reflect v2 hardware.
Signed-off-by: Loc Ho <lho@apm.com>
---
arch/arm64/boot/dts/apm/apm-shadowcat.dtsi | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/arm64/boot/dts/apm/apm-shadowcat.dtsi b/arch/arm64/boot/dts/apm/apm-shadowcat.dtsi
index 5d87a3d..83d293e 100644
--- a/arch/arm64/boot/dts/apm/apm-shadowcat.dtsi
+++ b/arch/arm64/boot/dts/apm/apm-shadowcat.dtsi
@@ -224,7 +224,7 @@
};
socpll: socpll@17000120 {
- compatible = "apm,xgene-socpll-clock";
+ compatible = "apm,xgene-socpll-v2-clock";
#clock-cells = <1>;
clocks = <&refclk 0>;
reg = <0x0 0x17000120 0x0 0x1000>;
--
1.7.1
next prev parent reply other threads:[~2016-01-20 2:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 2:27 [PATCH v2 0/3] clk: xgene: Add SoC and PMD PLL clocks with v2 hardware Loc Ho
2016-01-20 2:27 ` [PATCH v2 1/3] Documentation: Update APM X-Gene clock binding for " Loc Ho
2016-01-30 0:33 ` Stephen Boyd
2016-01-20 2:27 ` [PATCH v2 2/3] clk: xgene: Add SoC and PMD PLL clocks with " Loc Ho
2016-01-29 20:58 ` Stephen Boyd
2016-01-29 21:44 ` Loc Ho
2016-01-30 0:33 ` Stephen Boyd
2016-01-20 2:27 ` Loc Ho [this message]
2016-01-29 20:58 ` [PATCH v2 3/3] arm64: Update Merlin DT PCP PLL clock node for " Stephen Boyd
2016-01-29 21:46 ` Loc Ho
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=1453256863-15092-4-git-send-email-lho@apm.com \
--to=lho@apm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=patches@apm.com \
--cc=sboyd@codeaurora.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