From: "Rob Herring (Arm)" <robh@kernel.org>
To: Sean Nyekjaer <sean@geanix.com>
Cc: Conor Dooley <conor+dt@kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Vincent Mailhol <mailhol.vincent@wanadoo.fr>,
linux-can@vger.kernel.org, Marc Kleine-Budde <mkl@pengutronix.de>,
Paolo Abeni <pabeni@redhat.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Eric Dumazet <edumazet@google.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH can-next v5 1/2] dt-bindings: can: tcan4x5x: Document the ti,nwkrq-voltage-vio option
Date: Fri, 15 Nov 2024 11:37:55 -0600 [thread overview]
Message-ID: <173169227528.3443207.4824174918630075657.robh@kernel.org> (raw)
In-Reply-To: <20241114-tcan-wkrqv-v5-1-a2d50833ed71@geanix.com>
On Thu, 14 Nov 2024 10:14:49 +0100, Sean Nyekjaer wrote:
> The nWKRQ pin supports an output voltage of either the internal reference
> voltage (3.6V) or the reference voltage of
> the digital interface 0-6V (VIO).
> Add the devicetree option ti,nwkrq-voltage-vio to set it to VIO.
>
> If this property is omitted the reset default, the internal reference
> voltage, is used.
>
> Signed-off-by: Sean Nyekjaer <sean@geanix.com>
> ---
> Documentation/devicetree/bindings/net/can/ti,tcan4x5x.yaml | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2024-11-15 17:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 9:14 [PATCH can-next v5 0/2] can: tcan4x5x: add option for selecting nWKRQ voltage Sean Nyekjaer
2024-11-14 9:14 ` [PATCH can-next v5 1/2] dt-bindings: can: tcan4x5x: Document the ti,nwkrq-voltage-vio option Sean Nyekjaer
2024-11-15 17:37 ` Rob Herring (Arm) [this message]
2024-11-14 9:14 ` [PATCH can-next v5 2/2] can: tcan4x5x: add option for selecting nWKRQ voltage Sean Nyekjaer
2024-11-18 15:05 ` Sean Nyekjaer
2024-11-18 15:14 ` Marc Kleine-Budde
2025-01-03 12:32 ` Sean Nyekjaer
2024-11-18 8:55 ` [PATCH can-next v5 0/2] " Marc Kleine-Budde
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=173169227528.3443207.4824174918630075657.robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=mkl@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=sean@geanix.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®