[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200219203529.GA21085@bogus>
Date: Wed, 19 Feb 2020 14:35:29 -0600
From: Rob Herring <robh@...nel.org>
To: Faiz Abbas <faiz_abbas@...com>
Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, netdev@...r.kernel.org,
linux-can@...r.kernel.org, broonie@...nel.org, lgirdwood@...il.com,
catalin.marinas@....com, mark.rutland@....com, mkl@...gutronix.de,
wg@...ndegger.com, sriram.dash@...sung.com, dmurphy@...com
Subject: Re: [PATCH v2 1/3] dt-bindings: m_can: Add Documentation for
transceiver regulator
On Mon, Feb 17, 2020 at 07:58:34PM +0530, Faiz Abbas wrote:
> Some CAN transceivers have a standby line that needs to be asserted
> before they can be used. Model this GPIO lines as an optional
> fixed-regulator node. Document bindings for the same.
>
> Signed-off-by: Faiz Abbas <faiz_abbas@...com>
> ---
> Documentation/devicetree/bindings/net/can/m_can.txt | 3 +++
> 1 file changed, 3 insertions(+)
This has moved to DT schema in my tree, so please adjust it and resend.
> diff --git a/Documentation/devicetree/bindings/net/can/m_can.txt b/Documentation/devicetree/bindings/net/can/m_can.txt
> index ed614383af9c..f17e2a5207dc 100644
> --- a/Documentation/devicetree/bindings/net/can/m_can.txt
> +++ b/Documentation/devicetree/bindings/net/can/m_can.txt
> @@ -48,6 +48,9 @@ Optional Subnode:
> that can be used for CAN/CAN-FD modes. See
> Documentation/devicetree/bindings/net/can/can-transceiver.txt
> for details.
> +
> +- xceiver-supply: Regulator that powers the CAN transceiver.
The supply for a transceiver should go in the transceiver node.
> +
> Example:
> SoC dtsi:
> m_can1: can@...8000 {
> --
> 2.19.2
>
Powered by blists - more mailing lists