From: Sergei Shtylyov <sshtylyov@ru•mvista.com>
To: Vitaly Wool <vitalywool@gmail•com>
Cc: linuxppc-dev@ozlabs•org, dwmw2@redhat•com,
Paul Mackerras <paulus@samba•org>
Subject: Re: [PATCH][trivial][respin] update MTD OF documentation
Date: Wed, 20 Dec 2006 00:20:47 +0300 [thread overview]
Message-ID: <458857AF.6000406@ru.mvista.com> (raw)
In-Reply-To: <20061219184425.d924c4c2.vitalywool@gmail.com>
Hello.
Vitaly Wool wrote:
> the patch below updates the Documentation/powerpc part of the MTD OF implementation with the new field probe-type. Its support has already been implemented in MTD part (drivers/mtd/maps/physmap_of.c).
> Documentation/powerpc/booting-without-of.txt | 19 +++++++++++--------
> 1 files changed, 11 insertions(+), 8 deletions(-)
>
> Signed-off-by: Vitaly Wool <vwool@ru•mvista.com>
Signed-off-by: Sergei Shtylyov <sshtylyov@ru•mvista.com>
> diff --git a/Documentation/powerpc/booting-without-of.txt b/Documentation/powerpc/booting-without-of.txt
> index b3bd366..3399427 100644
> --- a/Documentation/powerpc/booting-without-of.txt
> +++ b/Documentation/powerpc/booting-without-of.txt
> @@ -1703,29 +1703,32 @@ platforms are moved over to use the flat
> Required properties:
>
> - device_type : has to be "rom"
> - - compatible : Should specify what this ROM device is compatible with
> - (i.e. "onenand"). Currently, this is most likely to be "direct-mapped"
> - (which corresponds to the MTD physmap mapping driver).
> - - regs : Offset and length of the register set (or memory mapping) for
> + - compatible : Should specify what this flash device is compatible with.
> + Currently, this is most likely to be "direct-mapped" (which
> + corresponds to the MTD physmap mapping driver).
> + - reg : Offset and length of the register set (or memory mapping) for
> the device.
> + - bank-width : Width of the flash data bus in bytes. Required
> + for the NOR flashes (compatible == "direct-mapped" and others) ONLY.
>
> Recommended properties :
>
> - - bank-width : Width of the flash data bus in bytes. Required
> - for the NOR flashes (compatible == "direct-mapped" and others) ONLY.
> - partitions : Several pairs of 32-bit values where the first value is
> partition's offset from the start of the device and the second one is
> partition size in bytes with LSB used to signify a read only
> - partititon (so, the parition size should always be an even number).
> + partition (so, the parition size should always be an even number).
> - partition-names : The list of concatenated zero terminated strings
> representing the partition names.
> + - probe-type : The type of probe which should be done for the chip
> + (JEDEC vs CFI actually). Valid ONLY for NOR flashes.
>
> Example:
>
> flash@ff000000 {
> device_type = "rom";
> compatible = "direct-mapped";
> - regs = <ff000000 01000000>;
> + probe-type = "CFI";
> + reg = <ff000000 01000000>;
> bank-width = <4>;
> partitions = <00000000 00f80000
> 00f80000 00080001>;
WBR, Sergei
prev parent reply other threads:[~2006-12-19 21:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 15:44 [PATCH][trivial][respin] update MTD OF documentation Vitaly Wool
2006-12-19 21:20 ` Sergei Shtylyov [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=458857AF.6000406@ru.mvista.com \
--to=sshtylyov@ru$(echo .)mvista.com \
--cc=dwmw2@redhat$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=paulus@samba$(echo .)org \
--cc=vitalywool@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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