From: David Gibson <david@gibson.dropbear.id.au>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Document and implement an improved flash device binding for powerpc (v4)
Date: Fri, 31 Aug 2007 12:58:17 +1000 [thread overview]
Message-ID: <20070831025817.GF19271@localhost.localdomain> (raw)
In-Reply-To: <20070830172932.GA3317@ld0162-tx32.am.freescale.net>
On Thu, Aug 30, 2007 at 12:29:33PM -0500, Scott Wood wrote:
> On Thu, Aug 30, 2007 at 11:21:18AM +1000, David Gibson wrote:
> > + For JEDEC compatible devices, the following additional properties
> > + are defined:
> > +
> > + - vendor-id : Contains the flash chip's vendor id (1 byte).
> > + - device-id : Contains the flash chip's device id (1 byte).
>
> Are these required, or recommended?
Heh.. that's an interesting question. I think they're a "SHOULD" in
rfc terminology. According to Segher, this information should be
provided for any JEDEC chip. However, it can, in practice, be probed
by the mtd code, and in fact there's no obvious way of actually
specifying these to the mtd code, so these properties aren't ever
actually used (at present, anyway).
> > + In addition to the information on the flash bank itself, the
> > + device tree may optionally contain additional information
> > + describing partitions of the flash address space. This can be
> > + used on platforms which have strong conventions about which
> > + portions of the flash are used for what purposes, but which don't
> > + use an on-flash partition table such as RedBoot.
> > +
> > + Each partition is represented as a sub-node of the flash device.
> > + Each node's name represents the name of the corresponding
> > + partition of the flash device.
>
> Hmm... I'm not thrilled with using the node name for this. For one, the
> node name usually functions more as a node type than a label. It also
> means that spaces can't be used in the name, which is fairly common for
> existing partition maps.
>
> This might be a good time to introduce a standard "label" property.
Hrm, yeah, that's not a bad idea. I'm thinking 'label' is used if
present, otherwise it falls back to the node name.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
prev parent reply other threads:[~2007-08-31 2:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 1:21 Document and implement an improved flash device binding for powerpc (v4) David Gibson
2007-08-30 17:29 ` Scott Wood
2007-08-30 17:59 ` Josh Boyer
2007-08-30 18:04 ` Scott Wood
2007-08-30 18:23 ` Josh Boyer
2007-08-31 2:58 ` David Gibson [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=20070831025817.GF19271@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.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).