From: Aswath Govindraju <a-govindraju@ti.com>
To: Rob Herring <robh@kernel.org>
Cc: Wolfgang Grandegger <wg@grandegger.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Kishon Vijay Abraham I <kishon@ti.com>,
Vinod Koul <vkoul@kernel.org>, <linux-can@vger.kernel.org>,
<linux-phy@lists.infradead.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] dt-bindings: phy: ti,tcan104x-can: Document mux-states property
Date: Thu, 16 Dec 2021 09:29:36 +0530 [thread overview]
Message-ID: <71c926f5-7dd5-b2c3-d31c-fbc7a3d553c4@ti.com> (raw)
In-Reply-To: <YbpSy0+x/SnTYUzb@robh.at.kernel.org>
Hi Rob,
On 16/12/21 2:10 am, Rob Herring wrote:
> On Tue, Dec 14, 2021 at 07:59:07PM +0530, Aswath Govindraju wrote:
>> 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 <a-govindraju@ti.com>
>> ---
>> .../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.
>> +
>
> You are still describing how the mux-states works. What the cells
> contain and how many are opaque to this binding. Here you need to
> describe how many muxes you have and what they are controlling as that
> is what is specific to this binding. If there is only one, this boils
> down to 'maxItems: 1'. It's just like reg, interrupts, clocks, etc.
>
Got it. Thank you for the clarification. Amending the description to the
following,
mux-states:
description:
mux controller node to route the signals from controller to
transceiver.
maxItems: 1
Thanks,
Aswath
>> 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
>>
>>
next prev parent reply other threads:[~2021-12-16 4:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 14:29 [PATCH v2 0/2] CAN: Add support for setting mux Aswath Govindraju
2021-12-14 14:29 ` [PATCH v2 1/2] dt-bindings: phy: ti,tcan104x-can: Document mux-states property Aswath Govindraju
2021-12-15 20:40 ` Rob Herring
2021-12-16 3:59 ` Aswath Govindraju [this message]
2021-12-14 14:29 ` [PATCH v2 2/2] phy: phy-can-transceiver: Add support for setting mux 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=71c926f5-7dd5-b2c3-d31c-fbc7a3d553c4@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=robh@kernel.org \
--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
all inboxes | Powered by JetHome®