From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Anton Glukhov <anton.a.glukhov@gmail.com>,
linux-can@vger.kernel.org, bcousson@baylibre.com
Subject: Re: [PATCH 2/3] can: ti_hecc: Add TI HECC DT binding documentation
Date: Mon, 12 Oct 2015 11:50:02 +0200 [thread overview]
Message-ID: <561B824A.3080003@pengutronix.de> (raw)
In-Reply-To: <1443988779-19935-2-git-send-email-anton.a.glukhov@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2145 bytes --]
On 10/04/2015 09:59 PM, Anton Glukhov wrote:
> DT binding documentation for TI High End CAN Controller
Please add the device tree binding discussion mailing list on Cc.
>
> Signed-off-by: Anton Glukhov <anton.a.glukhov@gmail.com>
> ---
> .../devicetree/bindings/net/can/ti_hecc.txt | 31 ++++++++++++++++++++++
> 1 file changed, 31 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/net/can/ti_hecc.txt
>
> diff --git a/Documentation/devicetree/bindings/net/can/ti_hecc.txt b/Documentation/devicetree/bindings/net/can/ti_hecc.txt
> new file mode 100644
> index 0000000..e29b0ec
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/can/ti_hecc.txt
> @@ -0,0 +1,31 @@
> +* Texas Instruments High End CAN Controller
> +
> +This file provides information, what the device node
> +for the hecc interface contains.
> +
> +Required properties:
> +- compatible: "ti,am35x-hecc"
> +- reg: offset and length of the register set for the device
> +- interrupts: interrupt mapping for the hecc interrupts sources
> +- clocks: clock phandles (see clock bindings for details)
> +- ti,scc-ram-offset: offset to scc module ram
> +- ti,hecc-ram-offset: offset to hecc module ram
> +- ti,mbx-offset: offset to mailbox ram
Are the offsets a per SoC parameter? I'm not sure if it's better to put
the offsets into the driver.
> +
> +Optional properties:
> +- ti,int-line: interrupt line
Better make it a bool and describe it better.
> +
> +Example:
> +
> +For am3517evm board:
> + hecc: can@0x5c050000 {
> + compatible = "ti,am35x-hecc";
> + status = "disabled";
> + reg = <0x5c050000 0x4000>;
> + interrupts = <24>;
> + clocks = <&hecc_ck>;
> + ti,scc-ram-offset = <0x3000>;
> + ti,hecc-ram-offset = <0x3000>;
> + ti,mbx-offset = <0x2000>;
> + ti,int-line = <0>;
> + };
>
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-10-12 9:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-04 19:59 [PATCH 1/3] can: ti_hecc: Add DT support for TI HECC module Anton Glukhov
2015-10-04 19:59 ` [PATCH 2/3] can: ti_hecc: Add TI HECC DT binding documentation Anton Glukhov
2015-10-12 9:50 ` Marc Kleine-Budde [this message]
2015-10-04 19:59 ` [PATCH 3/3] ARM: dts: AM35x: Add hecc node Anton Glukhov
2015-10-12 9:42 ` [PATCH 1/3] can: ti_hecc: Add DT support for TI HECC module Marc Kleine-Budde
2016-03-16 10:53 ` 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=561B824A.3080003@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=anton.a.glukhov@gmail.com \
--cc=bcousson@baylibre.com \
--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).