From: Matthieu CASTET <matthieu.castet@parrot.com>
To: Florian Fainelli <florian@openwrt.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
Artem Bityutskiy <dedekind1@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Brian Norris <norris@broadcom.com>,
Maxime Bizon <mbizon@freebox.fr>
Subject: Re: [PATCH 3/3 v3] NAND: add support for reading ONFI parameters from NAND device
Date: Thu, 21 Oct 2010 18:52:18 +0200 [thread overview]
Message-ID: <4CC06FC2.2060406@parrot.com> (raw)
In-Reply-To: <201008301832.24672.florian@openwrt.org>
Hi,
Florian Fainelli a écrit :
> This patch adds support for reading NAND device ONFI parameters and use
> the ONFI informations to define its geometry. In case the device supports
> ONFI, the onfi_version field in struct nand_chip contains the version (BCD)
> and the onfi_params structure can be used by drivers to set up timings and
> such. We currently only support ONFI 1.0 parameters.
>
> Signed-off-by: Brian Norris <norris@broadcom.com>
> Signed-off-by: Matthieu Castet <matthieu.castet@parrot.com>
> Signed-off-by: Maxime Bizon <mbizon@freebox.fr>
> Signed-off-by: Florian Fainelli <ffainelli@freebox.fr>
> ---
chip->cmdfunc = nand_command_lp;
>
> + /* TODO onfi flash name */
> printk(KERN_INFO "NAND device: Manufacturer ID:"
> - " 0x%02x, Chip ID: 0x%02x (%s %s)\n", *maf_id, dev_id,
> - nand_manuf_ids[maf_idx].name, type->name);
> + " 0x%02x, Chip ID: 0x%02x (%s %s)\n", *maf_id, *dev_id,
> + nand_manuf_ids[maf_idx].name,
> + chip->onfi_version ? type->name:chip->onfi_params.model);
>
I don't know if it has been noticed but it should be
chip->onfi_version ? chip->onfi_params.model : type->name
Matthieu
prev parent reply other threads:[~2010-10-21 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 16:32 [PATCH 3/3 v3] NAND: add support for reading ONFI parameters from NAND device Florian Fainelli
2010-08-31 11:46 ` Artem Bityutskiy
2010-08-31 12:02 ` Florian Fainelli
2010-10-21 16:52 ` Matthieu CASTET [this message]
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=4CC06FC2.2060406@parrot.com \
--to=matthieu.castet@parrot.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=florian@openwrt.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mbizon@freebox.fr \
--cc=norris@broadcom.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).