linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Mercier Ivan <ivan.mercier@gmail.com>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Elbc device driver
Date: Tue, 22 Oct 2013 11:43:31 +0200	[thread overview]
Message-ID: <CAMc2ierLhKeLX2ijUBaVU=suF3OF4DPku2N+WBTE1HvMPc3yaQ@mail.gmail.com> (raw)
In-Reply-To: <1381512940.7979.497.camel@snotra.buserror.net>

Ok Scott,
now it works!
We had severals hardware problem.
Thanks for your help

2013/10/11 Scott Wood <scottwood@freescale.com>:
> On Fri, 2013-10-11 at 17:03 +0200, Mercier Ivan wrote:
>> Hi,
>> this should be correct (I'm using chip select 3 for this device)
>>         lbc: localbus@ffe124000 {
>>                 reg = <0xf 0xfe124000 0 0x1000>;
>>                 ranges = <3 0 0xf 0xe0000000 0x08000000>;
>>
>>                 a3p400{
>>                         #address-cells = <1>;
>>                         #size-cells = <1>;
>>                         compatible = "my_a3p_driver";
>>                         reg = <0x0 0x0 0x800000>;
>>                 };
>>         };
>
> Compatible describes the device, not the driver.  It takes the format
> "vendor,device".  The node name, OTOH, is normally a generic description
> of the device's functionality ("flash", "ethernet", "board-control",
> etc).
>
> You don't need #address-cells/#size-cells on the a3p400 node unless it
> has child nodes with reg or ranges.
>
> -Scott
>
>
>

      reply	other threads:[~2013-10-22  9:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-08 14:06 Elbc device driver Mercier Ivan
2013-10-08 22:34 ` Scott Wood
2013-10-10 14:54   ` Mercier Ivan
2013-10-10 15:14     ` Scott Wood
2013-10-11 15:03       ` Mercier Ivan
2013-10-11 17:35         ` Scott Wood
2013-10-22  9:43           ` Mercier Ivan [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='CAMc2ierLhKeLX2ijUBaVU=suF3OF4DPku2N+WBTE1HvMPc3yaQ@mail.gmail.com' \
    --to=ivan.mercier@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=scottwood@freescale.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).