From: Aswath Govindraju <a-govindraju@ti.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Vignesh Raghavendra <vigneshr@ti.com>, Nishanth Menon <nm@ti.com>,
Aswath Govindraju <a-govindraju@ti.com>,
Peter Rosin <peda@axentia.se>, Rob Herring <robh+dt@kernel.org>,
Wolfgang Grandegger <wg@grandegger.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Kishon Vijay Abraham I <kishon@ti.com>,
Vinod Koul <vkoul@kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-can@vger.kernel.org>,
<linux-phy@lists.infradead.org>
Subject: [PATCH RFC v3 2/4] dt-bindings: phy: ti,tcan104x-can: Document mux-controls property
Date: Tue, 23 Nov 2021 13:42:19 +0530 [thread overview]
Message-ID: <20211123081222.27979-3-a-govindraju@ti.com> (raw)
In-Reply-To: <20211123081222.27979-1-a-govindraju@ti.com>
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@ti.com>
---
.../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
next prev parent reply other threads:[~2021-11-23 8:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 8:12 [PATCH RFC v3 0/4] MUX: Add support for reading enable state from DT Aswath Govindraju
2021-11-23 8:12 ` [PATCH RFC v3 1/4] dt-bindings: mux: Increase the number of arguments in mux-controls Aswath Govindraju
2021-11-25 13:35 ` Peter Rosin
2021-11-29 4:36 ` Aswath Govindraju
2021-11-29 8:15 ` Peter Rosin
2021-11-29 9:31 ` Aswath Govindraju
2021-11-29 12:28 ` Peter Rosin
2021-11-29 12:55 ` Aswath Govindraju
2021-11-23 8:12 ` Aswath Govindraju [this message]
2021-11-23 8:12 ` [PATCH RFC v3 3/4] mux: Add support for reading mux enable state from DT Aswath Govindraju
2021-11-25 13:52 ` Peter Rosin
2021-11-29 4:44 ` Aswath Govindraju
2021-11-29 8:36 ` Peter Rosin
2021-11-30 5:44 ` Aswath Govindraju
2021-11-30 5:58 ` Aswath Govindraju
2021-11-30 8:11 ` Peter Rosin
2021-11-23 8:12 ` [PATCH RFC v3 4/4] phy: phy-can-transceiver: Add support for setting mux Aswath Govindraju
2021-11-25 14:07 ` Peter Rosin
2021-11-29 4:51 ` Aswath Govindraju
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211123081222.27979-3-a-govindraju@ti.com \
--to=a-govindraju@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=mkl@pengutronix.de \
--cc=nm@ti.com \
--cc=peda@axentia.se \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.com \
--cc=vkoul@kernel.org \
--cc=wg@grandegger.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).