From: Rob Herring <robh@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: mkl@pengutronix.de, linux-can@vger.kernel.org,
qiangqing.zhang@nxp.com, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: can: fsl,flexcan.yaml: introduce the stb-gpios property
Date: Tue, 12 Jan 2021 21:23:55 -0600 [thread overview]
Message-ID: <20210113032355.GA1469209@robh.at.kernel.org> (raw)
In-Reply-To: <20210107205915.7602-1-festevam@gmail.com>
On Thu, Jan 07, 2021 at 05:59:14PM -0300, Fabio Estevam wrote:
> It is very common to have an STB pin in CAN transceivers, which allows
> putting the transceiver in standby or normal operation mode.
>
> Add a new optional 'stb-gpios' property to describe this.
>
> Signed-off-by: Fabio Estevam <festevam@gmail.com>
> ---
> Documentation/devicetree/bindings/net/can/fsl,flexcan.yaml | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/net/can/fsl,flexcan.yaml b/Documentation/devicetree/bindings/net/can/fsl,flexcan.yaml
> index 0d2df30f19db..64f904c4b3d5 100644
> --- a/Documentation/devicetree/bindings/net/can/fsl,flexcan.yaml
> +++ b/Documentation/devicetree/bindings/net/can/fsl,flexcan.yaml
> @@ -66,6 +66,9 @@ properties:
> xceiver-supply:
> description: Regulator that powers the CAN transceiver.
>
> + stb-gpios:
> + description: GPIO that controls the STB CAN transceiver pin.
maxItems: 1
> +
> big-endian:
> $ref: /schemas/types.yaml#/definitions/flag
> description: |
> --
> 2.17.1
>
prev parent reply other threads:[~2021-01-13 3:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 20:59 [PATCH 1/2] dt-bindings: can: fsl,flexcan.yaml: introduce the stb-gpios property Fabio Estevam
2021-01-07 20:59 ` [PATCH 2/2] can: flexcan: allow the control of the STB CAN transceiver pin Fabio Estevam
2021-01-13 3:23 ` Rob Herring [this message]
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=20210113032355.GA1469209@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=qiangqing.zhang@nxp.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