From: Artem Bityutskiy <dedekind1@gmail.com>
To: Florian Fainelli <ffainelli@freebox.fr>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [RFC] MTD: export more NAND-related informations to syfs
Date: Thu, 12 May 2011 13:01:03 +0300 [thread overview]
Message-ID: <1305194463.2713.79.camel@localhost> (raw)
In-Reply-To: <201105091621.38720.ffainelli@freebox.fr>
On Mon, 2011-05-09 at 16:21 +0200, Florian Fainelli wrote:
> Hello Artem,
>
> On Friday 06 May 2011 20:39:33 Artem Bityutskiy wrote:
> > On Fri, 2011-05-06 at 17:28 +0200, Florian Fainelli wrote:
> > > + /* NAND related attributes */
> > > + const char *nand_type;
> > > + const char *nand_manufacturer;
> >
> > Why other flashes cannot have type and manufacturer ?
>
> You are right, I will add this for NOR and SPI Flashes. My RFC was more about
> whether it is granted to add new members to struct mtd_info to get
> informations
struct mtd_info describes an mtd device. Things, which are common for
all mtd devices should be there, I think.
> Alternatively, would not it be better to have something like this:
>
> /sys/class/mtd/...
> nand0/
> manufacturer
> type
> onfi/
> version
> jedec_id
> ...
> nor0/
> cfi/
> manufacturer
> id
>
> This would allow us not to abuse the sysfs directory of a MTD partition to
> contain chip specific informations.
Why do you call it "abuse" and why is it better to "abuse" the directory
common to all MTD devices comparing to the directory of the specific MTD
device? :-)
I think that everything related to mtdX has to be in the mtdX
subdirectory.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2011-05-12 10:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 15:28 [RFC] MTD: export more NAND-related informations to syfs Florian Fainelli
2011-05-06 18:39 ` Artem Bityutskiy
2011-05-09 14:21 ` Florian Fainelli
2011-05-12 10:01 ` Artem Bityutskiy [this message]
2011-05-12 10:38 ` Ricard Wanderlof
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=1305194463.2713.79.camel@localhost \
--to=dedekind1@gmail.com \
--cc=ffainelli@freebox.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox