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

[Ryder Lee]

On Wed, 2026-02-11 at 10:08 +0100, Krzysztof Kozlowski wrote:
> On 11/02/2026 09:59, Ryder Lee wrote:
> > 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
> 
> I do not see there anything like you wrote here. You just list all of
> them, no device constraints.
> 
> Best regards,
> Krzysztof
> 

The original schema is a broad description. Now a reviewer want me to
describe the differences for various connected devices, but I don’t
know how to add a compatible string for PCIe, USB, or even SDIO devices
for their constraints. So I used the driver’s generation name... can I
just write “mt7996”? Or do I need a complete and meaningful compatible
string?

Or maybe there’s no need to change the documentation at all and just
let the driver handle it, so we don’t have to discuss these details.

Ryder