From: Oliver Hartkopp <socketcan@hartkopp.net>
To: linux-can@vger.kernel.org, mkl@pengutronix.de,
mailhol.vincent@wanadoo.fr
Cc: netdev@vger.kernel.org, Oliver Hartkopp <socketcan@hartkopp.net>
Subject: [PATCH v6 0/8] Introduce optional DLC element for Classic CAN
Date: Tue, 10 Nov 2020 11:18:44 +0100 [thread overview]
Message-ID: <20201110101852.1973-1-socketcan@hartkopp.net> (raw)
Introduce improved DLC handling for Classic CAN with introduces a new
element 'len8_dlc' to the struct can_frame and additionally rename
the 'can_dlc' element to 'len' as it represents a plain payload length.
Before implementing the CAN_CTRLMODE_CC_LEN8_DLC handling on driver level
this patch set cleans up and renames the relevant code.
No functional changes.
This patch set is based on kernel/git/netdev/net-next.git
Changes in v2:
- rephrase commit message of patch 4 about can_dlc replacement
Changes in v3:
- remove unnecessarily introduced u8 cast in flexcan.c
Changes in v4:
- adopt phrasing suggestions from Vincent Mailhol
- separate and extend CAN documentation (Documentation/networking/can.rst)
- add new patches for len8_dlc handling for CAN drivers
- add new helpers in include/linux/can/dev.h
- add len8_dlc support for various CAN USB adapters as reference
Changes in v5:
- rename CAN FD related can_len2dlc and can_dlc2len helpers so that they
fit to the renamed can_cc_dlc2len helper for Classical CAN
(suggested by Vincent Mailhol)
Changes in v6: (only patch 7 & 8)
- rework helpers to access Classical CAN DLC values
- move CAN_CTRLMODE_CC_LEN8_DLC at the end of ctrlmode_supported defs
Oliver Hartkopp (8):
can: add optional DLC element to Classical CAN frame structure
can: rename get_can_dlc() macro with can_cc_dlc2len()
can: remove obsolete get_canfd_dlc() macro
can: replace can_dlc as variable/element for payload length
can: rename CAN FD related can_len2dlc and can_dlc2len helpers
can: update documentation for DLC usage in Classical CAN
can-dev: introduce helpers to access Classical CAN DLC values
can-dev: add len8_dlc support for various CAN USB adapters
Documentation/networking/can.rst | 70 ++++++++++++++-----
drivers/net/can/at91_can.c | 14 ++--
drivers/net/can/c_can/c_can.c | 20 +++---
drivers/net/can/cc770/cc770.c | 14 ++--
drivers/net/can/dev.c | 16 ++---
drivers/net/can/flexcan.c | 6 +-
drivers/net/can/grcan.c | 10 +--
drivers/net/can/ifi_canfd/ifi_canfd.c | 10 +--
drivers/net/can/janz-ican3.c | 20 +++---
drivers/net/can/kvaser_pciefd.c | 10 +--
drivers/net/can/m_can/m_can.c | 12 ++--
drivers/net/can/mscan/mscan.c | 20 +++---
drivers/net/can/pch_can.c | 14 ++--
drivers/net/can/peak_canfd/peak_canfd.c | 16 ++---
drivers/net/can/rcar/rcar_can.c | 14 ++--
drivers/net/can/rcar/rcar_canfd.c | 12 ++--
drivers/net/can/rx-offload.c | 2 +-
drivers/net/can/sja1000/sja1000.c | 10 +--
drivers/net/can/slcan.c | 32 ++++-----
drivers/net/can/softing/softing_fw.c | 2 +-
drivers/net/can/softing/softing_main.c | 14 ++--
drivers/net/can/spi/hi311x.c | 20 +++---
drivers/net/can/spi/mcp251x.c | 20 +++---
.../net/can/spi/mcp251xfd/mcp251xfd-core.c | 10 +--
drivers/net/can/sun4i_can.c | 10 +--
drivers/net/can/ti_hecc.c | 8 +--
drivers/net/can/usb/ems_usb.c | 16 ++---
drivers/net/can/usb/esd_usb2.c | 16 ++---
drivers/net/can/usb/gs_usb.c | 17 ++---
.../net/can/usb/kvaser_usb/kvaser_usb_core.c | 2 +-
.../net/can/usb/kvaser_usb/kvaser_usb_hydra.c | 24 +++----
.../net/can/usb/kvaser_usb/kvaser_usb_leaf.c | 22 +++---
drivers/net/can/usb/mcba_usb.c | 10 +--
drivers/net/can/usb/peak_usb/pcan_usb.c | 18 ++---
drivers/net/can/usb/peak_usb/pcan_usb_fd.c | 29 +++++---
drivers/net/can/usb/peak_usb/pcan_usb_pro.c | 14 ++--
drivers/net/can/usb/ucan.c | 20 +++---
drivers/net/can/usb/usb_8dev.c | 20 +++---
drivers/net/can/xilinx_can.c | 16 ++---
include/linux/can/dev.h | 41 +++++++++--
include/linux/can/dev/peak_canfd.h | 2 +-
include/uapi/linux/can.h | 38 ++++++----
include/uapi/linux/can/netlink.h | 1 +
net/can/af_can.c | 2 +-
net/can/gw.c | 2 +-
net/can/j1939/main.c | 4 +-
46 files changed, 403 insertions(+), 317 deletions(-)
--
2.28.0
next reply other threads:[~2020-11-10 10:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 10:18 Oliver Hartkopp [this message]
2020-11-10 10:18 ` [PATCH v6 1/8] can: add optional DLC element to Classical CAN frame structure Oliver Hartkopp
2020-11-10 10:18 ` [PATCH v6 2/8] can: rename get_can_dlc() macro with can_cc_dlc2len() Oliver Hartkopp
2020-11-10 10:18 ` [PATCH v6 3/8] can: remove obsolete get_canfd_dlc() macro Oliver Hartkopp
2020-11-10 10:18 ` [PATCH v6 4/8] can: replace can_dlc as variable/element for payload length Oliver Hartkopp
2020-11-20 9:49 ` broken on next-next - " Oliver Hartkopp
2020-11-10 10:18 ` [PATCH v6 5/8] can: rename CAN FD related can_len2dlc and can_dlc2len helpers Oliver Hartkopp
2020-11-10 10:18 ` [PATCH v6 6/8] can: update documentation for DLC usage in Classical CAN Oliver Hartkopp
2020-11-10 10:18 ` [PATCH v6 7/8] can-dev: introduce helpers to access Classical CAN DLC values Oliver Hartkopp
2020-11-10 15:50 ` Marc Kleine-Budde
2020-11-10 17:00 ` Oliver Hartkopp
2020-11-10 10:18 ` [PATCH v6 8/8] can-dev: add len8_dlc support for various CAN USB adapters Oliver Hartkopp
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=20201110101852.1973-1-socketcan@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=mkl@pengutronix.de \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).