From: Marco Felsch <m.felsch@pengutronix.de>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org,
heikki.krogerus@linux.intel.com, kernel@pengutronix.de,
gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, linux@roeck-us.net,
jun.li@nxp.com
Subject: Re: [PATCH v2 1/4] dt-bindings: usb: typec-tcpci: add tcpci fallback binding
Date: Thu, 22 Feb 2024 22:13:34 +0100 [thread overview]
Message-ID: <20240222211334.xvgwe33dsj7digrt@pengutronix.de> (raw)
In-Reply-To: <20240222202357.2etmuoy6i6qr6bnq@pengutronix.de>
On 24-02-22, Marco Felsch wrote:
> On 24-02-22, Krzysztof Kozlowski wrote:
> > On 15/02/2024 22:28, Marco Felsch wrote:
> > > The NXP PTN5110 [1] is an TCPCI [2] compatible chip, so add the fallback
> > > binding.
> > >
> > > [1] https://www.nxp.com/docs/en/data-sheet/PTN5110.pdf
> > > [2] https://www.usb.org/sites/default/files/documents/usb-port_controller_specification_rev2.0_v1.0_0.pdf
> > >
> > > Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
> > > ---
> > > v2:
> > > - rephrase commit message
> > >
> > > Documentation/devicetree/bindings/usb/nxp,ptn5110.yaml | 4 +++-
> > > 1 file changed, 3 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/Documentation/devicetree/bindings/usb/nxp,ptn5110.yaml b/Documentation/devicetree/bindings/usb/nxp,ptn5110.yaml
> > > index eaedb4cc6b6c..7bd7bbbac9e0 100644
> > > --- a/Documentation/devicetree/bindings/usb/nxp,ptn5110.yaml
> > > +++ b/Documentation/devicetree/bindings/usb/nxp,ptn5110.yaml
> > > @@ -11,7 +11,9 @@ maintainers:
> > >
> > > properties:
> > > compatible:
> > > - const: nxp,ptn5110
> > > + enum:
> > > + - nxp,ptn5110
> > > + - tcpci
> >
> > That's not a fallback, but enum. Fallback is "items" and then you could
>
> Damn, you're right. Sorry.
>
> > also send a follow-up patchset (separate, so Greg won't take it) fixing
> > DTS (if not, let me know, so I will fix it).
>
> Sry. but I don't get this. Why do I need to send a follow-up? Greg did
> not apply anything, at least I didn't received an e-mail, that this
> patchset was picked.
Got it now and made it this way.
Regards,
Marco
next prev parent reply other threads:[~2024-02-22 21:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 21:28 [PATCH v2 0/4] USB-C TCPM Orientation Support Marco Felsch
2024-02-15 21:28 ` [PATCH v2 1/4] dt-bindings: usb: typec-tcpci: add tcpci fallback binding Marco Felsch
2024-02-22 16:19 ` Krzysztof Kozlowski
2024-02-22 20:23 ` Marco Felsch
2024-02-22 21:13 ` Marco Felsch [this message]
2024-02-24 9:15 ` Krzysztof Kozlowski
2024-02-15 21:28 ` [PATCH v2 2/4] usb: typec: tcpci: add generic tcpci fallback compatible Marco Felsch
2024-02-15 21:28 ` [PATCH v2 3/4] usb: typec: tcpm: add support to set tcpc connector orientatition Marco Felsch
2024-02-15 21:28 ` [PATCH v2 4/4] usb: typec: tcpci: add support to set connector orientation Marco Felsch
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=20240222211334.xvgwe33dsj7digrt@pengutronix.de \
--to=m.felsch@pengutronix.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jun.li@nxp.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh+dt@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
all inboxes | Powered by JetHome®