From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] arm: dts: imx6* Add clock-names for all ssi nodes
Date: Wed, 30 Apr 2014 14:41:06 +0800 [thread overview]
Message-ID: <20140430064104.GE16727@dragon> (raw)
In-Reply-To: <1398694356-22511-3-git-send-email-mpa@pengutronix.de>
On Mon, Apr 28, 2014 at 04:12:35PM +0200, Markus Pargmann wrote:
> There are two possible clocks now, baud and ipg. To avoid any issues,
> add clock-names to all ssi device nodes.
>
> Signed-off-by: Markus Pargmann <mpa@pengutronix.de>
> ---
> arch/arm/boot/dts/imx6qdl.dtsi | 3 +++
> arch/arm/boot/dts/imx6sl.dtsi | 3 +++
> 2 files changed, 6 insertions(+)
>
> diff --git a/arch/arm/boot/dts/imx6qdl.dtsi b/arch/arm/boot/dts/imx6qdl.dtsi
> index b230c09..288c76e 100644
> --- a/arch/arm/boot/dts/imx6qdl.dtsi
> +++ b/arch/arm/boot/dts/imx6qdl.dtsi
> @@ -257,6 +257,7 @@
> reg = <0x02028000 0x4000>;
> interrupts = <0 46 IRQ_TYPE_LEVEL_HIGH>;
> clocks = <&clks 178>;
> + clock-names = "ipg";
I'd like to make such change at the time when we have multiple clocks to
define here.
Shawn
> dmas = <&sdma 37 1 0>,
> <&sdma 38 1 0>;
> dma-names = "rx", "tx";
> @@ -271,6 +272,7 @@
> reg = <0x0202c000 0x4000>;
> interrupts = <0 47 IRQ_TYPE_LEVEL_HIGH>;
> clocks = <&clks 179>;
> + clock-names = "ipg";
> dmas = <&sdma 41 1 0>,
> <&sdma 42 1 0>;
> dma-names = "rx", "tx";
> @@ -285,6 +287,7 @@
> reg = <0x02030000 0x4000>;
> interrupts = <0 48 IRQ_TYPE_LEVEL_HIGH>;
> clocks = <&clks 180>;
> + clock-names = "ipg";
> dmas = <&sdma 45 1 0>,
> <&sdma 46 1 0>;
> dma-names = "rx", "tx";
> diff --git a/arch/arm/boot/dts/imx6sl.dtsi b/arch/arm/boot/dts/imx6sl.dtsi
> index 3cb4941..36da35c 100644
> --- a/arch/arm/boot/dts/imx6sl.dtsi
> +++ b/arch/arm/boot/dts/imx6sl.dtsi
> @@ -231,6 +231,7 @@
> reg = <0x02028000 0x4000>;
> interrupts = <0 46 IRQ_TYPE_LEVEL_HIGH>;
> clocks = <&clks IMX6SL_CLK_SSI1>;
> + clock-names = "ipg";
> dmas = <&sdma 37 1 0>,
> <&sdma 38 1 0>;
> dma-names = "rx", "tx";
> @@ -245,6 +246,7 @@
> reg = <0x0202c000 0x4000>;
> interrupts = <0 47 IRQ_TYPE_LEVEL_HIGH>;
> clocks = <&clks IMX6SL_CLK_SSI2>;
> + clock-names = "ipg";
> dmas = <&sdma 41 1 0>,
> <&sdma 42 1 0>;
> dma-names = "rx", "tx";
> @@ -259,6 +261,7 @@
> reg = <0x02030000 0x4000>;
> interrupts = <0 48 IRQ_TYPE_LEVEL_HIGH>;
> clocks = <&clks IMX6SL_CLK_SSI3>;
> + clock-names = "ipg";
> dmas = <&sdma 45 1 0>,
> <&sdma 46 1 0>;
> dma-names = "rx", "tx";
> --
> 1.9.1
>
next prev parent reply other threads:[~2014-04-30 6:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 14:12 [PATCH 0/3] ARM: dts: imx6 fsl-ssi and i2c4 Markus Pargmann
2014-04-28 14:12 ` [PATCH 1/3] arm: dts: imx6qdl, remove fsl,ssi-dma-events Markus Pargmann
2014-04-30 6:37 ` Shawn Guo
2014-04-30 7:01 ` Markus Pargmann
2014-04-28 14:12 ` [PATCH 2/3] arm: dts: imx6* Add clock-names for all ssi nodes Markus Pargmann
2014-04-30 6:41 ` Shawn Guo [this message]
2014-04-30 7:10 ` Markus Pargmann
2014-04-28 14:12 ` [PATCH 3/3] ARM: dts: imx6dl, fix i2c4 device node Markus Pargmann
2014-04-30 6:42 ` Shawn Guo
2014-04-30 7:02 ` Markus Pargmann
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=20140430064104.GE16727@dragon \
--to=shawn.guo@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).