public inbox for linux-can@vger.kernel.org
 help / color / mirror / Atom feed
From: Francesco Valla <francesco@valla.it>
To: linux-can@vger.kernel.org
Subject: [QUESTION] How to support partial networking
Date: Wed, 14 Jan 2026 22:26:39 +0100	[thread overview]
Message-ID: <aWgKD8AG-C9YlFRe@bywater> (raw)

Hello linux-can,

I am starting to develop a driver for the TJA1465 SIC CAN transceiver
from NXP [0], which among other things supports partial networking, and
I was wondering whether it has already been discussed or not how to
support such a feature.

For those not familiar, partial networking is an automotive-oriented
feature that allows to wake-up selectively through CAN traffic some ECUs
while leaving others in a quiescent state. This can be used for example
for periodic maintenance tasks, diagnostics or updates. It is typically
implemented inside a trasceiver, which is always powered and stores in
a volatile memory a list of CAN IDs (plus masks, much like the SocketCAN
filtering works) that shall lead to the wake-up of the ECU.

In the context of the Linux kernel, this can be probably be implemented
in a number of ways:

 - as a device-specifc capability (accessible e.g. through sysfs)
 - at phy level
 - in the generic CAN subsystem
 - ?

I did not find a previous discussion neither in the mailing list nor in
public presentations, but maybe some discussion already took place
privately or I missed something.

Any idea or preference? If not, I'll try to come up with a proposal and
submit an RFC.

[0] https://www.nxp.com/products/TJA1465

Thank you in advance!

Regards,
Francesco


             reply	other threads:[~2026-01-14 21:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-14 21:26 Francesco Valla [this message]
2026-01-15 14:58 ` [QUESTION] How to support partial networking Marc Kleine-Budde

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=aWgKD8AG-C9YlFRe@bywater \
    --to=francesco@valla.it \
    --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