From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Gerhard Bertelsmann <info@gerhard-bertelsmann.de>,
linux-can@vger.kernel.org
Subject: Re: [PATCH v2 1/2] Allwinner SoC CAN controller Support
Date: Tue, 8 Sep 2015 12:57:21 +0200 [thread overview]
Message-ID: <55EEBF11.4020301@pengutronix.de> (raw)
In-Reply-To: <1441274970-5632-2-git-send-email-info@gerhard-bertelsmann.de>
[-- Attachment #1: Type: text/plain, Size: 2224 bytes --]
On 09/03/2015 12:09 PM, Gerhard Bertelsmann wrote:
> Devicetree Bindings documentation
>
> Signed-off-by: Gerhard Bertelsmann < info@gerhard-bertelsmann.de >
^ ^
nitpick: no space here.
Please format your subject like: "can: add Allwinner SoC CAN controller
Devicetree Bindings documentation".
>
>
> .../devicetree/bindings/net/can/sunxi_can.txt | 42 ++
> 1 files changed, 42 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/net/can/sunxi_can.txt b/Documentation/devicetree/bindings/net/can/sunxi_can.txt
> new file mode 100644
> index 0000000..454e92f
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/can/sunxi_can.txt
> @@ -0,0 +1,42 @@
> +Allwinner A10/A20 CAN controller Device Tree Bindings
> +-----------------------------------------------------
> +
> +Required properties:
> +- compatible: "allwinner,sunxican"
> +- reg: physical base address and size of the Allwinner A10/A20 CAN register map.
> +- interrupts: interrupt specifier for the sole interrupt.
> +- clocks: phandle and clock specifier.
> +- pinctrl-0: pin control group to be used for this controller.
> +- pinctrl-names: must be "default".
> +
> +
> +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,sunxican";
> + reg = <0x01c2bc00 0x400>;
> + interrupts = <0 26 4>;
> + clocks = <&apb1_gates 4>;
> + status = "disabled";
> + #address-cells = <1>;
> + #size-cells = <0>;
Why address and size cells?
> + };
> +
> +Board specific .dts file:
> +
> + can0: can@01c2bc00 {
> + pinctrl-names = "default";
> + pinctrl-0 = <&can0_pins_a>;
> + status = "okay";
> + };
> +
>
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2015-09-08 10:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 10:09 [PATCH v2 0/2] Allwinner SoC CAN controller Support Gerhard Bertelsmann
2015-09-03 10:09 ` [PATCH v2 1/2] " Gerhard Bertelsmann
2015-09-08 10:57 ` Marc Kleine-Budde [this message]
2015-09-03 10:09 ` [PATCH v2 2/2] " Gerhard Bertelsmann
2015-09-03 11:13 ` Andri Yngvason
2015-09-08 10:51 ` Marc Kleine-Budde
2015-09-10 6:29 ` Gerhard Bertelsmann
2015-09-10 8:17 ` Marc Kleine-Budde
2015-09-10 8:29 ` Mirza Krak
2015-09-10 9:07 ` 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=55EEBF11.4020301@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=info@gerhard-bertelsmann.de \
--cc=linux-can@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).