From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Milton Miller <miltonm@bga.com>
Cc: linuxppc-dev@ozlabs.org, linux-mtd@lists.infradead.org,
arnd@arndb.de, linuxppc-embedded@ozlabs.org
Subject: Re: [RFC] Adding MTD to device tree
Date: Sat, 12 Aug 2006 21:43:51 +0400 [thread overview]
Message-ID: <44DE1357.5010703@ru.mvista.com> (raw)
In-Reply-To: <311553550076b8b45674.846930886.miltonm@bga.com>
Hello.
Milton Miller wrote:
>>>+ h) MTD nodes
>>>+
>>>+ Memory Technology Devices are flash, ROM, and similar chips, often used
>>>+ for solid state file systems on embedded devices.
>>>+
>>>+ Required properties:
>>>+
>>>+ - device_type : has to be "mtd"
>>>+ - compatible : Should be the name of the MTD driver. Currently, this is
>>>+ most likely to be "physmap".
>>>+ - reg : Offset and length of the register set for the device.
>>I would prefer to call them something different in the device tree.
>>The name 'mtd' is very specific to Linux, but the device tree
>>is a more generic concept.
"Memory type devices" are specific to Linux? Doubt it. :-)
In fact, device type "flash" sounds too restrictive.
>>I understand that the booting-without-of.txt file is by definition
>>Linux specific as well, but we should be prepared for making parts
>>of it a OS independent binding at the point where we put the same
>>device nodes into actual OF implementations that able to boot
>>different operating systems.
>>I would prefer a naming that has
>> Required properties:
>> - device_type : one of "nand-flash", "nor-flash", or "rom".
>> - model : an identifier for the actual controller chip used.
>> - compatible : Should be the name of the MTD driver. For
>> type "rom", this is most likely "physmap".
> I'm with your suggestion for device_type and model, but not
> compatable. "physmap"? What kind of device is that? A
Directly mapped NOR flash or ROM I think.
> command set name, maybe with a width, would be
That'd be pretty useless if you don't let Linux know which MTD *map*
driver to use. And I have specified the "bank-width" prop.
> appropriate. Physmap is the name of another linux driver.
And the role of the "compatible" prop is exactly to help OS in selecting
the driver.
> Something like direct or linear might be appropriate for a rom,
> where just address and length appear.
I agree that "linear" or "direct" may be better variants.
> Even rom would be better than physmap.
Doubt it since the ROM is the only one thing (and even the least probable)
that we're going to support.
> milton
WBR, Sergei
next parent reply other threads:[~2006-08-12 17:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <311553550076b8b45674.846930886.miltonm@bga.com>
2006-08-12 17:43 ` Sergei Shtylyov [this message]
2006-08-12 18:48 ` [RFC] Adding MTD to device tree Segher Boessenkool
2006-08-14 12:39 ` David Woodhouse
2006-08-12 21:15 ` Milton Miller
2006-08-12 22:00 ` Sergei Shtylyov
2006-08-13 0:20 ` Wolfgang Denk
2006-08-13 0:20 ` Wolfgang Denk
[not found] <20060614213643.137680b8@vitb.ru.mvista.com>
[not found] ` <44A83AE1.4020707@ru.mvista.com>
[not found] ` <20060705153118.6ffbe97d@localhost.localdomain>
[not found] ` <44ABC0D1.1020407@ru.mvista.com>
[not found] ` <20060705191007.54e8b4b6@localhost.localdomain>
[not found] ` <44B00C03.5010409@ru.mvista.com>
[not found] ` <20060709001435.7a94294e@localhost.localdomain>
2006-08-11 15:31 ` Sergei Shtylyov
2006-08-11 21:10 ` Arnd Bergmann
[not found] ` <1155347601.3108.7.camel@vader.jdub.homelinux.org>
2006-08-12 9:58 ` Segher Boessenkool
2006-08-12 16:19 ` Sergei Shtylyov
2006-08-12 18:44 ` Segher Boessenkool
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=44DE1357.5010703@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=arnd@arndb.de \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=miltonm@bga.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