On Wed, Jan 11, 2017 at 03:05:20PM +0100, yegorslists@xxxxxxxxxxxxxx wrote:
> From: Anton Glukhov <anton.a.glukhov@xxxxxxxxx>
>
> DT binding documentation for TI High End CAN Controller
>
> Signed-off-by: Anton Glukhov <anton.a.glukhov@xxxxxxxxx>
> Signed-off-by: Yegor Yefremov <yegorslists@xxxxxxxxxxxxxx>
> ---
> Changes v1 -> v2:
> change compatible to "ti,am3505"
>
> .../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..ce015cf
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/can/ti_hecc.txt
> @@ -0,0 +1,31 @@
> +* Texas Instruments High End CAN Controller (HECC)
> +
> +This file provides information, what the device node
> +for the hecc interface contains.
> +
> +Required properties:
> +- compatible: "ti,am3505"
> +- 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
Is there not a common case that would be the default?
> +
> +Optional properties:
> +- ti,int-line: interrupt line
Needs a better description. What are valid values? This is some internal
setting about which pin to route the interrupt output to I'm guessing.
> +
> +Example:
> +
> +For am3517evm board:
> + hecc: can@0x5c050000 {
> + compatible = "ti,am3505";
> + 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>;
> + };
> --
> 2.1.4
>
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
