From: Franklin S Cooper Jr <fcooper@ti.com> To: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, netdev@vger.kernel.org, linux-can@vger.kernel.org, wg@grandegger.com, mkl@pengutronix.de, robh+dt@kernel.org, quentin.schulz@free-electrons.com, dev.kurt@vandijck-laurijssen.be, andrew@lunn.ch, sergei.shtylyov@cogentembedded.com, socketcan@hartkopp.net Cc: Franklin S Cooper Jr <fcooper@ti.com> Subject: [PATCH v2 3/4] can: m_can: Update documentation to mention new fixed transceiver binding Date: Mon, 24 Jul 2017 18:05:20 -0500 [thread overview] Message-ID: <20170724230521.1436-4-fcooper@ti.com> (raw) In-Reply-To: <20170724230521.1436-1-fcooper@ti.com> Add information regarding fixed transceiver binding. This is especially important for MCAN since the IP allows CAN FD mode to run significantly faster than what most transceivers are capable of. Signed-off-by: Franklin S Cooper Jr <fcooper@ti.com> --- Version 2 changes: Drop unit address Documentation/devicetree/bindings/net/can/m_can.txt | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/Documentation/devicetree/bindings/net/can/m_can.txt b/Documentation/devicetree/bindings/net/can/m_can.txt index 9e33177..e4abd2c 100644 --- a/Documentation/devicetree/bindings/net/can/m_can.txt +++ b/Documentation/devicetree/bindings/net/can/m_can.txt @@ -43,6 +43,11 @@ Required properties: Please refer to 2.4.1 Message RAM Configuration in Bosch M_CAN user manual for details. +Optional properties: +- fixed-transceiver : Fixed-transceiver subnode describing maximum speed + that can be used for CAN and/or CAN-FD modes. See + Documentation/devicetree/bindings/net/can/fixed-transceiver.txt + for details. Example: SoC dtsi: m_can1: can@020e8000 { @@ -64,4 +69,9 @@ Board dts: pinctrl-names = "default"; pinctrl-0 = <&pinctrl_m_can1>; status = "enabled"; + + fixed-transceiver { + max-arbitration-speed = <1000000>; + max-data-speed = <5000000>; + }; }; -- 2.10.0
WARNING: multiple messages have this Message-ID (diff)
From: Franklin S Cooper Jr <fcooper@ti.com> To: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>, <netdev@vger.kernel.org>, <linux-can@vger.kernel.org>, <wg@grandegger.com>, <mkl@pengutronix.de>, <robh+dt@kernel.org>, <quentin.schulz@free-electrons.com>, <dev.kurt@vandijck-laurijssen.be>, <andrew@lunn.ch>, <sergei.shtylyov@cogentembedded.com>, <socketcan@hartkopp.net> Cc: Franklin S Cooper Jr <fcooper@ti.com> Subject: [PATCH v2 3/4] can: m_can: Update documentation to mention new fixed transceiver binding Date: Mon, 24 Jul 2017 18:05:20 -0500 [thread overview] Message-ID: <20170724230521.1436-4-fcooper@ti.com> (raw) In-Reply-To: <20170724230521.1436-1-fcooper@ti.com> Add information regarding fixed transceiver binding. This is especially important for MCAN since the IP allows CAN FD mode to run significantly faster than what most transceivers are capable of. Signed-off-by: Franklin S Cooper Jr <fcooper@ti.com> --- Version 2 changes: Drop unit address Documentation/devicetree/bindings/net/can/m_can.txt | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/Documentation/devicetree/bindings/net/can/m_can.txt b/Documentation/devicetree/bindings/net/can/m_can.txt index 9e33177..e4abd2c 100644 --- a/Documentation/devicetree/bindings/net/can/m_can.txt +++ b/Documentation/devicetree/bindings/net/can/m_can.txt @@ -43,6 +43,11 @@ Required properties: Please refer to 2.4.1 Message RAM Configuration in Bosch M_CAN user manual for details. +Optional properties: +- fixed-transceiver : Fixed-transceiver subnode describing maximum speed + that can be used for CAN and/or CAN-FD modes. See + Documentation/devicetree/bindings/net/can/fixed-transceiver.txt + for details. Example: SoC dtsi: m_can1: can@020e8000 { @@ -64,4 +69,9 @@ Board dts: pinctrl-names = "default"; pinctrl-0 = <&pinctrl_m_can1>; status = "enabled"; + + fixed-transceiver { + max-arbitration-speed = <1000000>; + max-data-speed = <5000000>; + }; }; -- 2.10.0
next prev parent reply other threads:[~2017-07-24 23:05 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-07-24 23:05 [PATCH v2 0/4] can: Add new binding to limit bit rate used Franklin S Cooper Jr 2017-07-24 23:05 ` Franklin S Cooper Jr 2017-07-24 23:05 ` Franklin S Cooper Jr 2017-07-24 23:05 ` [PATCH v2 1/4] can: dev: Add support for limiting configured bitrate Franklin S Cooper Jr 2017-07-24 23:05 ` Franklin S Cooper Jr 2017-07-24 23:05 ` Franklin S Cooper Jr [this message] 2017-07-24 23:05 ` [PATCH v2 3/4] can: m_can: Update documentation to mention new fixed transceiver binding Franklin S Cooper Jr 2017-08-03 17:07 ` Rob Herring 2017-08-10 1:02 ` Franklin S Cooper Jr 2017-08-10 1:02 ` Franklin S Cooper Jr [not found] ` <20170724230521.1436-1-fcooper-l0cyMroinI0@public.gmane.org> 2017-07-24 23:05 ` [PATCH v2 2/4] can: fixed-transceiver: Add documentation for CAN fixed transceiver bindings Franklin S Cooper Jr 2017-07-24 23:05 ` Franklin S Cooper Jr 2017-07-24 23:05 ` Franklin S Cooper Jr 2017-07-25 16:32 ` Oliver Hartkopp [not found] ` <29df7e04-01c6-a09b-491e-1354dab98cd0-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org> 2017-07-25 18:14 ` Franklin S Cooper Jr 2017-07-25 18:14 ` Franklin S Cooper Jr 2017-07-25 18:14 ` Franklin S Cooper Jr 2017-07-26 16:41 ` Andrew Lunn 2017-07-26 17:05 ` Oliver Hartkopp [not found] ` <355b90b3-97ce-1057-6617-d5d709449c48-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org> 2017-07-26 18:29 ` Franklin S Cooper Jr 2017-07-26 18:29 ` Franklin S Cooper Jr 2017-07-26 18:29 ` Franklin S Cooper Jr [not found] ` <a77fe395-33c7-9405-b51a-5d3372e5c58b-l0cyMroinI0@public.gmane.org> 2017-07-27 18:47 ` Oliver Hartkopp 2017-07-27 18:47 ` Oliver Hartkopp 2017-07-27 21:10 ` Franklin S Cooper Jr 2017-07-27 21:10 ` Franklin S Cooper Jr 2017-07-28 4:57 ` Kurt Van Dijck 2017-07-28 8:41 ` Oliver Hartkopp 2017-07-24 23:05 ` [PATCH v2 4/4] can: m_can: Add call to of_can_transceiver_fixed Franklin S Cooper Jr 2017-07-24 23:05 ` Franklin S Cooper Jr 2017-07-24 23:05 ` Franklin S Cooper Jr
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=20170724230521.1436-4-fcooper@ti.com \ --to=fcooper@ti.com \ --cc=andrew@lunn.ch \ --cc=dev.kurt@vandijck-laurijssen.be \ --cc=devicetree@vger.kernel.org \ --cc=linux-can@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mkl@pengutronix.de \ --cc=netdev@vger.kernel.org \ --cc=quentin.schulz@free-electrons.com \ --cc=robh+dt@kernel.org \ --cc=sergei.shtylyov@cogentembedded.com \ --cc=socketcan@hartkopp.net \ --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: linkBe 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.