[PATCH v3 2/2] dt-bindings: net: wireless: mt76: clarify backoff limit format

[Ryder Lee]

On Wed, 2026-02-11 at 09:41 +0100, Krzysztof Kozlowski wrote:
> On 11/02/2026 09:33, Ryder Lee wrote:
> > > > > Why this cannot be a schema?
> > > > > 
> > > > > 
> > > > Well, actually, it's already a schema. This is just an expanded
> > > 
> > > Where exactly?
> > > 
> > 
> > How 1T1ss is used across different generations is what my example
> > above
> > was talking about.
> 
> Where exactly it is already a schema? Please point me line encoding
> this.
> 
> 
line 243 paths-ru
line 261 paths-ru-bf

1T1ss refers to the second row in the example below

Previously, we were mainly discussing how the driver should handle
parsing 0 versus non-zero cases, but this can be fully managed by the
driver itself. My [1/2] patch already explains this clearly.

paths-ru-bf =
<1 20 22 38 36 24 30 23 21 28 29>,
<1 20 39 31 25 26 25 28 30 39 39>,
<1 37 34 26 26 25 21 34 23 34 24>,
<1 0 20 23 31 23 30 39 28 29 36>,
<1 0 27 34 33 34 29 38 33 33 22>,
<1 0 30 23 39 28 21 25 29 28 21>,
<1 0 34 20 38 32 35 33 37 26 36>;

Whether the DTS needs to interpret it is really up to personal
preference. Personally, I don’t think it’s needed but I respect
everyone's opinion.

Our newer IC generations are only going to get more complex. If we
hardcode too many definitions now, you’ll end up having to change them
repeatedly. It’s better to let the driver handle this logic.

Ryder