linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Yangbo Lu <yangbo.lu@nxp.com>
To: <linux-mmc@vger.kernel.org>, <linuxppc-dev@lists.ozlabs.org>,
	<devicetree@vger.kernel.org>
Cc: <ulf.hansson@linaro.org>, <scott.wood@nxp.com>,
	Rob Herring <robh+dt@kernel.org>, Yangbo Lu <yangbo.lu@nxp.com>
Subject: [PATCH 1/2] powerpc/85xx: adapt QorIQ eSDHC to the new clocking model
Date: Wed, 20 Apr 2016 18:20:43 +0800	[thread overview]
Message-ID: <1461147644-18041-1-git-send-email-yangbo.lu@nxp.com> (raw)

Provide clocks property instead of clock-frequency for QorIQ eSDHC
dts node to adapt to the new clocking model, so that the driver
could get clock value by the common clk API and the u-boot could
remove the clock fixup.

Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
---
 arch/powerpc/boot/dts/fsl/qoriq-esdhc-0.dtsi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/powerpc/boot/dts/fsl/qoriq-esdhc-0.dtsi b/arch/powerpc/boot/dts/fsl/qoriq-esdhc-0.dtsi
index 20835ae..ddbe562 100644
--- a/arch/powerpc/boot/dts/fsl/qoriq-esdhc-0.dtsi
+++ b/arch/powerpc/boot/dts/fsl/qoriq-esdhc-0.dtsi
@@ -36,5 +36,5 @@ sdhc: sdhc@114000 {
 	compatible = "fsl,esdhc";
 	reg = <0x114000 0x1000>;
 	interrupts = <48 2 0 0>;
-	clock-frequency = <0>;
+	clocks = <&clockgen 4 1>;
 };
-- 
2.1.0.27.g96db324

             reply	other threads:[~2016-04-20 10:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-20 10:20 Yangbo Lu [this message]
2016-04-20 10:20 ` [PATCH 2/2] mmc: sdhci-pltfm: get clock through the common clk APIs Yangbo Lu
2016-04-21 23:08 ` [PATCH 1/2] powerpc/85xx: adapt QorIQ eSDHC to the new clocking model Scott Wood
2016-04-26  6:19   ` Yangbo Lu
2016-04-26  6:29   ` Yangbo Lu
2016-04-26  6:31     ` Scott Wood

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=1461147644-18041-1-git-send-email-yangbo.lu@nxp.com \
    --to=yangbo.lu@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=robh+dt@kernel.org \
    --cc=scott.wood@nxp.com \
    --cc=ulf.hansson@linaro.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).