[PATCH v2 1/2] dt-bindings: phy: ti, tcan104x-can: Document mux-states property
From: Aswath Govindraju <hidden>
Date: 2021-12-14 14:30:08
Also in:
linux-can, linux-devicetree, 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 | 10 ++++++++++ 1 file changed, 10 insertions(+)
diff --git a/Documentation/devicetree/bindings/phy/ti,tcan104x-can.yaml b/Documentation/devicetree/bindings/phy/ti,tcan104x-can.yaml
index 6107880e5246..7b9216e43b58 100644
--- a/Documentation/devicetree/bindings/phy/ti,tcan104x-can.yaml
+++ b/Documentation/devicetree/bindings/phy/ti,tcan104x-can.yaml@@ -37,6 +37,15 @@ properties: max bit rate supported in bps minimum: 1 + mux-states: + description: + mux controller node to route the signals from controller to + transceiver. Two arguments can be present depending on the + mux chip. If one argument is used then it represents the state + to be set on the mux-chip. If there are two arguments then the + first argument is the control line and the second argument is + its corresponding state to be set, on the mux-chip. + required: - compatible - '#phy-cells'
@@ -53,4 +62,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
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy