[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 11 Nov 2021 22:13:11 +0530
From: Aswath Govindraju <a-govindraju@...com>
To: unlisted-recipients:; (no To-header on input)
CC: Vignesh Raghavendra <vigneshr@...com>,
Kishon Vijay Abraham I <kishon@...com>,
Nishanth Menon <nm@...com>,
Aswath Govindraju <a-govindraju@...com>,
Wolfgang Grandegger <wg@...ndegger.com>,
Marc Kleine-Budde <mkl@...gutronix.de>,
Vinod Koul <vkoul@...nel.org>,
Rob Herring <robh+dt@...nel.org>, <linux-can@...r.kernel.org>,
<linux-phy@...ts.infradead.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
Subject: [PATCH RFC 1/2] dt-bindings: phy: ti,tcan104x-can: Document mux-controls property
On some boards, for routing CAN signals from controller to transceivers,
muxes might need to be set. Use mux-controls property can be used for model
this.
Signed-off-by: Aswath Govindraju <a-govindraju@...com>
---
Documentation/devicetree/bindings/phy/ti,tcan104x-can.yaml | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/Documentation/devicetree/bindings/phy/ti,tcan104x-can.yaml b/Documentation/devicetree/bindings/phy/ti,tcan104x-can.yaml
index 6107880e5246..24cc3c04b85d 100644
--- a/Documentation/devicetree/bindings/phy/ti,tcan104x-can.yaml
+++ b/Documentation/devicetree/bindings/phy/ti,tcan104x-can.yaml
@@ -37,6 +37,11 @@ properties:
max bit rate supported in bps
minimum: 1
+ mux-controls:
+ description:
+ mux controller node to route the signals from controller to
+ transceiver.
+
required:
- compatible
- '#phy-cells'
@@ -53,4 +58,5 @@ examples:
max-bitrate = <5000000>;
standby-gpios = <&wakeup_gpio1 16 GPIO_ACTIVE_LOW>;
enable-gpios = <&main_gpio1 67 GPIO_ACTIVE_HIGH>;
+ mux-controls = <&mux0>;
};
--
2.17.1
Powered by blists - more mailing lists