All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: linux-can@vger.kernel.org
Cc: Oliver Hartkopp <socketcan@hartkopp.net>,
	Vincent Mailhol <mailhol.vincent@wanadoo.fr>,
	Marc Kleine-Budde <mkl@pengutronix.de>
Subject: [net-next v2 09/15] can: length: canfd_sanitize_len(): add function to sanitize CAN-FD data length
Date: Mon, 11 Jan 2021 11:45:23 +0100	[thread overview]
Message-ID: <20210111104529.657057-10-mkl@pengutronix.de> (raw)
In-Reply-To: <20210111104529.657057-1-mkl@pengutronix.de>

The data field in CAN-FD frames have specifig frame length (0, 1, 2, 3, 4, 5,
6, 7, 8, 12, 16, 20, 24, 32, 48, 64). This function "rounds" up a given length
to the next valid CAN-FD frame length.

Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
---
 include/linux/can/length.h | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/include/linux/can/length.h b/include/linux/can/length.h
index 156b9d17969a..b2313b2a0b02 100644
--- a/include/linux/can/length.h
+++ b/include/linux/can/length.h
@@ -45,4 +45,10 @@ u8 can_fd_dlc2len(u8 dlc);
 /* map the sanitized data length to an appropriate data length code */
 u8 can_fd_len2dlc(u8 len);
 
+/* map the data length to an appropriate data link layer length */
+static inline u8 canfd_sanitize_len(u8 len)
+{
+	return can_fd_dlc2len(can_fd_len2dlc(len));
+}
+
 #endif /* !_CAN_LENGTH_H */
-- 
2.29.2



  parent reply	other threads:[~2021-01-11 10:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-11 10:45 [net-next v2 00/15] can: dev: cleanup and add CAN frame length handling support Marc Kleine-Budde
2021-01-11 10:45 ` [net-next v2 01/15] MAINTAINERS: CAN network layer: add missing header file can-ml.h Marc Kleine-Budde
2021-01-11 10:45 ` [net-next v2 02/15] can: dev: move driver related infrastructure into separate subdir Marc Kleine-Budde
2021-01-11 10:45 ` [net-next v2 03/15] can: dev: move bittiming related code into seperate file Marc Kleine-Budde
2021-01-11 10:45 ` [net-next v2 04/15] can: dev: move length " Marc Kleine-Budde
2021-01-11 10:45 ` [net-next v2 05/15] can: dev: move skb related " Marc Kleine-Budde
2021-01-11 12:51   ` Vincent MAILHOL
2021-01-11 14:20     ` Marc Kleine-Budde
2021-01-11 15:27       ` Vincent MAILHOL
2021-01-11 10:45 ` [net-next v2 06/15] can: dev: move netlink related code " Marc Kleine-Budde
2021-01-11 10:45 ` [net-next v2 07/15] can: length: convert to kernel coding style Marc Kleine-Budde
2021-01-11 10:45 ` [net-next v2 08/15] can: length: can_fd_len2dlc(): simplify length calculcation Marc Kleine-Budde
2021-01-11 10:45 ` Marc Kleine-Budde [this message]
2021-01-11 10:45 ` [net-next v2 10/15] can: length: can_skb_get_frame_len(): introduce function to get data length of frame in data link layer Marc Kleine-Budde
2021-01-11 13:11   ` Vincent MAILHOL
2021-01-11 10:45 ` [net-next v2 11/15] can: dev: extend struct can_skb_priv to hold CAN frame length Marc Kleine-Budde
2021-01-11 10:45 ` [net-next v2 12/15] can: dev: can_put_echo_skb(): extend to handle frame_len Marc Kleine-Budde
2021-01-11 10:45 ` [net-next v2 13/15] can: dev: can_get_echo_skb(): extend to return can frame length Marc Kleine-Budde
2021-01-11 10:45 ` [net-next v2 14/15] can: dev: can_rx_offload_get_echo_skb(): " Marc Kleine-Budde
2021-01-11 10:45 ` [net-next v2 15/15] can: dev: add software tx timestamps Marc Kleine-Budde
2021-01-11 12:56   ` Vincent MAILHOL

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=20210111104529.657057-10-mkl@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=linux-can@vger.kernel.org \
    --cc=mailhol.vincent@wanadoo.fr \
    --cc=socketcan@hartkopp.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.