From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: Vitaly Wool <vwool@ru.mvista.com>, linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] adding ROM chips to device tree
Date: Thu, 02 Nov 2006 22:09:26 +0300 [thread overview]
Message-ID: <454A4266.8040505@ru.mvista.com> (raw)
In-Reply-To: <1162474237.11351.7.camel@zod.rchland.ibm.com>
Hello.
Josh Boyer wrote:
>>+
>>+ Required properties:
>>+
>>+ - device_type : has to be "rom"
> Why "rom" instead of "NOR"?
What does "NOR" mean -- logical operator? :-)
I'd yet agree with "nor-flash", however, the physmap-driven device may not
always be writeable, IIUC...
>>+ - 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.
> reg doesn't really describe a register set here. It's the overall
> memory space for flash.
This is no more a standard boilerplate, if you look at this file.
Also remember that we're not describing "physmap" compatible devices only.
>>+
>>+ Recommended properties :
>>+
>>+ - bank-width : Width of the flash data bus in bytes. Must be specified
>>+ for the NOR flashes.
> This is a required property, not a recommended one.
Required by *certain* driver. Others may not need it (know beforehand).
> josh
WBR, Sergei
next prev parent reply other threads:[~2006-11-02 19:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-02 11:55 [PATCH] adding ROM chips to device tree Vitaly Wool
2006-11-02 13:30 ` Josh Boyer
2006-11-02 13:45 ` Vitaly Wool
2006-11-02 19:09 ` Sergei Shtylyov [this message]
2006-11-02 20:23 ` Vitaly Wool
2006-11-07 18:29 ` Sergei Shtylyov
2006-11-02 15:31 ` Grant Likely
2006-11-02 15:53 ` Vitaly Wool
2006-11-02 19:01 ` Sergei Shtylyov
2006-11-02 20:30 ` Vitaly Wool
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=454A4266.8040505@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=vwool@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 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.