public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, linux-can@vger.kernel.org,
	kernel@pengutronix.de,
	Viken Dadhaniya <viken.dadhaniya@oss.qualcomm.com>,
	Conor Dooley <conor.dooley@microchip.com>,
	Marc Kleine-Budde <mkl@pengutronix.de>
Subject: [PATCH net-next 1/6] dt-bindings: can: mcp251xfd: add microchip,xstbyen property
Date: Wed,  1 Apr 2026 09:30:09 +0200	[thread overview]
Message-ID: <20260401073338.5592-2-mkl@pengutronix.de> (raw)
In-Reply-To: <20260401073338.5592-1-mkl@pengutronix.de>

From: Viken Dadhaniya <viken.dadhaniya@oss.qualcomm.com>

Add the boolean property 'microchip,xstbyen' to enable the dedicated
transceiver standby control function on the INT0/GPIO0/XSTBY pin of
the MCP251xFD family.

Signed-off-by: Viken Dadhaniya <viken.dadhaniya@oss.qualcomm.com>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
Link: https://patch.msgid.link/20260321135031.3107408-2-viken.dadhaniya@oss.qualcomm.com
Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
---
 .../devicetree/bindings/net/can/microchip,mcp251xfd.yaml  | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/Documentation/devicetree/bindings/net/can/microchip,mcp251xfd.yaml b/Documentation/devicetree/bindings/net/can/microchip,mcp251xfd.yaml
index 2d13638ebc6a..28e494262cd9 100644
--- a/Documentation/devicetree/bindings/net/can/microchip,mcp251xfd.yaml
+++ b/Documentation/devicetree/bindings/net/can/microchip,mcp251xfd.yaml
@@ -44,6 +44,14 @@ properties:
       signals a pending RX interrupt.
     maxItems: 1
 
+  microchip,xstbyen:
+    type: boolean
+    description:
+      If present, configure the INT0/GPIO0/XSTBY pin as transceiver standby
+      control. The pin is driven low when the controller is active and high
+      when it enters Sleep mode, allowing automatic standby control of an
+      external CAN transceiver connected to this pin.
+
   spi-max-frequency:
     description:
       Must be half or less of "clocks" frequency.

base-commit: f1359c240191e686614847905fc861cbda480b47
-- 
2.53.0


  reply	other threads:[~2026-04-01  7:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-01  7:30 [PATCH net-next 0/6] pull-request: can-next 2026-04-01 Marc Kleine-Budde
2026-04-01  7:30 ` Marc Kleine-Budde [this message]
2026-04-02  2:30   ` [PATCH net-next 1/6] dt-bindings: can: mcp251xfd: add microchip,xstbyen property patchwork-bot+netdevbpf
2026-04-01  7:30 ` [PATCH net-next 2/6] net: can: ctucanfd: remove useless copy of PCI_DEVICE_DATA macro Marc Kleine-Budde
2026-04-01  7:30 ` [PATCH net-next 3/6] can: kvaser_usb: leaf: refactor endpoint lookup Marc Kleine-Budde
2026-04-01  7:30 ` [PATCH net-next 4/6] can: mcp251xfd: add support for XSTBYEN transceiver standby control Marc Kleine-Budde
2026-04-01  7:30 ` [PATCH net-next 5/6] can: rcar_can: Convert to FIELD_MODIFY() Marc Kleine-Budde
2026-04-01  7:30 ` [PATCH net-next 6/6] can: ucan: refactor endpoint lookup 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=20260401073338.5592-2-mkl@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=conor.dooley@microchip.com \
    --cc=davem@davemloft.net \
    --cc=kernel@pengutronix.de \
    --cc=kuba@kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=viken.dadhaniya@oss.qualcomm.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