Devicetree
 help / color / mirror / Atom feed
From: <amber.kao@ite.com.tw>
To: <krzk@kernel.org>, <ite_pd@ite.com.tw>
Cc: <jeson.yang@ite.com.tw>, <Yaode.Fang@ite.com.tw>,
	<gregkh@linuxfoundation.org>, <robh@kernel.org>,
	<krzk+dt@kernel.org>, <conor+dt@kernel.org>,
	<linux-usb@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] dt-bindings: usb: Add ITE IT5271/IT5272/IT5273/IT5274 support
Date: Mon, 7 Sep 2026 09:57:34 +0000	[thread overview]
Message-ID: <cc3a8a7133184decb06884d65c5f06c5@ite.com.tw> (raw)
In-Reply-To: <20260907-bulky-adorable-agama-40ece9@quoll>

On Mon, Sep 07, 2026 at 05:03:00PM +0800, Krzysztof Kozlowski wrote:
> On Thu, Sep 03, 2026 at 06:15:43PM +0800, Amber Kao wrote:
> > This binding is submitted independently so it can be reviewed on
> 
> No, it cannot be reviewed on its own, because splitting it means you
> have undocumented compatibles in the other patchset.
> 
> And if you do not, then there is no user for this binding.
> 
> > its own; once the driver series lands, IT527x support will be wired
> > into it there.
> 
> Then what is the point of this binding now?

Understood, that's a fair point — reviewing a binding without a driver
user in tree is a waste of everyone's time. I'll drop this standalone
binding patch.

> > +    - IT5271: single-port variant, SPR
> > +    - IT5272: two-port variant, SPR
> > +    - IT5273: single-port variant, EPR
> > +    - IT5274: two-port variant, EPR
> > +
> 
> Why isn't this entire binding part of the other file?

IT527x and IT885x are different hardware, which is why we described
them in separate DT bindings. However, since their UCSI operational
flow is similar, they share the same driver (ucsi_itepd.c).

> > +properties:
> > +  compatible:
> > +    oneOf:
> > +      - const: ite,it5271
> > +      - items:
> > +          - const: ite,it5272
> 
> enum

Noted, will fix in the next submission.

> I finished actually here, becausr I still find reviewing outside of
> driver a waste of our time.

Instead of resubmitting this binding alone, I'm planning to send a new
series containing both the binding (with the enum fix) and the
corresponding compatible strings added to ucsi_itepd.c, so there's
always a driver user for the binding under review.

One thing I'd like to check first: the base IT8851/IT8853 series this
depends on has already picked up Reviewed-by tags from Heikki Krogerus
and Rob Herring, but hasn't landed in mainline yet. Heikki previously
suggested it's fine to send a follow-up series before the base lands,
as long as the dependency is noted in the cover letter. Given that,
would you be okay with me sending the IT527x driver+binding series now
with that dependency called out, or would you prefer I wait until the
IT8851/IT8853 series is actually merged first?

Best regards,
Amber Kao

      reply	other threads:[~2026-09-07  9:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03 10:15 [PATCH] dt-bindings: usb: Add ITE IT5271/IT5272/IT5273/IT5274 support Amber Kao
2026-09-03 10:22 ` sashiko-bot
2026-09-07  9:02 ` Krzysztof Kozlowski
2026-09-07  9:57   ` amber.kao [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=cc3a8a7133184decb06884d65c5f06c5@ite.com.tw \
    --to=amber.kao@ite.com.tw \
    --cc=Yaode.Fang@ite.com.tw \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=ite_pd@ite.com.tw \
    --cc=jeson.yang@ite.com.tw \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --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