netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Grandegger <wg@grandegger.com>
To: David Miller <davem@davemloft.net>
Cc: grant.likely@secretlab.ca, netdev@vger.kernel.org,
	Linuxppc-dev@ozlabs.org, devicetree-discuss@ozlabs.org
Subject: Re: [net-next-2.6 PATCH] can: SJA1000: generic OF platform bus driver
Date: Fri, 22 May 2009 16:47:26 +0200	[thread overview]
Message-ID: <4A16BAFE.7090401@grandegger.com> (raw)
In-Reply-To: <20090521.233123.135354184.davem@davemloft.net>

David Miller wrote:
> From: Grant Likely <grant.likely@secretlab.ca>
> Date: Thu, 21 May 2009 22:42:07 -0600
> 
>> On Wed, May 20, 2009 at 11:06 AM, Wolfgang Grandegger <wg@grandegger.com> wrote:
>>> This patch adds a generic driver for SJA1000 chips on the OpenFirmware
>>> platform bus found on embedded PowerPC systems. You need a SJA1000 node
>>> definition in your flattened device tree source (DTS) file similar to:
>>>
>>>   can@3,100 {
>>>           compatible = "philips,sja1000";
>>>           reg = <3 0x100 0x80>;
>>>           clock-frequency = <8000000>;
>>>           cdr-reg = <0x48>;
>>>           ocr-reg = <0x0a>;
>>>           interrupts = <2 0>;
>>>           interrupt-parent = <&mpic>;
>>>   };
>> This new binding must be documented in Documentation/powerpc/dts-bindings
> 
> Wolfgang, please add this documentation and resubmit your patch.
> Thanks!

I just sent out v2 incuding the missing documentation.

Thanks,

Wolfgang.

      reply	other threads:[~2009-05-22 14:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-20 17:06 [net-next-2.6 PATCH] can: SJA1000: generic OF platform bus driver Wolfgang Grandegger
2009-05-22  4:42 ` Grant Likely
     [not found]   ` <fa686aa40905212142n4a8c3caamb2f28eef036e3922-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-05-22  6:31     ` David Miller
2009-05-22 14:47       ` Wolfgang Grandegger [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=4A16BAFE.7090401@grandegger.com \
    --to=wg@grandegger.com \
    --cc=Linuxppc-dev@ozlabs.org \
    --cc=davem@davemloft.net \
    --cc=devicetree-discuss@ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=netdev@vger.kernel.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).