All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Grandegger <wg@grandegger.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Andreas Larsson <andreas@gaisler.com>,
	linux-can@vger.kernel.org, software@gaisler.com
Subject: Re: [PATCH] can: can_oc: Add driver for CAN_OC cores from Aeroflex Gaisler
Date: Wed, 26 Sep 2012 11:56:15 +0200	[thread overview]
Message-ID: <5062D13F.1090908@grandegger.com> (raw)
In-Reply-To: <5062CD27.3090803@pengutronix.de>

On 09/26/2012 11:38 AM, Marc Kleine-Budde wrote:
> On 09/25/2012 07:52 AM, Andreas Larsson wrote:
>> This driver is for the sja1000 compatible CAN_OC cores from Aeroflex
>> Gaisler available in the GRLIB VHDL IP core library.
> 
> Why don't you describe a single sja1000 compatible core with an OF
> device? The devices have indipendent address spaces and IRQs. With a
> proper abstraction/desciption you would not need this driver.

Right, at least I do not see anything special. The following DTS entry
should do the jobs:


  /* First CAN device */
  can@3,100 {
        compatible = "nxp,sja1000";
        reg = <3 0x100 0x80>;
        interrupts = <2 0>;
        interrupt-parent = <&mpic>;
        nxp,external-clock-frequency = <16000000>;
  };

  /* Second CAN device */
  can@3,200 {
        compatible = "nxp,sja1000";
        reg = <3 0x200 0x80>;
        interrupts = <2 0>;
        interrupt-parent = <&mpic>;
        nxp,external-clock-frequency = <16000000>;
  };

Addresses and IRQs might be different, of course.

See also;


http://lxr.linux.no/#linux+v3.5.4/Documentation/devicetree/bindings/net/can/sja1000.txt

Wolfgang.

  reply	other threads:[~2012-09-26  9:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-25  5:52 [PATCH] can: can_oc: Add driver for CAN_OC cores from Aeroflex Gaisler Andreas Larsson
2012-09-26  9:38 ` Marc Kleine-Budde
2012-09-26  9:56   ` Wolfgang Grandegger [this message]
2012-09-26 11:40     ` Andreas Larsson
2012-09-26 11:41       ` Marc Kleine-Budde
2012-09-26 12:55         ` Andreas Larsson
2012-09-26 12:58           ` Marc Kleine-Budde

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=5062D13F.1090908@grandegger.com \
    --to=wg@grandegger.com \
    --cc=andreas@gaisler.com \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=software@gaisler.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.