From: Joel Fernandes <joelf@ti.com>
To: George Cherian <george.cherian@ti.com>
Cc: linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, bcousson@baylibre.com,
tony@atomide.com, rob.herring@calxeda.com, pawel.moll@arm.com,
mark.rutland@arm.com, swarren@wwwdotorg.org,
ijc+devicetree@hellion.org.uk, linux@arm.linux.org.uk,
Vinod Koul <vinod.koul@intel.com>
Subject: Re: [PATCH] arm: dts: am33xx: Add mmc nodes for am33xx platform
Date: Fri, 6 Sep 2013 13:21:46 -0500 [thread overview]
Message-ID: <522A1D3A.8000301@ti.com> (raw)
In-Reply-To: <1378455712-17379-1-git-send-email-george.cherian@ti.com>
Hi George,
On 09/06/2013 03:21 AM, George Cherian wrote:
> Add mmc nodes for am33xx platforms
>
> Signed-off-by: George Cherian <george.cherian@ti.com>
> ---
> Verified after applying [1] and [2]
> [1] - [PATCH v4 0/6] dma: edma: Support scatter-lists of any length - https://lkml.org/lkml/2013/8/29/466
> [2] - [PATCH v2] ARM: dts: add AM33XX EDMA support - https://lkml.org/lkml/2013/8/26/57
Thanks for the verification.
But, this patch should not be applied on its own as it a part of a bigger patch
I had submitted earlier that includes DTS for other derivative boards and
bindings Documentation. [3] That's the one to be applied and should be applied
only after the above patches are merged. I will resubmit this later again once
pending EDMA changes are merged. Thanks.
[3] https://lkml.org/lkml/2013/6/25/781
Regards,
-Joel
> arch/arm/boot/dts/am33xx.dtsi | 35 +++++++++++++++++++++++++++++++++++
> 1 file changed, 35 insertions(+)
>
> diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
> index b0badff..1df512d 100644
> --- a/arch/arm/boot/dts/am33xx.dtsi
> +++ b/arch/arm/boot/dts/am33xx.dtsi
> @@ -236,6 +236,41 @@
> status = "disabled";
> };
>
> + mmc1: mmc@48061000 {
> + compatible = "ti,omap4-hsmmc";
> + reg = <0x48060000 0x1000>;
> + interrupts = <64>;
> + ti,hwmods = "mmc1";
> + ti,dual-volt;
> + ti,needs-special-reset;
> + ti,needs-special-hs-handling;
> + dmas = <&edma 24
> + &edma 25>;
> + dma-names = "tx", "rx";
> + status = "disabled";
> + };
> +
> + mmc2: mmc@481d8000 {
> + compatible = "ti,omap4-hsmmc";
> + reg = <0x481d8000 0x1000>;
> + interrupts = <28>;
> + ti,hwmods = "mmc2";
> + ti,needs-special-reset;
> + dmas = <&edma 2
> + &edma 3>;
> + dma-names = "tx", "rx";
> + status = "disabled";
> + };
> +
> + mmc3: mmc@47810000 {
> + compatible = "ti,omap4-hsmmc";
> + reg = <0x47810000 0x1000>;
> + interrupts = <29>;
> + ti,hwmods = "mmc3";
> + ti,needs-special-reset;
> + status = "disabled";
> + };
> +
> wdt2: wdt@44e35000 {
> compatible = "ti,omap3-wdt";
> ti,hwmods = "wd_timer2";
>
prev parent reply other threads:[~2013-09-06 18:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-06 8:21 [PATCH] arm: dts: am33xx: Add mmc nodes for am33xx platform George Cherian
2013-09-06 18:21 ` Joel Fernandes [this message]
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=522A1D3A.8000301@ti.com \
--to=joelf@ti.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=george.cherian@ti.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=swarren@wwwdotorg.org \
--cc=tony@atomide.com \
--cc=vinod.koul@intel.com \
/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).