devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Faiz Abbas <faiz_abbas@ti.com>
To: wg@grandegger.com, mkl@pengutronix.de, robh+dt@kernel.org,
	mark.rutland@arm.com
Cc: linux-can@vger.kernel.org, netdev@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	faiz_abbas@ti.com, nsekhar@ti.com, fcooper@ti.com,
	robh@kernel.org, Wenyou.Yang@microchip.com,
	sergei.shtylyov@cogentembedded.com, linux-omap@vger.kernel.org,
	b29396@freescale.com
Subject: [PATCH v8 2/5] dt-bindings: can: can-transceiver: Document new binding
Date: Tue, 16 Jan 2018 17:07:11 +0530	[thread overview]
Message-ID: <1516102634-6771-3-git-send-email-faiz_abbas@ti.com> (raw)
In-Reply-To: <1516102634-6771-1-git-send-email-faiz_abbas@ti.com>

From: Franklin S Cooper Jr <fcooper@ti.com>

Add documentation to describe usage of the new can-transceiver binding.
This new binding is applicable for any CAN device therefore it exists as
its own document.

Signed-off-by: Franklin S Cooper Jr <fcooper@ti.com>
Signed-off-by: Sekhar Nori <nsekhar@ti.com>
Acked-by: Rob Herring <robh@kernel.org>
Signed-off-by: Faiz Abbas <faiz_abbas@ti.com>
---
 .../bindings/net/can/can-transceiver.txt           | 24 ++++++++++++++++++++++
 1 file changed, 24 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/net/can/can-transceiver.txt

diff --git a/Documentation/devicetree/bindings/net/can/can-transceiver.txt b/Documentation/devicetree/bindings/net/can/can-transceiver.txt
new file mode 100644
index 0000000..0011f53
--- /dev/null
+++ b/Documentation/devicetree/bindings/net/can/can-transceiver.txt
@@ -0,0 +1,24 @@
+Generic CAN transceiver Device Tree binding
+------------------------------
+
+CAN transceiver typically limits the max speed in standard CAN and CAN FD
+modes. Typically these limitations are static and the transceivers themselves
+provide no way to detect this limitation at runtime. For this situation,
+the "can-transceiver" node can be used.
+
+Required Properties:
+ max-bitrate:	a positive non 0 value that determines the max
+		speed that CAN/CAN-FD can run. Any other value
+		will be ignored.
+
+Examples:
+
+Based on Texas Instrument's TCAN1042HGV CAN Transceiver
+
+m_can0 {
+	....
+	can-transceiver {
+		max-bitrate = <5000000>;
+	};
+	...
+};
-- 
2.7.4

  parent reply	other threads:[~2018-01-16 11:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-16 11:37 [PATCH v8 0/5] Add MCAN Support for Dra76 platform Faiz Abbas
2018-01-16 11:37 ` [PATCH v8 1/5] dt-bindings: can: m_can: Document new can transceiver binding Faiz Abbas
2018-01-16 11:37 ` Faiz Abbas [this message]
2018-01-16 11:37 ` [PATCH v8 3/5] can: m_can: Move allocation of net device to probe Faiz Abbas
     [not found]   ` <1516102634-6771-4-git-send-email-faiz_abbas-l0cyMroinI0@public.gmane.org>
2018-01-16 13:03     ` Marc Kleine-Budde
     [not found]       ` <caa11848-3c69-1229-e4b8-09e51cebe739-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2018-01-16 14:00         ` Marc Kleine-Budde
2018-01-16 11:37 ` [PATCH v8 4/5] can: m_can: Add PM Support Faiz Abbas
2018-01-16 12:57   ` Marc Kleine-Budde
2018-01-16 11:37 ` [PATCH v8 5/5] can: m_can: Support higher speed CAN-FD bitrates Faiz Abbas
2018-01-16 14:12 ` [PATCH v8 0/5] Add MCAN Support for Dra76 platform 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=1516102634-6771-3-git-send-email-faiz_abbas@ti.com \
    --to=faiz_abbas@ti.com \
    --cc=Wenyou.Yang@microchip.com \
    --cc=b29396@freescale.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fcooper@ti.com \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=nsekhar@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=sergei.shtylyov@cogentembedded.com \
    --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).