From: <piergiorgio.beruto@gmail.com>
To: <netdev@vger.kernel.org>
Subject: Adding IEEE802.3cg Clause 148 PLCA support to Linux
Date: Sat, 5 Nov 2022 18:42:10 +0100 [thread overview]
Message-ID: <026701d8f13d$ef0c2800$cd247800$@gmail.com> (raw)
Hello,
I would like to add IEEE 802.3cg-2019 PLCA support to Linux.
PLCA (Physical Layer Collision Avoidance) is an enhanced media-access protocol for multi-drop networks, and it is currently specified for the 10BASE-T1S PHY defined in Clause 147 of the same standard.
This feature is fully integrated into PHY and MACPHY implementations such as the onsemi NCN26010 and Microchip LAN867x, which are available on the market.
And, I am the inventor of the PLCA protocol 😊.
I am writing here because I am seeking advice on what is the best way forward.
In practice, what we need to do is configuring some additional parameters of the PHY: PLCA ID, TO_TIMER, NODE_COUNT, BURST.
The PHY registers for PLCA configuration are further documented in the OPEN alliance SIG public specifications (see https://www.opensig.org/about/specifications/ -> PLCA Management Registers)
The parameters I mentioned has to be configured dynamically. Therefore, I think we should not use module parameters or static DT configurations.
Based on my personal experience, It looks to me that extending ethtool is the way to go. Maybe we should consider those as “tunables”?
I am really interested to hear the opinion of the relevant Linux network experts on this topic.
Kind Regards,
Piergiorgio
next reply other threads:[~2022-11-05 17:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-05 17:42 piergiorgio.beruto [this message]
2022-11-05 23:40 ` Adding IEEE802.3cg Clause 148 PLCA support to Linux Andrew Lunn
2022-11-06 1:39 ` piergiorgio.beruto
2022-11-06 17:08 ` Andrew Lunn
2022-11-06 18:11 ` piergiorgio.beruto
2022-11-06 19:05 ` Andrew Lunn
2022-11-07 12:32 ` Oleksij Rempel
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='026701d8f13d$ef0c2800$cd247800$@gmail.com' \
--to=piergiorgio.beruto@gmail.com \
--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).