linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Laurent Pinchart <laurentp@cse-semaphore.com>
Cc: ben@simtec.co.uk, linuxppc-dev@ozlabs.org,
	linux-mtd@lists.infradead.org,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH 2/2] [POWERPC] Describe memory-mapped RAM&ROM chips of bindings
Date: Wed, 26 Mar 2008 15:52:37 +0100	[thread overview]
Message-ID: <d195a61e876d685ea04b29474da187cc@kernel.crashing.org> (raw)
In-Reply-To: <200803261344.26555.laurentp@cse-semaphore.com>

> +    Dedicated RAM and ROM chips are often used as storage for 
> temporary or
> +    permanent data in embedded devices. Possible usage include 
> non-volatile
> +    storage in battery-backed SRAM, semi-permanent storage in 
> dedicated SRAM
> +    to preserve data accross reboots and firmware storage in 
> dedicated ROM.
> +
> +     - compatible : should contain the specific model of RAM/ROM 
> chip(s)
> +       used, if known, followed by either "physmap-ram" or 
> "physmap-rom"
> +     - reg : Address range of the RAM/ROM chip
> +     - bank-width : Width (in bytes) of the RAM/ROM bank. Equal to the
> +       device width times the number of interleaved chips.
> +     - device-width : (optional) Width of a single RAM/ROM chip. If
> +       omitted, assumed to be equal to 'bank-width'.

Maybe I'm rehashing some old discussion here, if so, sorry; but why
do you have bank-width and device-width here?  What useful information
does it provide?  If this is about saying what the preferred (or only
possible) access width is, better names are in order.


Segher

  reply	other threads:[~2008-03-26 14:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-26 12:44 [PATCH 2/2] [POWERPC] Describe memory-mapped RAM&ROM chips of bindings Laurent Pinchart
2008-03-26 14:52 ` Segher Boessenkool [this message]
2008-03-27  9:37   ` Laurent Pinchart
2008-03-27  9:44     ` David Gibson

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=d195a61e876d685ea04b29474da187cc@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=ben@simtec.co.uk \
    --cc=david@gibson.dropbear.id.au \
    --cc=laurentp@cse-semaphore.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).