Netdev List
 help / color / mirror / Atom feed
From: Luke Howard <lukeh@padl.com>
To: netdev@vger.kernel.org
Cc: andrew@lunn.ch, vladimir.oltean@nxp.com, kieran@sienda.com,
	jcschroeder@gmail.com, max@huntershome.org,
	Luke Howard <lukeh@padl.com>
Subject: [RFC net-next 5/5] dt-bindings: net: dsa: mv88e6xxx: add mv88e6xxx-avb-mode property
Date: Sat, 27 Sep 2025 17:07:08 +1000	[thread overview]
Message-ID: <20250927070724.734933-6-lukeh@padl.com> (raw)
In-Reply-To: <20250927070724.734933-1-lukeh@padl.com>

Add the vendor-specific marvell,mv88e6xxx-avb-mode property for adding
stricter handling of frames with non-AVB frame priorities and destination
addresses.

Signed-off-by: Luke Howard <lukeh@padl.com>
---
 .../bindings/net/dsa/marvell,mv88e6xxx.yaml   | 25 +++++++++++++++++++
 1 file changed, 25 insertions(+)

diff --git a/Documentation/devicetree/bindings/net/dsa/marvell,mv88e6xxx.yaml b/Documentation/devicetree/bindings/net/dsa/marvell,mv88e6xxx.yaml
index 19f15bdd1c976..33d0cf5f21d5b 100644
--- a/Documentation/devicetree/bindings/net/dsa/marvell,mv88e6xxx.yaml
+++ b/Documentation/devicetree/bindings/net/dsa/marvell,mv88e6xxx.yaml
@@ -97,6 +97,31 @@ properties:
     required:
       - compatible
 
+  marvell,mv88e6xxx-avb-mode:
+    description: Marvell MV88E6xxx that support Audio Video Bridging/Time
+      Sensitive Networking (AVB/TSN) traffic prioritization can have ports
+      ports configured in one of several modes. These modes control the
+      handling of frames with non-AVB frame priorities and destination
+      addresses.
+    oneOf:
+      - enum:
+          - 0
+          - 1
+          - 2
+      - description: |
+        0: Standard Mode: frames with a priority that is mapped to an AVB
+           traffic class (TC) are considered as AVB frames. Others frames
+           are considered Legacy (non-AVB).
+        1: Enhanced: frames with a priority that is mapped to an AVB TC
+           and for which there is a static FDB or MDB entry are
+           considered as AVB frames. Those with an AVB TC but no FDB or
+	   MDB entry will be dropped. To avoid conflict with other multicast
+           protocols, only AVTP (91:e0:f0) destination addresses are
+           considered to be AVB multicast addresses.
+        2: Secure: as for Enhanced, but also require the FDB or MDB entry
+           to have its source port's bit set to one. In this mode, all
+	   frames with an AVTP destination address must be valid AVB frames.
+
 allOf:
   - $ref: dsa.yaml#/$defs/ethernet-ports
 
-- 
2.43.0


      parent reply	other threads:[~2025-09-27  7:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-27  7:07 [RFC net-next 0/5] net: dsa: mv88e6xxx: support for 802.1Qav Luke Howard
2025-09-27  7:07 ` [RFC net-next 1/5] net: dsa: mv88e6xxx: add num_tx_queues to chip info structure Luke Howard
2025-09-27  7:07 ` [RFC net-next 2/5] net: dsa: mv88e6xxx: add MV88E6XXX_G1_ATU_CTL_MAC_AVB setter Luke Howard
2025-09-27 14:29   ` Andrew Lunn
2025-09-27  7:07 ` [RFC net-next 3/5] net: dsa: mv88e6xxx: MQPRIO support Luke Howard
2025-09-27 15:12   ` Andrew Lunn
2025-09-27 16:00     ` Luke Howard
2025-09-27 17:36       ` Andrew Lunn
2025-09-27 18:14         ` Luke Howard
2026-05-26  7:05           ` Luke Howard
2025-09-27  7:07 ` [RFC net-next 4/5] net: dsa: mv88e6xxx: CBS support Luke Howard
2025-09-27  7:07 ` Luke Howard [this message]

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=20250927070724.734933-6-lukeh@padl.com \
    --to=lukeh@padl.com \
    --cc=andrew@lunn.ch \
    --cc=jcschroeder@gmail.com \
    --cc=kieran@sienda.com \
    --cc=max@huntershome.org \
    --cc=netdev@vger.kernel.org \
    --cc=vladimir.oltean@nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox