All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryder Lee <Ryder.Lee@mediatek.com>
To: "wenst@chromium.org" <wenst@chromium.org>
Cc: "robh@kernel.org" <robh@kernel.org>,
	"nbd@nbd.name" <nbd@nbd.name>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"Allen Ye (葉芷勳)" <Allen.Ye@mediatek.com>,
	"krzk@kernel.org" <krzk@kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v3 2/2] dt-bindings: net: wireless: mt76: clarify backoff limit format
Date: Wed, 11 Feb 2026 09:07:57 +0000	[thread overview]
Message-ID: <622c89592f5fdc7fb8547c3cd9ed66cc63c3cf92.camel@mediatek.com> (raw)
In-Reply-To: <CAGXv+5EY=8Xta4OdnS9Skjx3Ls3ZnW7oNS38cK1Ch=wL6JJJ0g@mail.gmail.com>

On Wed, 2026-02-11 at 17:01 +0800, Chen-Yu Tsai wrote:
> On Wed, Feb 11, 2026 at 4:41 PM Krzysztof Kozlowski <krzk@kernel.org>
> 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.
> 
> I think what Krzysztof is asking is why can't you have different
> compatible
> strings for each generation (connac, connac2, connac3), and then have
> conditionals in this document to describe in proper DT schema, not
> text,
> the length requirements of each property for each generation.
> 
> 
> ChenYu
> 

Oh, so this is exactly my original question: how do I describe a PCIe
device in the platform binding when there is no compatible string for
it (a NIC card)?

Ryder

      reply	other threads:[~2026-02-11  9:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-10 18:08 [PATCH v3 1/2] wifi: mt76: fix backoff fields and max_power calculation Ryder Lee
2026-02-10 18:08 ` [PATCH v3 2/2] dt-bindings: net: wireless: mt76: clarify backoff limit format Ryder Lee
2026-02-10 18:12   ` Ryder Lee
2026-02-10 18:16     ` Ryder Lee
2026-02-11  6:31   ` Krzysztof Kozlowski
2026-02-11  8:13     ` Ryder Lee
2026-02-11  8:16       ` Krzysztof Kozlowski
2026-02-11  8:33         ` Ryder Lee
2026-02-11  8:41           ` Krzysztof Kozlowski
2026-02-11  8:59             ` Ryder Lee
2026-02-11  9:08               ` Krzysztof Kozlowski
2026-02-11  9:19                 ` Ryder Lee
2026-02-11  9:35                   ` Ryder Lee
2026-02-11  9:52                   ` Chen-Yu Tsai
2026-02-11 16:26                     ` Ryder Lee
2026-02-11  9:01             ` Chen-Yu Tsai
2026-02-11  9:07               ` Ryder Lee [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=622c89592f5fdc7fb8547c3cd9ed66cc63c3cf92.camel@mediatek.com \
    --to=ryder.lee@mediatek.com \
    --cc=Allen.Ye@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nbd@nbd.name \
    --cc=robh@kernel.org \
    --cc=wenst@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.