From: Felipe Balbi <balbi@ti.com>
To: Dave Gerlach <d-gerlach@ti.com>, Tony Lindgren <tony@atomide.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
devicetree@vger.kernel.org, Paul Walmsley <paul@pwsan.com>
Subject: Re: [PATCH 2/2] ARM: dts: am4372: Add emif node
Date: Tue, 2 Jun 2015 14:22:28 -0500 [thread overview]
Message-ID: <20150602192228.GF9623@saruman.tx.rr.com> (raw)
In-Reply-To: <1430933133-33412-3-git-send-email-d-gerlach@ti.com>
[-- Attachment #1: Type: text/plain, Size: 2016 bytes --]
On Wed, May 06, 2015 at 12:25:33PM -0500, Dave Gerlach wrote:
> Add node for TI AM4372 EMIF.
>
> Signed-off-by: Dave Gerlach <d-gerlach@ti.com>
Tony, this patch fixes the regression I just reported at [1], care to
pick this one up ?
Tested-by: Felipe Balbi <balbi@ti.com>
Acked-by: Felipe Balbi <balbi@ti.com>
[1] http://marc.info/?l=linux-omap&m=143327283632248&w=2
> ---
> Documentation/devicetree/bindings/memory-controllers/ti/emif.txt | 1 +
> arch/arm/boot/dts/am4372.dtsi | 6 ++++++
> 2 files changed, 7 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/memory-controllers/ti/emif.txt b/Documentation/devicetree/bindings/memory-controllers/ti/emif.txt
> index 938f8e1..0db6047 100644
> --- a/Documentation/devicetree/bindings/memory-controllers/ti/emif.txt
> +++ b/Documentation/devicetree/bindings/memory-controllers/ti/emif.txt
> @@ -8,6 +8,7 @@ of the EMIF IP and memory parts attached to it.
> Required properties:
> - compatible : Should be of the form "ti,emif-<ip-rev>" where <ip-rev>
> is the IP revision of the specific EMIF instance.
> + For am437x should be ti,emif-am4372.
>
> - phy-type : <u32> indicating the DDR phy type. Following are the
> allowed values
> diff --git a/arch/arm/boot/dts/am4372.dtsi b/arch/arm/boot/dts/am4372.dtsi
> index c80a3e2..9521a38 100644
> --- a/arch/arm/boot/dts/am4372.dtsi
> +++ b/arch/arm/boot/dts/am4372.dtsi
> @@ -132,6 +132,12 @@
> };
> };
>
> + emif: emif@4c000000 {
> + compatible = "ti,emif-am4372";
> + reg = <0x4c000000 0x1000000>;
> + ti,hwmods = "emif";
> + };
> +
> edma: edma@49000000 {
> compatible = "ti,edma3";
> ti,hwmods = "tpcc", "tptc0", "tptc1", "tptc2";
> --
> 2.3.6
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-06-02 19:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 17:25 [PATCH 0/2] ARM: OMAP2+: AM4372: Add emif hwmod and dt node Dave Gerlach
2015-05-06 17:25 ` [PATCH 1/2] ARM: OMAP: AM43xx hwmod: Add data for am43xx emif hwmod Dave Gerlach
[not found] ` <1430933133-33412-2-git-send-email-d-gerlach-l0cyMroinI0@public.gmane.org>
2015-06-02 18:37 ` Paul Walmsley
2015-05-06 17:25 ` [PATCH 2/2] ARM: dts: am4372: Add emif node Dave Gerlach
2015-06-02 19:22 ` Felipe Balbi [this message]
2015-06-02 19:58 ` Tony Lindgren
[not found] ` <20150602195841.GM30984-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2015-07-06 12:14 ` Tony Lindgren
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=20150602192228.GF9623@saruman.tx.rr.com \
--to=balbi@ti.com \
--cc=d-gerlach@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=tony@atomide.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).