[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20251203-canxl-netlink-v3-3-999f38fae8c2@kernel.org>
Date: Wed, 03 Dec 2025 19:24:30 +0100
From: Vincent Mailhol <mailhol@...nel.org>
To: netdev@...r.kernel.org, Stephen Hemminger <stephen@...workplumber.org>,
Marc Kleine-Budde <mkl@...gutronix.de>,
Oliver Hartkopp <socketcan@...tkopp.net>, David Ahern <dsahern@...nel.org>
Cc: Rakuram Eswaran <rakuram.e96@...il.com>,
Stéphane Grosjean <stephane.grosjean@...e.fr>,
linux-kernel@...r.kernel.org, linux-can@...r.kernel.org,
Vincent Mailhol <mailhol@...nel.org>
Subject: [PATCH iproute2-next v3 3/7] iplink_can: print_usage: describe the
CAN bittiming units
While the meaning of "bps" or "ns" may be relatively easy to understand,
some of the CAN specific units such as "mtq" (minimum time quanta) may be
harder to understand.
Add a new paragraph to the help menu which describes all the different
units used for the CAN bittiming parameters.
Signed-off-by: Vincent Mailhol <mailhol@...nel.org>
---
Changelog
v1 -> v2:
- "s/milli second/millisecond/g" and "s/nano second/nanosecond/g"
---
ip/iplink_can.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/ip/iplink_can.c b/ip/iplink_can.c
index ee27659c..d5abc43a 100644
--- a/ip/iplink_can.c
+++ b/ip/iplink_can.c
@@ -60,6 +60,13 @@ static void print_usage(FILE *f)
"\t TDCO := { NUMBER in mtq }\n"
"\t TDCF := { NUMBER in mtq }\n"
"\t RESTART-MS := { 0 | NUMBER in ms }\n"
+ "\n"
+ "\tUnits:\n"
+ "\t bps := bit per second\n"
+ "\t ms := millisecond\n"
+ "\t mtq := minimum time quanta\n"
+ "\t ns := nanosecond\n"
+ "\t tq := time quanta\n"
);
}
--
2.51.2
Powered by blists - more mailing lists