From: Florian Fainelli <ffainelli@freebox.fr>
To: linux-mtd@lists.infradead.org
Cc: Tom Isaacson <Tom.Isaacson@navico.com>
Subject: Re: Exposing NAND chip information
Date: Mon, 16 Apr 2012 08:59:48 +0200 [thread overview]
Message-ID: <8396132.PHseJUhzUe@bender> (raw)
In-Reply-To: <B36E81988B048A4FA3600EDE585F756BD0EBD2@EXCH02-AKLNZ.MARINE.NET.INT>
Hi,
On Sunday 15 April 2012 23:20:25 Tom Isaacson wrote:
> Hi,
>
> Our production software needs to record the NAND chip type used in
> production so we have a record in case we get problems later. The
> information we need is printed out by nand_get_flash_type(), e.g.: NAND
> device: Manufacturer ID: 0x98, Chip ID: 0xd1 (Toshiba NAND 128MiB 3,3V
> 8-bit) My plan is to add some files to the /sys tree to expose this
> information. But the only part of that information stored is the device
> name, in mtd_info.name. Is there any reason why I shouldn't add the
> manufacturer name and ID and the chip ID to mtd_info so they can be
> accessed later on? Or should I add them to mxd_mtd_s (in nand_base.c) and
> keep it local?
>
> Also, when I add the files to the /sys tree is there any naming convention I
> should follow? I was going to copy the way the eMMC device does it: manfid
> - Manufacturer ID
> devid - Chip ID
> manf_name - Manufacturer name
> dev_name - Chip name
I have the exact same requirement and cooked up a patch to do this for NAND:
http://patchwork.ozlabs.org/patch/94407/
however, to be complete it would also need to expose such informations for SPI
and NOR flashes, which I have not done yet.
--
Florian
next prev parent reply other threads:[~2012-04-16 6:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-15 23:20 Exposing NAND chip information Tom Isaacson
2012-04-16 6:59 ` Florian Fainelli [this message]
2012-04-16 23:51 ` Tom Isaacson
2012-04-17 9:39 ` Florian Fainelli
2012-04-22 14:44 ` Artem Bityutskiy
2012-04-22 23:40 ` Tom Isaacson
2012-04-27 14:12 ` Artem Bityutskiy
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=8396132.PHseJUhzUe@bender \
--to=ffainelli@freebox.fr \
--cc=Tom.Isaacson@navico.com \
--cc=linux-mtd@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.