From: Cory Tusar <cory.tusar@pid1solutions.com> To: shawnguo@kernel.org, kernel@pengutronix.de, stefan@agner.ch Cc: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com, ijc+devicetree@hellion.org.uk, galak@codeaurora.org, linux@arm.linux.org.uk, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, andrew@lunn.ch, Cory Tusar <cory.tusar@pid1solutions.com> Subject: [PATCH 1/1] ARM: dts: vfxxx: Include support for esdhc0 functionality. Date: Wed, 8 Jul 2015 16:51:06 -0400 [thread overview] Message-ID: <1436388666-29376-2-git-send-email-cory.tusar@pid1solutions.com> (raw) In-Reply-To: <1436388666-29376-1-git-send-email-cory.tusar@pid1solutions.com> Extend the existing Vybrid eSDHC devicetree implementation to also describe the esdhc0 functional block. Tested on a custom VF610-based board with a Toshiba THGBM1G5D2EBAI7 eMMC module attached to esdhc0. Signed-off-by: Cory Tusar <cory.tusar@pid1solutions.com> --- arch/arm/boot/dts/vfxxx.dtsi | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/arch/arm/boot/dts/vfxxx.dtsi b/arch/arm/boot/dts/vfxxx.dtsi index 4aa3351..7e97017 100644 --- a/arch/arm/boot/dts/vfxxx.dtsi +++ b/arch/arm/boot/dts/vfxxx.dtsi @@ -445,6 +445,17 @@ status = "disabled"; }; + esdhc0: esdhc@400b1000 { + compatible = "fsl,imx53-esdhc"; + reg = <0x400b1000 0x1000>; + interrupts = <27 IRQ_TYPE_LEVEL_HIGH>; + clocks = <&clks VF610_CLK_IPG_BUS>, + <&clks VF610_CLK_PLATFORM_BUS>, + <&clks VF610_CLK_ESDHC0>; + clock-names = "ipg", "ahb", "per"; + status = "disabled"; + }; + esdhc1: esdhc@400b2000 { compatible = "fsl,imx53-esdhc"; reg = <0x400b2000 0x1000>; -- 2.3.6
WARNING: multiple messages have this Message-ID (diff)
From: cory.tusar@pid1solutions.com (Cory Tusar) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 1/1] ARM: dts: vfxxx: Include support for esdhc0 functionality. Date: Wed, 8 Jul 2015 16:51:06 -0400 [thread overview] Message-ID: <1436388666-29376-2-git-send-email-cory.tusar@pid1solutions.com> (raw) In-Reply-To: <1436388666-29376-1-git-send-email-cory.tusar@pid1solutions.com> Extend the existing Vybrid eSDHC devicetree implementation to also describe the esdhc0 functional block. Tested on a custom VF610-based board with a Toshiba THGBM1G5D2EBAI7 eMMC module attached to esdhc0. Signed-off-by: Cory Tusar <cory.tusar@pid1solutions.com> --- arch/arm/boot/dts/vfxxx.dtsi | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/arch/arm/boot/dts/vfxxx.dtsi b/arch/arm/boot/dts/vfxxx.dtsi index 4aa3351..7e97017 100644 --- a/arch/arm/boot/dts/vfxxx.dtsi +++ b/arch/arm/boot/dts/vfxxx.dtsi @@ -445,6 +445,17 @@ status = "disabled"; }; + esdhc0: esdhc at 400b1000 { + compatible = "fsl,imx53-esdhc"; + reg = <0x400b1000 0x1000>; + interrupts = <27 IRQ_TYPE_LEVEL_HIGH>; + clocks = <&clks VF610_CLK_IPG_BUS>, + <&clks VF610_CLK_PLATFORM_BUS>, + <&clks VF610_CLK_ESDHC0>; + clock-names = "ipg", "ahb", "per"; + status = "disabled"; + }; + esdhc1: esdhc at 400b2000 { compatible = "fsl,imx53-esdhc"; reg = <0x400b2000 0x1000>; -- 2.3.6
next prev parent reply other threads:[~2015-07-08 20:51 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-07-08 20:51 [PATCH 0/1] Add support for esdhc0 on Vybrid Cory Tusar 2015-07-08 20:51 ` Cory Tusar 2015-07-08 20:51 ` Cory Tusar [this message] 2015-07-08 20:51 ` [PATCH 1/1] ARM: dts: vfxxx: Include support for esdhc0 functionality Cory Tusar 2015-07-09 15:07 ` Stefan Agner 2015-07-09 15:07 ` Stefan Agner 2015-07-14 3:38 ` Shawn Guo 2015-07-14 3:38 ` Shawn Guo 2015-07-14 3:38 ` Shawn Guo 2015-07-09 6:07 ` [PATCH 0/1] Add support for esdhc0 on Vybrid Holger Schurig 2015-07-09 6:07 ` Holger Schurig 2015-07-09 6:07 ` Holger Schurig 2015-07-09 6:13 ` Stefan Agner 2015-07-09 6:13 ` Stefan Agner 2015-07-09 12:40 ` Cory Tusar 2015-07-09 12:40 ` Cory Tusar 2015-07-09 12:40 ` Cory Tusar
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=1436388666-29376-2-git-send-email-cory.tusar@pid1solutions.com \ --to=cory.tusar@pid1solutions.com \ --cc=andrew@lunn.ch \ --cc=devicetree@vger.kernel.org \ --cc=galak@codeaurora.org \ --cc=ijc+devicetree@hellion.org.uk \ --cc=kernel@pengutronix.de \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux@arm.linux.org.uk \ --cc=mark.rutland@arm.com \ --cc=pawel.moll@arm.com \ --cc=robh+dt@kernel.org \ --cc=shawnguo@kernel.org \ --cc=stefan@agner.ch \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.