From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Gerhard Bertelsmann <info@gerhard-bertelsmann.de>,
wg@grandegger.com, linux-can@vger.kernel.org,
netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 1/3] can: Allwinner A10/A20 CAN Controller support - Devicetree bindings
Date: Thu, 17 Sep 2015 12:06:17 +0200 [thread overview]
Message-ID: <20150917100617.GB4684@lukather> (raw)
In-Reply-To: <55FA7428.4030801@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 2053 bytes --]
On Thu, Sep 17, 2015 at 10:04:56AM +0200, Marc Kleine-Budde wrote:
> On 09/16/2015 01:21 PM, Gerhard Bertelsmann wrote:
> > Devicetree bindings for Allwinner A10/A20 CAN
> >
> > Signed-off-by: Gerhard Bertelsmann <info@gerhard-bertelsmann.de>
> > ---
> >
> > .../devicetree/bindings/net/can/sun4i_can.txt | 38 +
> > 1 files changed, 389 insertions(+)
> >
> >
> > diff --git a/Documentation/devicetree/bindings/net/can/sun4i_can.txt b/Documentation/devicetree/bindings/net/can/sun4i_can.txt
> > new file mode 100644
> > index 0000000..cd0f50c
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/net/can/sun4i_can.txt
> > @@ -0,0 +1,38 @@
> > +Allwinner A10/A20 CAN controller Device Tree Bindings
> > +-----------------------------------------------------
> > +
> > +Required properties:
> > +- compatible: "allwinner,sun4i-a10-can"
> > +- reg: physical base address and size of the Allwinner A10/A20 CAN register map.
> > +- interrupts: interrupt specifier for the sole interrupt.
> > +- clock: phandle and clock specifier.
> > +
> > +
> > +Example
> > +-------
> > +
> > +SoC common .dtsi file:
> > +
> > + can0_pins_a: can0@0 {
> > + allwinner,pins = "PH20","PH21";
> > + allwinner,function = "can";
> > + allwinner,drive = <0>;
> > + allwinner,pull = <0>;
> > + };
> > +...
> > + can0: can@01c2bc00 {
> > + compatible = "allwinner,sun4i-a10-can";
> > + reg = <0x01c2bc00 0x400>;
> > + interrupts = <0 26 4>;
> > + clocks = <&apb1_gates 4>;
> > + status = "disabled";
> > + };
>
> What about adding this snippet to SoC where the CAN core is available?
> Maxime, what's the policy on sinxi?
It would be great, but it can come as a second step.
> If you give me an Ack I'd like to take the series via linux-can-next
> (and to net-next) upstream.
I just did so for this patch, I'll review the driver when I'll have a
bit of time.
Thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-09-17 10:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 11:21 [PATCH v8 0/4] can: Allwinner A10/A20 CAN Controller support - Summary Gerhard Bertelsmann
2015-09-16 11:21 ` [PATCH v8 1/3] can: Allwinner A10/A20 CAN Controller support - Devicetree bindings Gerhard Bertelsmann
2015-09-17 8:04 ` Marc Kleine-Budde
2015-09-17 10:06 ` Maxime Ripard [this message]
2015-09-17 10:05 ` Maxime Ripard
2015-09-16 11:21 ` [PATCH v8 2/4] can: Allwinner A10/A20 CAN Controller support - Defconfig Gerhard Bertelsmann
2015-09-16 11:21 ` [PATCH v8 3/4] " Gerhard Bertelsmann
2015-09-16 11:21 ` [PATCH v8 4/4] can: Allwinner A10/A20 CAN Controller support - Kernel module Gerhard Bertelsmann
2015-09-17 17:52 ` Maxime Ripard
2015-09-17 17:54 ` [PATCH v8 0/4] can: Allwinner A10/A20 CAN Controller support - Summary Maxime Ripard
2015-09-17 18:12 ` Oliver Hartkopp
2015-09-17 18:27 ` Maxime Ripard
2015-09-17 18:29 ` Oliver Hartkopp
2015-09-17 20:57 ` 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=20150917100617.GB4684@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=info@gerhard-bertelsmann.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=wg@grandegger.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).