public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dinh Nguyen <dinguyen@opensource.altera.com>
To: Pavel Machek <pavel@denx.de>, <wsa@the-dreams.de>,
	kernel list <linux-kernel@vger.kernel.org>, <jg1.han@samsung.com>,
	<artem.bityutskiy@linux.intel.com>, <sachin.kamat@linaro.org>,
	<David.Woodhouse@intel.com>, <dinguyen@altera.com>, <sr@denx.de>
Cc: <marex@denx.de>, Graham Moore <grmoore@opensource.altera.com>
Subject: Re: Denali NAND driver on SocKit
Date: Mon, 30 Nov 2015 13:35:42 -0600	[thread overview]
Message-ID: <565CA50E.7040106@opensource.altera.com> (raw)
In-Reply-To: <20151130183155.GA26351@amd>

CC: Graham Moore

Graham should know more about this.

Dinh

On 11/30/2015 12:31 PM, Pavel Machek wrote:
> Hi!
> 
> I'm trying to get NAND to work on socdk board... but it looks like
> neccessary device tree bindings are not there. And when I do add them,
> they don't seem to work.
> 
> Does it work for you? Is there patch I should apply?
> 
> Thanks,
> 								Pavel
> 
> 
> diff --git a/arch/arm/boot/dts/socfpga.dtsi b/arch/arm/boot/dts/socfpga.dtsi
> index bd2937f..ec61b29 100644
> --- a/arch/arm/boot/dts/socfpga.dtsi
> +++ b/arch/arm/boot/dts/socfpga.dtsi
> @@ -582,6 +582,46 @@
>  			status = "disabled";
>  		};
>  
> +		nand: nand@ff900000 {
> +			#address-cells = <1>;
> +			#size-cells = <1>;
> +			compatible = "denali,denali-nand-dt";
> +			reg = <0xff900000 0x100000>, <0xffb80000 0x10000>;
> +			reg-names = "nand_data", "denali_reg";
> +			interrupts = <0 144 4>;
> +			dma-mask = <0xffffffff>;
> +			clocks = <&nand_clk>;
> +			have-hw-ecc-fixup;
> +			status = "disabled";
> +
> +			partition@nand-boot {
> +				/* 8MB for raw data. */
> +				label = "NAND Flash Boot Area 8MB";
> +				reg = <0x0 0x800000>;
> +			};
> +			partition@nand-rootfs {
> +				/* 128MB jffs2 root filesystem. */
> +				label = "NAND Flash jffs2 Root Filesystem 128MB";
> +				reg = <0x800000 0x8000000>;
> +			};
> +			partition@nand-128 {
> +				label = "NAND Flash 128 MB";
> +				reg = <0x8800000 0x8000000>;
> +			};
> +			partition@nand-64 {
> +				label = "NAND Flash 64 MB";
> +				reg = <0x10800000 0x4000000>;
> +			};
> +			partition@nand-32 {
> +				label = "NAND Flash 32 MB";
> +				reg = <0x14800000 0x2000000>;
> +			};
> +			partition@nand-16 {
> +				label = "NAND Flash 16 MB";
> +				reg = <0x16800000 0x1000000>;
> +			};
> +		};
> +
>  		gpio0: gpio@ff708000 {
>  			#address-cells = <1>;
>  			#size-cells = <0>;
> diff --git a/arch/arm/boot/dts/socfpga_cyclone5_socdk.dts b/arch/arm/boot/dts/socfpga_cyclone5_socdk.dts
> index d4d0a28..b56c8f9 100644
> --- a/arch/arm/boot/dts/socfpga_cyclone5_socdk.dts
> +++ b/arch/arm/boot/dts/socfpga_cyclone5_socdk.dts
> @@ -89,3 +89,7 @@
>  &usb1 {
>  	status = "okay";
>  };
> +
> +&nand {
> +        status = "okay";
> +};
> 


  reply	other threads:[~2015-11-30 19:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-30 18:31 Denali NAND driver on SocKit Pavel Machek
2015-11-30 19:35 ` Dinh Nguyen [this message]
2015-12-04 16:55   ` Pavel Machek

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=565CA50E.7040106@opensource.altera.com \
    --to=dinguyen@opensource.altera.com \
    --cc=David.Woodhouse@intel.com \
    --cc=artem.bityutskiy@linux.intel.com \
    --cc=dinguyen@altera.com \
    --cc=grmoore@opensource.altera.com \
    --cc=jg1.han@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marex@denx.de \
    --cc=pavel@denx.de \
    --cc=sachin.kamat@linaro.org \
    --cc=sr@denx.de \
    --cc=wsa@the-dreams.de \
    /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