From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: kirkwood: Increase NAND chip-delay for DNS-320
Date: Mon, 29 Oct 2012 07:46:32 +0100 [thread overview]
Message-ID: <20121029064632.GJ15143@lunn.ch> (raw)
In-Reply-To: <alpine.DEB.2.00.1210282123250.10589@marmot.wormnet.eu>
> The chip markings are: SAMSUNG 146 K9F1G08U0D SCB0 (FKJ554PWN)
>
> Unfortunately the other NAS is too far away to get at, but D-link
> haven't stuck to exactly the same chip. This DNS-320 review shows a
> different Samsung part:
>
> http://diit.cz/data/images/thumb/67491_2b9e5e4fbd.jpg?1307884464
>
> The datasheet for the K9F1G08U0D says max 35usecs "Data Transfer
> from Cell to Register", whereas K9F1G08U0C (what the DNS-320 review
> shows) says 25usecs. If this is the value in the datasheet to check,
> then this would explain the problems.
Seems sensible.
I'm currently downloading the GPL sources from dlink. If the kernel
sources are included, we can see how dlink sets this. If its also 35,
then there is no argument.
The only thing you could think about is probing the nand device, and
if it is not K9F1G08U0D put the delay back to 25.
Andrew
next prev parent reply other threads:[~2012-10-29 6:46 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 [this message]
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
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=20121029064632.GJ15143@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.