[PATCH 1/2] dt-bindings: phy: ti,tcan104x-can: Document mux-states property
From: Aswath Govindraju <hidden>
Date: 2021-12-02 13:10:50
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. This can be implemented using mux-states property. Therefore, document the same in the respective bindings. Signed-off-by: Aswath Govindraju <redacted> --- .../devicetree/bindings/phy/ti,tcan104x-can.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+)
diff --git a/Documentation/devicetree/bindings/phy/ti,tcan104x-can.yaml b/Documentation/devicetree/bindings/phy/ti,tcan104x-can.yaml
index 6107880e5246..5b2b08016635 100644
--- a/Documentation/devicetree/bindings/phy/ti,tcan104x-can.yaml
+++ b/Documentation/devicetree/bindings/phy/ti,tcan104x-can.yaml@@ -37,6 +37,18 @@ properties: max bit rate supported in bps minimum: 1 + mux-states: + description: + mux controller node to route the signals from controller to + transceiver. Depending on the mux chip and the control lines + in it, the first and second parameters can be used for + representing control line and state. The number of arguments + is to be used based on '#mux-state-cells' property in the + mux-controller node. If '#mux-state-cells' is equal to + one then, then the argument to be used would be the state. + If it is set to two, then the first argument is the control + line and the second argument would be its corresponding state. + required: - compatible - '#phy-cells'
@@ -53,4 +65,5 @@ examples: max-bitrate = <5000000>; standby-gpios = <&wakeup_gpio1 16 GPIO_ACTIVE_LOW>; enable-gpios = <&main_gpio1 67 GPIO_ACTIVE_HIGH>; + mux-states = <&mux0 1>; };
--
2.17.1