On Fri, Sep 13, 2024 at 04:15:05PM +0300, Vladimir Oltean wrote: > If we don't add something along these lines, it is absolutely impossible > to know, for trees with 3 or more switches, which links represent direct > connections and which don't. > > I've studied existing mainline device trees, and it seems that the rule > has been respected thus far. I've actually tested such a 3-switch setup > with the Turris MOX. What about out of tree (so in u-boot or the likes)? Are there other users that we need to care about? This doesn't really seem like an ABI change, if this is the established convention, but feels like a fixes tag and backports to stable etc are in order to me. > > Signed-off-by: Vladimir Oltean <vladimir.oltean@xxxxxxx> > --- > Documentation/devicetree/bindings/net/dsa/dsa-port.yaml | 9 +++++---- > 1 file changed, 5 insertions(+), 4 deletions(-) > > diff --git a/Documentation/devicetree/bindings/net/dsa/dsa-port.yaml b/Documentation/devicetree/bindings/net/dsa/dsa-port.yaml > index 480120469953..307c61aadcbc 100644 > --- a/Documentation/devicetree/bindings/net/dsa/dsa-port.yaml > +++ b/Documentation/devicetree/bindings/net/dsa/dsa-port.yaml > @@ -31,10 +31,11 @@ properties: > > link: > description: > - Should be a list of phandles to other switch's DSA port. This > - port is used as the outgoing port towards the phandle ports. The > - full routing information must be given, not just the one hop > - routes to neighbouring switches > + Should be a list of phandles to other switch's DSA port. This port is > + used as the outgoing port towards the phandle ports. In case of trees > + with more than 2 switches, the full routing information must be given. > + The first element of the list must be the directly connected DSA port > + of the adjacent switch. > $ref: /schemas/types.yaml#/definitions/phandle-array > items: > maxItems: 1 > -- > 2.34.1 >
Attachment:
signature.asc
Description: PGP signature
