[PATCH RFC v3 2/4] dt-bindings: phy: ti,tcan104x-can: Document mux-controls property
From: Aswath Govindraju <hidden>
Date: 2021-11-23 08:13:18
Also in:
linux-can, linux-phy, lkml
Subsystem:
can network drivers, generic phy framework, open firmware and flattened device tree bindings, the rest · Maintainers:
Marc Kleine-Budde, Vincent Mailhol, Vinod Koul, Rob Herring, Krzysztof Kozlowski, Conor Dooley, Linus Torvalds
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 <redacted> --- .../devicetree/bindings/phy/ti,tcan104x-can.yaml | 8 ++++++++ 1 file changed, 8 insertions(+)
diff --git a/Documentation/devicetree/bindings/phy/ti,tcan104x-can.yaml b/Documentation/devicetree/bindings/phy/ti,tcan104x-can.yaml
index 6107880e5246..7392088cf060 100644
--- a/Documentation/devicetree/bindings/phy/ti,tcan104x-can.yaml
+++ b/Documentation/devicetree/bindings/phy/ti,tcan104x-can.yaml@@ -37,6 +37,13 @@ properties: max bit rate supported in bps minimum: 1 + mux-controls: + description: + mux controller node to route the signals from controller to + transceiver. The first and second arguments can be used + representing the line in the mux-controller to control and + the state to be set in the given line respectively. + required: - compatible - '#phy-cells'
@@ -53,4 +60,5 @@ examples: max-bitrate = <5000000>; standby-gpios = <&wakeup_gpio1 16 GPIO_ACTIVE_LOW>; enable-gpios = <&main_gpio1 67 GPIO_ACTIVE_HIGH>; + mux-controls = <&mux0 0 1>; };
--
2.17.1