linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollis@penguinppc.org>
To: Vitaly Wool <vwool@ru.mvista.com>
Cc: linuxppc-dev@ozlabs.org, linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] powerpc: Add of_platform support for ROM devices
Date: Mon, 20 Nov 2006 09:48:24 -0600	[thread overview]
Message-ID: <1164037704.10815.11.camel@diesel> (raw)
In-Reply-To: <20061120163239.f9a38fc1.vwool@ru.mvista.com>

On Mon, 2006-11-20 at 16:32 +0300, Vitaly Wool wrote:
> +
> +    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
> +       the device.
> +
> +    Recommended properties :
> +
> +     - bank-width : Width of the flash data bus in bytes. Required
> +       for the NOR flashes (compatible == "direct-mapped" and others) ONLY.

Maybe you should put this in the Required section then, with a note that
it's only Recommended for non-NOR flashes. I can easily imagine somebody
ignoring every Recommendation section and missing this requirement.

> +     - 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" misspelled, twice. :)

-Hollis

  reply	other threads:[~2006-11-20 15:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-20 13:32 [PATCH] powerpc: Add of_platform support for ROM devices Vitaly Wool
2006-11-20 15:48 ` Hollis Blanchard [this message]
2006-11-21 17:22 ` David Woodhouse

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=1164037704.10815.11.camel@diesel \
    --to=hollis@penguinppc.org \
    --cc=linuxppc-dev@ozlabs.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).