[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170719230926.10872-3-fcooper@ti.com>
Date: Wed, 19 Jul 2017 18:09:25 -0500
From: Franklin S Cooper Jr <fcooper@...com>
To: <linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>,
<netdev@...r.kernel.org>, <linux-can@...r.kernel.org>,
<wg@...ndegger.com>, <mkl@...gutronix.de>, <robh+dt@...nel.org>,
<quentin.schulz@...e-electrons.com>
CC: Franklin S Cooper Jr <fcooper@...com>
Subject: [PATCH 2/3] can: m_can: Update documentation to indicate that hclk may be optional
Update the documentation to reflect that hclk is now an optional clock.
Signed-off-by: Franklin S Cooper Jr <fcooper@...com>
---
Documentation/devicetree/bindings/net/can/m_can.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/net/can/m_can.txt b/Documentation/devicetree/bindings/net/can/m_can.txt
index 9e33177..2a0fe5b 100644
--- a/Documentation/devicetree/bindings/net/can/m_can.txt
+++ b/Documentation/devicetree/bindings/net/can/m_can.txt
@@ -12,7 +12,8 @@ Required properties:
- interrupt-names : Should contain "int0" and "int1"
- clocks : Clocks used by controller, should be host clock
and CAN clock.
-- clock-names : Should contain "hclk" and "cclk"
+- clock-names : Should contain "hclk" and "cclk". For some socs hclk
+ may be optional.
- pinctrl-<n> : Pinctrl states as described in bindings/pinctrl/pinctrl-bindings.txt
- pinctrl-names : Names corresponding to the numbered pinctrl states
- bosch,mram-cfg : Message RAM configuration data.
--
2.10.0
Powered by blists - more mailing lists