From: Conor Dooley <conor@kernel.org>
To: Luke Howard <lukeh@padl.com>
Cc: netdev@vger.kernel.org, Kieran Tyrrell <kieran@sienda.com>,
Max Hunter <max@huntershome.org>,
Cedric Jehasse <cedric.jehasse@luminex.be>,
Andrew Lunn <andrew@lunn.ch>, Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 6/6] dt-bindings: net: dsa: mv88e6xxx: add mv88e6xxx-avb-mode property
Date: Wed, 27 May 2026 16:04:16 +0100 [thread overview]
Message-ID: <20260527-supplier-lively-a2b353dbd9ec@spud> (raw)
In-Reply-To: <f0a4fc5e6918040b2c9a72da46a8cdcb43ed5049.1779841530.git.lukeh@padl.com>
[-- Attachment #1: Type: text/plain, Size: 2570 bytes --]
On Wed, May 27, 2026 at 10:42:52AM +1000, Luke Howard wrote:
> 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 | 26 +++++++++++++++++++
> 1 file changed, 26 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/net/dsa/marvell,mv88e6xxx.yaml b/Documentation/devicetree/bindings/net/dsa/marvell,mv88e6xxx.yaml
> index 19ae600e93394..1a01810e7682c 100644
> --- a/Documentation/devicetree/bindings/net/dsa/marvell,mv88e6xxx.yaml
> +++ b/Documentation/devicetree/bindings/net/dsa/marvell,mv88e6xxx.yaml
> @@ -97,6 +97,32 @@ properties:
> required:
> - compatible
>
> + marvell,mv88e6xxx-avb-mode:
"marvell,avb-mode" should be sufficient here.
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description:
> + Marvell MV88E6xxx switches that support Audio Video Bridging /
> + Time-Sensitive Networking (AVB/TSN) traffic prioritization can have
> + ports configured in one of several modes. These modes control the
> + handling of frames with non-AVB frame priorities and destination
> + addresses.
I've got no idea if this is a valid thing to make a property for, but I
really don't like this things being integers when there's some pretty
clear strings you could use instead: standard, enhanced and secure.
Also, you're missing a default, which is required for optional
properties.
Cheers,
Conor.
pw-bot: changes-requested
> + oneOf:
> + - description:
> + Standard Mode. Frames whose priority is mapped to an AVB
> + traffic class (TC) are considered AVB frames; other frames are
> + considered legacy (non-AVB).
> + const: 0
> + - description:
> + Enhanced Mode. Frames whose priority is mapped to an AVB TC
> + and for which a static FDB or MDB entry exists are considered
> + AVB frames. Frames with an AVB TC but no matching FDB or MDB
> + entry are dropped. AVB MDB entries can be added using the
> + MDB_FLAGS_STREAM_RESERVED netlink flag.
> + const: 1
> + - description:
> + Secure Mode. As Enhanced Mode, but the matching FDB or MDB
> + entry must also have the source port's bit set.
> + const: 2
> +
> allOf:
> - $ref: dsa.yaml#/$defs/ethernet-ports
>
> --
> 2.43.0
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-05-27 15:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1779841530.git.lukeh@padl.com>
2026-05-27 0:42 ` [PATCH net-next 6/6] dt-bindings: net: dsa: mv88e6xxx: add mv88e6xxx-avb-mode property Luke Howard
2026-05-27 15:04 ` Conor Dooley [this message]
2026-05-30 0:49 ` sashiko-bot
2026-05-30 2:01 ` Luke Howard
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=20260527-supplier-lively-a2b353dbd9ec@spud \
--to=conor@kernel.org \
--cc=andrew@lunn.ch \
--cc=cedric.jehasse@luminex.be \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=kieran@sienda.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukeh@padl.com \
--cc=max@huntershome.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=robh@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