From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Stefan Roese <sr-ynQEQJNshbs@public.gmane.org>
Cc: linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.org,
devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org,
linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 3/3 v3] mtd/powerpc: Describe multiple "reg" tuples usage
Date: Thu, 16 Apr 2009 07:23:10 -0600 [thread overview]
Message-ID: <fa686aa40904160623j1cc734a7qefe3c576f02f2042@mail.gmail.com> (raw)
In-Reply-To: <1239883865-17915-1-git-send-email-sr-ynQEQJNshbs@public.gmane.org>
On Thu, Apr 16, 2009 at 6:11 AM, Stefan Roese <sr-ynQEQJNshbs@public.gmane.org> wrote:
> Signed-off-by: Stefan Roese <sr-ynQEQJNshbs@public.gmane.org>
> CC: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Acked-by: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
I'll pick this one up too.
> ---
> Changes in ver3:
> - Removed reference to Intel P30 parts
> - Added exact chip compatible property for best practice.
>
> Documentation/powerpc/dts-bindings/mtd-physmap.txt | 19 ++++++++++++++++++-
> 1 files changed, 18 insertions(+), 1 deletions(-)
>
> diff --git a/Documentation/powerpc/dts-bindings/mtd-physmap.txt b/Documentation/powerpc/dts-bindings/mtd-physmap.txt
> index cd474f9..667c9bd 100644
> --- a/Documentation/powerpc/dts-bindings/mtd-physmap.txt
> +++ b/Documentation/powerpc/dts-bindings/mtd-physmap.txt
> @@ -5,7 +5,9 @@ file systems on embedded devices.
>
> - compatible : should contain the specific model of flash chip(s)
> used, if known, followed by either "cfi-flash" or "jedec-flash"
> - - reg : Address range of the flash chip
> + - reg : Address range(s) of the flash chip(s)
> + It's possible to (optionally) define multiple "reg" tuples so that
> + non-identical NOR chips can be described in one flash node.
> - bank-width : Width (in bytes) of the flash bank. Equal to the
> device width times the number of interleaved chips.
> - device-width : (optional) Width of a single flash chip. If
> @@ -61,3 +63,18 @@ Example:
> read-only;
> };
> };
> +
> +Here an example with multiple "reg" tuples:
> +
> + flash@f0000000,0 {
> + #address-cells = <1>;
> + #size-cells = <1>;
> + compatible = "intel,PC48F4400P0VB", "cfi-flash";
> + reg = <0 0x00000000 0x02000000
> + 0 0x02000000 0x02000000>;
> + bank-width = <2>;
> + partition@0 {
> + label = "test-part1";
> + reg = <0 0x04000000>;
> + };
> + };
> --
> 1.6.2.3
>
>
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
prev parent reply other threads:[~2009-04-16 13:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 12:11 [PATCH 3/3 v3] mtd/powerpc: Describe multiple "reg" tuples usage Stefan Roese
[not found] ` <1239883865-17915-1-git-send-email-sr-ynQEQJNshbs@public.gmane.org>
2009-04-16 13:23 ` Grant Likely [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=fa686aa40904160623j1cc734a7qefe3c576f02f2042@mail.gmail.com \
--to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
--cc=devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
--cc=linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
--cc=sr-ynQEQJNshbs@public.gmane.org \
/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