All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Fritz <christoph.fritz@hexdev.de>
To: Oliver Hartkopp <socketcan@hartkopp.net>,
	Pavel Pisa <pisa@cmp.felk.cvut.cz>,
	Richard Weinberger <richard@nod.at>,
	Andreas Lauser <andreas.lauser@mbition.io>,
	Wolfgang Grandegger <wg@grandegger.com>,
	Marc Kleine-Budde <mkl@pengutronix.de>,
	"David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Jonathan Corbet <corbet@lwn.net>
Cc: linux-can@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [RFC][PATCH 0/2] LIN support for Linux
Date: Sun, 27 Nov 2022 20:02:42 +0100	[thread overview]
Message-ID: <20221127190244.888414-1-christoph.fritz@hexdev.de> (raw)

The intention of this series is to kick off a discussion about how to
support LIN (ISO 17987) [0] in Linux.

This series consist of two patches which are two individual proposals
for adding LIN abstraction into the kernel.

One approach is to add LIN ontop of CANFD:
  [RFC] can: introduce LIN abstraction

The other approach is adding a new type of CAN-socket:
  [RFC] can: Add LIN proto skeleton

These patches are abstracting LIN so that actual device drivers can
make use of it.

For reference, the LIN-ontop-of-CANFD variant already has a device
driver using it (not part of this series). It is a specially built USB
LIN-BUS adapter hardware called hexLIN [1].  Its purpose is mainly to
test, adapt and discuss different LIN APIs for mainline Linux kernel.
But it can already be used productively as a Linux LIN node in
controller (master) and responder (slave) mode. By sysfs, hexLIN
supports different checksum calculations and setting up a
responder-table.

For more info about hexLIN, see link below [1].

We are looking for partners with Linux based LIN projects for funding. 

[0]: https://en.wikipedia.org/wiki/Local_Interconnect_Network
[1]: https://hexdev.de/hexlin/

Christoph Fritz (1):
  [RFC] can: Introduce LIN bus as CANFD abstraction

Richard Weinberger (1):
  [RFC] can: Add LIN proto skeleton

 drivers/net/can/Kconfig          |  10 ++
 drivers/net/can/Makefile         |   1 +
 drivers/net/can/lin.c            | 181 +++++++++++++++++++++++++++
 include/net/lin.h                |  30 +++++
 include/uapi/linux/can.h         |   8 +-
 include/uapi/linux/can/lin.h     |  15 +++
 include/uapi/linux/can/netlink.h |   1 +
 net/can/Kconfig                  |   5 +
 net/can/Makefile                 |   3 +
 net/can/lin.c                    | 207 +++++++++++++++++++++++++++++++
 10 files changed, 460 insertions(+), 1 deletion(-)
 create mode 100644 drivers/net/can/lin.c
 create mode 100644 include/net/lin.h
 create mode 100644 include/uapi/linux/can/lin.h
 create mode 100644 net/can/lin.c

-- 
2.30.2


             reply	other threads:[~2022-11-27 19:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-27 19:02 Christoph Fritz [this message]
2022-11-27 19:02 ` [PATCH 1/2] [RFC] can: Introduce LIN bus as CANFD abstraction Christoph Fritz
2022-11-27 19:02 ` [PATCH 2/2] [RFC] can: Add LIN proto skeleton Christoph Fritz
2022-11-27 21:16   ` kernel test robot
2022-11-27 22:27   ` kernel test robot
2022-11-27 22:57   ` kernel test robot
2022-11-27 23:28   ` kernel test robot
2022-11-28  8:21 ` [RFC][PATCH 0/2] LIN support for Linux Oliver Hartkopp
2022-11-28 10:16   ` Christoph Fritz
2022-11-28 14:49     ` Pavel Pisa
2022-11-28 17:02       ` Ryan Edwards
2022-11-28 17:52         ` Pavel Pisa
2022-11-28 18:47           ` Ryan Edwards
2022-11-28 21:48             ` Christoph Fritz
2022-11-28 22:47               ` Andrew Lunn
2022-11-30 21:02     ` 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=20221127190244.888414-1-christoph.fritz@hexdev.de \
    --to=christoph.fritz@hexdev.de \
    --cc=andreas.lauser@mbition.io \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pisa@cmp.felk.cvut.cz \
    --cc=richard@nod.at \
    --cc=socketcan@hartkopp.net \
    --cc=wg@grandegger.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 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.