From: Laurent Pinchart <laurentp@cse-semaphore.com>
To: "Grant Likely" <grant.likely@secretlab.ca>
Cc: ben@simtec.co.uk, linuxppc-dev@ozlabs.org,
linux-mtd@lists.infradead.org,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCHv2] powerpc: Describe memory-mapped RAM&ROM chips OF bindings
Date: Thu, 3 Apr 2008 12:15:29 +0200 [thread overview]
Message-ID: <200804031215.30314.laurentp@cse-semaphore.com> (raw)
In-Reply-To: <fa686aa40804010616v4d6a2c8at5d3be8c32f316494@mail.gmail.com>
On Tuesday 01 April 2008 15:16, Grant Likely wrote:
> On Mon, Mar 31, 2008 at 10:39 AM, Laurent Pinchart
> <laurentp@cse-semaphore.com> wrote:
> >
> > Signed-off-by: Laurent Pinchart <laurentp@cse-semaphore.com>
> > ---
> > Documentation/powerpc/booting-without-of.txt | 13 ++++++++++++-
> > 1 files changed, 12 insertions(+), 1 deletions(-)
> >
> > diff --git a/Documentation/powerpc/booting-without-of.txt=20
> > b/Documentation/powerpc/booting-without-of.txt=20
> > index 7b4e8a7..3e1963b 100644
> > --- a/Documentation/powerpc/booting-without-of.txt
> > +++ b/Documentation/powerpc/booting-without-of.txt
> > @@ -57,7 +57,8 @@ Table of Contents
> > n) 4xx/Axon EMAC ethernet nodes
> > o) Xilinx IP cores
> > p) Freescale Synchronous Serial Interface
> > - q) USB EHCI controllers
> > + q) USB EHCI controllers
> > + r) Memory-mapped RAM & ROM
> >
> > VII - Specifying interrupt information for devices
> > 1) interrupts property
> > @@ -2816,6 +2817,16 @@ platforms are moved over to use the
> > flattened-device-tree model.=20
> > big-endian;
> > };
> >
> > + r) Memory-mapped RAM & ROM
> > +
> > + Dedicated RAM and ROM chips are often used as storage for tempora=
ry
> > or=20
> > + permanent data in embedded devices. Possible usage include
> > non-volatile=20
> > + storage in battery-backed SRAM, semi-permanent storage in dedicat=
ed
> > SRAM=20
> > + to preserve data accross reboots and firmware storage in dedicated
> > ROM.=20
> > +
> > + - name : should be either "ram" or "rom"
> > + - reg : Address range of the RAM/ROM chip
> > +
>=20
> No compatible prop? How does the OS know what the node is to be used for?
If I understood Sergei's arguments properly, the device tree should describ=
e=20
device properties and not their intended usage. With generic devices such a=
s=20
RAM chips, platform code is responsible for binding the device to the=20
appropriate driver (mtd-ram for instance).
Cheers,
=2D-=20
Laurent Pinchart
CSE Semaphore Belgium
Chauss=E9e de Bruxelles, 732A
B-1410 Waterloo
Belgium
T +32 (2) 387 42 59
=46 +32 (2) 387 42 75
prev parent reply other threads:[~2008-04-03 10:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 16:39 [PATCHv2] powerpc: Describe memory-mapped RAM&ROM chips OF bindings Laurent Pinchart
2008-03-31 17:06 ` Sergei Shtylyov
2008-04-01 8:47 ` Laurent Pinchart
2008-04-01 9:18 ` Trent Piepho
2008-04-01 12:39 ` Laurent Pinchart
2008-04-01 13:04 ` Sergei Shtylyov
2008-04-01 13:16 ` Grant Likely
2008-04-03 10:15 ` Laurent Pinchart [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=200804031215.30314.laurentp@cse-semaphore.com \
--to=laurentp@cse-semaphore.com \
--cc=ben@simtec.co.uk \
--cc=david@gibson.dropbear.id.au \
--cc=grant.likely@secretlab.ca \
--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).