devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benoit Cousson <b-cousson@ti.com>
To: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
Cc: Tony Lindgren <tony@atomide.com>,
	Russell King <linux@arm.linux.org.uk>,
	Enric Balletbo i Serra <eballetbo@gmail.com>,
	Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
	linux-omap@vger.kernel.org, devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCH v2 2/2] ARM: dts: omap3-igep0030: Add NAND flash support
Date: Mon, 27 May 2013 10:40:30 +0200	[thread overview]
Message-ID: <51A31BFE.7090908@ti.com> (raw)
In-Reply-To: <1368214859-23558-1-git-send-email-javier.martinez@collabora.co.uk>

Hi Javier,

On 05/10/2013 09:40 PM, Javier Martinez Canillas wrote:
> The IGEP COM Module has an 512MB NAND flash memory.
> 
> Add a device node for this NAND and its parition layout.
> 
> Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
> ---
> 
> Changes since v1:
>  - I just realized that sent a wrong version of the patch, sorry for the noise

And what about the first one? For igep0020?

Thanks,
Benoit

> 
>  arch/arm/boot/dts/omap3-igep0030.dts |   50 ++++++++++++++++++++++++++++++++++
>  1 files changed, 50 insertions(+), 0 deletions(-)
> 
> diff --git a/arch/arm/boot/dts/omap3-igep0030.dts b/arch/arm/boot/dts/omap3-igep0030.dts
> index 9dc48d2..f65bc3a 100644
> --- a/arch/arm/boot/dts/omap3-igep0030.dts
> +++ b/arch/arm/boot/dts/omap3-igep0030.dts
> @@ -42,3 +42,53 @@
>  		};
>  	};
>  };
> +
> +&gpmc {
> +	ranges = <0 0 0x00000000 0x20000000>;
> +
> +	nand@0,0 {
> +		linux,mtd-name= "micron,mt29c4g96maz";
> +		reg = <0 0 0>;
> +		nand-bus-width = <16>;
> +		ti,nand-ecc-opt = "bch8";
> +
> +		gpmc,sync-clk-ps = <0>;
> +		gpmc,cs-on-ns = <0>;
> +		gpmc,cs-rd-off-ns = <44>;
> +		gpmc,cs-wr-off-ns = <44>;
> +		gpmc,adv-on-ns = <6>;
> +		gpmc,adv-rd-off-ns = <34>;
> +		gpmc,adv-wr-off-ns = <44>;
> +		gpmc,we-off-ns = <40>;
> +		gpmc,oe-off-ns = <54>;
> +		gpmc,access-ns = <64>;
> +		gpmc,rd-cycle-ns = <82>;
> +		gpmc,wr-cycle-ns = <82>;
> +		gpmc,wr-access-ns = <40>;
> +		gpmc,wr-data-mux-bus-ns = <0>;
> +
> +		#address-cells = <1>;
> +		#size-cells = <1>;
> +
> +		partition@0 {
> +			label = "SPL";
> +			reg = <0 0x100000>;
> +		};
> +		partition@0x80000 {
> +			label = "U-Boot";
> +			reg = <0x100000 0x180000>;
> +		};
> +		partition@0x1c0000 {
> +			label = "Environment";
> +			reg = <0x280000 0x100000>;
> +		};
> +		partition@0x280000 {
> +			label = "Kernel";
> +			reg = <0x380000 0x300000>;
> +		};
> +		partition@0x780000 {
> +			label = "Filesystem";
> +			reg = <0x680000 0x1f980000>;
> +		};
> +	};
> +};
> 


  reply	other threads:[~2013-05-27  8:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-10 19:40 [PATCH v2 2/2] ARM: dts: omap3-igep0030: Add NAND flash support Javier Martinez Canillas
2013-05-27  8:40 ` Benoit Cousson [this message]
2013-05-27  8:50   ` Javier Martinez Canillas
2013-05-27  8:54     ` Benoit Cousson
2013-05-27  9:08       ` Javier Martinez Canillas

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=51A31BFE.7090908@ti.com \
    --to=b-cousson@ti.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=eballetbo@gmail.com \
    --cc=ezequiel.garcia@free-electrons.com \
    --cc=javier.martinez@collabora.co.uk \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --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).