From: Oliver Hartkopp <socketcan@hartkopp.net>
To: linux-can@vger.kernel.org
Cc: Oliver Hartkopp <socketcan@hartkopp.net>
Subject: [RFC PATCH v2 4/4] can: canxl: support CAN XL transceiver switching in data phase
Date: Wed, 4 Dec 2024 08:57:03 +0100 [thread overview]
Message-ID: <20241204075703.3699-4-socketcan@hartkopp.net> (raw)
In-Reply-To: <20241204075703.3699-1-socketcan@hartkopp.net>
In the CAN XL data phase the CAN XL controller can advise the CAN XL
transceiver to switch the physical layer.
To enable this feature the CAN_CTRLMODE_XL_TRX has to be set in the
driver control mode.
Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net>
---
include/uapi/linux/can/netlink.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/uapi/linux/can/netlink.h b/include/uapi/linux/can/netlink.h
index 55b8374ab094..652576234f63 100644
--- a/include/uapi/linux/can/netlink.h
+++ b/include/uapi/linux/can/netlink.h
@@ -105,10 +105,11 @@ struct can_ctrlmode {
#define CAN_CTRLMODE_TDC_MANUAL 0x400 /* FD TDCV is manually set up by user */
#define CAN_CTRLMODE_XL 0x800 /* CAN XL mode */
#define CAN_CTRLMODE_XL_TDC_AUTO 0x1000 /* XL transceiver automatically calculates TDCV */
#define CAN_CTRLMODE_XL_TDC_MANUAL 0x2000 /* XL TDCV is manually set up by user */
#define CAN_CTRLMODE_XL_RRS 0x4000 /* XL enable RRS bit access */
+#define CAN_CTRLMODE_XL_TRX 0x8000 /* XL switch trx in data phase */
/*
* CAN device statistics
*/
struct can_device_stats {
--
2.45.2
prev parent reply other threads:[~2024-12-04 7:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 7:57 [RFC PATCH v2 1/4] can xl dummy driver from Vincent Oliver Hartkopp
2024-12-04 7:57 ` [RFC PATCH v2 2/4] add CAN XL support RFC based on Vicents cleanups Oliver Hartkopp
2024-12-04 7:57 ` [RFC PATCH v2 3/4] can: canxl: support Remote Request Substitution bit access Oliver Hartkopp
2024-12-04 7:57 ` Oliver Hartkopp [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=20241204075703.3699-4-socketcan@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
/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