linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2] ARM: kirkwood: Increase NAND chip-delay for DNS-32[05]
Date: Fri, 2 Nov 2012 06:45:52 +0100	[thread overview]
Message-ID: <20121102054552.GC27438@lunn.ch> (raw)
In-Reply-To: <1351807021-17478-1-git-send-email-jm@lentin.co.uk>

On Thu, Nov 01, 2012 at 09:57:01PM +0000, Jamie Lentin wrote:
> The default chip-delay of 25us is a bit too tight for some DNS-320's,
> and D-Link seem to specify 30us in their kernels for both devices.
> Increase to 35us to make sure the NAND is stable.
> 
> Signed-off-by: Jamie Lentin <jm@lentin.co.uk>
> ---
>  arch/arm/boot/dts/kirkwood-dnskw.dtsi |    1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/arch/arm/boot/dts/kirkwood-dnskw.dtsi b/arch/arm/boot/dts/kirkwood-dnskw.dtsi
> index e0e4397..0360361 100644
> --- a/arch/arm/boot/dts/kirkwood-dnskw.dtsi
> +++ b/arch/arm/boot/dts/kirkwood-dnskw.dtsi
> @@ -48,6 +48,7 @@
>  
>  		nand at 3000000 {
>  			status = "okay";
> +			chip-delay = <35>;
>  
>  			partition at 0 {
>  				label = "u-boot";
> -- 
> 1.7.10.4
> 

Acked-by: Andrew Lunn <andrew@lunn.ch>

	  Andrew

  reply	other threads:[~2012-11-02  5:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-28 20:47 [PATCH] ARM: kirkwood: Increase NAND chip-delay for DNS-320 Jamie Lentin
2012-10-28 20:59 ` Andrew Lunn
2012-10-28 21:53   ` Jamie Lentin
2012-10-29  6:46     ` Andrew Lunn
2012-10-29 22:47       ` Jamie Lentin
2012-10-30  6:02         ` Andrew Lunn
2012-11-01 21:57           ` [PATCH V2] ARM: kirkwood: Increase NAND chip-delay for DNS-32[05] Jamie Lentin
2012-11-02  5:45             ` Andrew Lunn [this message]
2012-11-01 22:09           ` [PATCH] ARM: kirkwood: Increase NAND chip-delay for DNS-320 Jamie Lentin

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=20121102054552.GC27438@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).