linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurentp@cse-semaphore.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: ben@simtec.co.uk, linuxppc-dev@ozlabs.org, linux-mtd@lists.infradead.org
Subject: Re: OF compatible MTD platform RAM driver ?
Date: Tue, 25 Mar 2008 15:36:12 +0100	[thread overview]
Message-ID: <200803251536.17795.laurentp@cse-semaphore.com> (raw)
In-Reply-To: <20080311224048.GA7642@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 2189 bytes --]

On Tuesday 11 March 2008 23:40, David Gibson wrote:
> On Tue, Mar 11, 2008 at 11:39:08AM +0100, Laurent Pinchart wrote:
> > On Tuesday 11 March 2008 01:45, David Gibson wrote:
> > > On Mon, Mar 10, 2008 at 12:00:22PM -0500, Rune Torgersen wrote:
> > > > linuxppc-dev-bounces+runet=innovsys.com@ozlabs.org wrote:
> [snip]
> > > > We ran ito the same issue.
> > > > We did option 3, as it was efinetly the easiest,
> > >
> > > I think this is the best option in principle.
> > 
> > I'll implement that and post a patch after completing the ppc-to-powerpc 
> > migration.
> > 
> > > > here is the sram entry in our dts:
> > >
> > > Except that your implementation of it is not good.
> > >
> > > You're relying on the old obsolete flash binding with the "probe-type"
> > > field.  The solution should be adapted to the new approach which uses
> > > values in the "compatible" field to indicate various sorts of flash
> > > device.
> > 
> > What "compatible" values should I use for ROM and RAM mappings ?
> 
> That I'm not so sure of.  We'll need to find some consensus.
> 
> There may be existing IEEE1275 bindings for roms, which we should
> investigate.

Do you (or someone else here) have access to the IEEE1275 specification ? Is 
there any ROM binding in there ?

> Arguably RAM should be represented by a memory node, but 
> that's going to get messy for this sort of application.

We're talking about a very specific type of RAM, used for permanent storage 
with a battery backup. The RAM is really meant to be used as an MTD device 
and as such I think it makes sense to describe it as an mtd-compatible device 
on the local bus.

What about the following definition for the RAM node ?

        nvram@2,0000 {
                compatible = "mtd,ram";
                reg = <2 0x0000 0x00100000>;
                bank-width = <2>;
        };

Or should the node have a device-type property of either 'ram' or 'rom' with 
the compatible property just referencing MTD ?

Best regards,

-- 
Laurent Pinchart
CSE Semaphore Belgium

Chaussée de Bruxelles, 732A
B-1410 Waterloo
Belgium

T +32 (2) 387 42 59
F +32 (2) 387 42 75

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-03-25 14:36 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-10 15:06 OF compatible MTD platform RAM driver ? Laurent Pinchart
2008-03-10 17:00 ` Rune Torgersen
2008-03-11  0:45   ` David Gibson
2008-03-11 10:39     ` Laurent Pinchart
2008-03-11 22:40       ` David Gibson
2008-03-25 14:36         ` Laurent Pinchart [this message]
2008-03-25 15:29           ` Sergei Shtylyov
2008-03-25 15:51             ` Laurent Pinchart
2008-03-25 16:23               ` Sergei Shtylyov
2008-03-25 16:44                 ` Laurent Pinchart
2008-03-25 17:02                   ` Sergei Shtylyov
2008-03-25 17:23                     ` Laurent Pinchart
2008-03-25 17:37                       ` Sergei Shtylyov
2008-03-25 17:56                       ` Rune Torgersen
2008-03-25 18:14                         ` Laurent Pinchart
2008-03-26 12:53                           ` Sergei Shtylyov
2008-03-27  9:13                             ` Laurent Pinchart
2008-03-27 10:03                               ` David Gibson
2008-03-27 12:23                                 ` Sergei Shtylyov
2008-03-28  0:07                                   ` David Gibson
2008-03-28 12:31                                     ` Sergei Shtylyov
2008-03-27 14:31                                 ` Laurent Pinchart
2008-03-28  0:09                                   ` David Gibson
2008-03-30 18:15                                 ` Segher Boessenkool
2008-03-30 21:16                                   ` Paul Mackerras
2008-03-30 22:39                                     ` Segher Boessenkool
2008-03-31  0:42                                       ` Paul Mackerras
2008-03-31  0:59                                         ` Segher Boessenkool
2008-03-31  1:24                                           ` Segher Boessenkool
2008-03-31  8:21                                       ` Laurent Pinchart
2008-03-31 12:21                                         ` Segher Boessenkool
2008-03-26 15:06                           ` Segher Boessenkool
2008-03-26 15:40                             ` Sergei Shtylyov
2008-03-27  9:24                               ` Laurent Pinchart
2008-03-30 18:12                               ` Segher Boessenkool
2008-03-26 15:09                   ` Segher Boessenkool
2008-03-11 15:00     ` Rune Torgersen
2008-03-11 22:41       ` 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=200803251536.17795.laurentp@cse-semaphore.com \
    --to=laurentp@cse-semaphore.com \
    --cc=ben@simtec.co.uk \
    --cc=david@gibson.dropbear.id.au \
    --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).