From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-embedded@ozlabs.org
Cc: Sergei Shtylyov <sshtylyov@ru.mvista.com>,
linuxppc-dev@ozlabs.org, linux-mtd@lists.infradead.org
Subject: Re: [RFC] Adding MTD to device tree
Date: Fri, 11 Aug 2006 23:10:40 +0200 [thread overview]
Message-ID: <200608112310.41110.arnd@arndb.de> (raw)
In-Reply-To: <44DCA2BF.1030002@ru.mvista.com>
On Friday 11 August 2006 17:31, Sergei Shtylyov 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.
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".
Arnd <><
next prev parent reply other threads:[~2006-08-11 21:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 ` [RFC] Adding MTD to device tree Sergei Shtylyov
2006-08-11 21:10 ` Arnd Bergmann [this message]
[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
[not found] <311553550076b8b45674.846930886.miltonm@bga.com>
2006-08-12 17:43 ` Sergei Shtylyov
2006-08-12 18:48 ` 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
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=200608112310.41110.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=sshtylyov@ru.mvista.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