From: antoine.tenart@free-electrons.com (Antoine Tenart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 07/12] mtd: nand: add Samsung K9GBG08U0A-M to nand_ids table
Date: Wed, 20 May 2015 16:06:31 +0200 [thread overview]
Message-ID: <20150520140631.GN22054@kwain> (raw)
In-Reply-To: <555792FC.8030407@vanguardiasur.com.ar>
On Sat, May 16, 2015 at 03:57:00PM -0300, Ezequiel Garcia wrote:
> On 05/11/2015 11:58 AM, Antoine Tenart wrote:
> > Add the full description of the Samsung K9GBG08U0A-M nand chip in the
> > nand_ids table.
> >
> > Signed-off-by: Antoine Tenart <antoine.tenart@free-electrons.com>
> > ---
> > drivers/mtd/nand/nand_ids.c | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/drivers/mtd/nand/nand_ids.c b/drivers/mtd/nand/nand_ids.c
> > index dd620c19c619..500c33e1db06 100644
> > --- a/drivers/mtd/nand/nand_ids.c
> > +++ b/drivers/mtd/nand/nand_ids.c
> > @@ -50,6 +50,10 @@ struct nand_flash_dev nand_flash_ids[] = {
> > { .id = {0xad, 0xde, 0x94, 0xda, 0x74, 0xc4} },
> > SZ_8K, SZ_8K, SZ_2M, 0, 6, 640, NAND_ECC_INFO(40, SZ_1K),
> > 4 },
> > + {"NAND 4GiB 3,3V 8-bit",
> > + { .id = {0xec, 0xd7, 0x94, 0x76, 0x64, 0x43}, },
> > + 8192, 4096, SZ_1M, LP_OPTIONS, 0, 0, NAND_ECC_INFO(40, SZ_1K),
>
> You should stick to SZ_8K and SZ_4K here.
Right.
>
> > + 4 },
> >
> > LEGACY_ID_NAND("NAND 4MiB 5V 8-bit", 0x6B, 4, SZ_8K, SP_OPTIONS),
> > LEGACY_ID_NAND("NAND 4MiB 3,3V 8-bit", 0xE3, 4, SZ_8K, SP_OPTIONS),
> >
>
> I found a datasheet here for K9GBG08U0A that claims to support JEDEC
> device identification (i.e. 0x90 0x40 and 0xEC 0x40 commands). Have you
> tested it? Any reason you are adding full ID instead?
This nand looks like another one defined in this file, so a full ID make
sure the right parameters applies here.
Antoine
--
Antoine T?nart, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-05-20 14:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 14:58 [PATCH v5 00/12] ARM: berlin: add nand support Antoine Tenart
2015-05-11 14:58 ` [PATCH v5 01/12] mtd: pxa3xx_nand: add a non mandatory ECC clock Antoine Tenart
2015-05-11 14:58 ` [PATCH v5 02/12] Documentation: bindings: document the clocks for pxa3xx-nand Antoine Tenart
2015-05-11 14:58 ` [PATCH v5 03/12] mtd: pxa3xx_nand: add a default chunk size Antoine Tenart
2015-05-11 14:58 ` [PATCH v5 04/12] mtd: pxa3xx_nand: add helpers to setup the timings Antoine Tenart
2015-05-11 14:58 ` [PATCH v5 05/12] mtd: pxa3xx_nand: rework flash detection and timing setup Antoine Tenart
2015-05-11 22:10 ` Ezequiel Garcia
2015-05-12 14:39 ` Antoine Tenart
2015-05-16 21:23 ` Ezequiel Garcia
2015-05-20 13:55 ` Antoine Tenart
2015-05-20 13:56 ` Ezequiel Garcia
2015-05-20 14:04 ` Antoine Tenart
2015-05-16 22:02 ` Ezequiel Garcia
2015-05-20 14:03 ` Antoine Tenart
2015-05-20 14:05 ` Ezequiel Garcia
2015-05-11 14:58 ` [PATCH v5 06/12] mtd: pxa3xx_nand: clean up the pxa3xx timings Antoine Tenart
2015-05-11 14:58 ` [PATCH v5 07/12] mtd: nand: add Samsung K9GBG08U0A-M to nand_ids table Antoine Tenart
2015-05-16 18:57 ` Ezequiel Garcia
2015-05-20 14:06 ` Antoine Tenart [this message]
2015-05-20 14:09 ` Ezequiel Garcia
2015-05-20 14:24 ` Antoine Tenart
2015-05-20 14:43 ` Antoine Tenart
2015-05-24 18:42 ` Ezequiel Garcia
2015-07-20 18:08 ` Brian Norris
2015-07-20 18:22 ` Ezequiel Garcia
2015-05-11 14:58 ` [PATCH v5 08/12] mtd: pxa3xx_nand: add support for the Marvell Berlin nand controller Antoine Tenart
2015-05-11 14:58 ` [PATCH v5 09/12] Documentation: bindings: add the Berlin nand controller compatible Antoine Tenart
2015-05-11 14:58 ` [PATCH v5 10/12] mtd: nand: let Marvell Berlin SoCs select the pxa3xx driver Antoine Tenart
2015-05-11 14:59 ` [PATCH v5 11/12] ARM: berlin: add BG2Q node for the nand Antoine Tenart
2015-05-11 14:59 ` [PATCH v5 12/12] ARM: berlin: enable flash on the BG2Q DMP Antoine Tenart
2015-05-16 21:37 ` [PATCH v5 00/12] ARM: berlin: add nand support Ezequiel Garcia
2015-05-20 14:08 ` Antoine Tenart
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=20150520140631.GN22054@kwain \
--to=antoine.tenart@free-electrons.com \
--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).