From: Pavel Machek <pavel@ucw.cz>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: phone-devel@vger.kernel.org,
kernel list <linux-kernel@vger.kernel.org>,
fiona.klute@gmx.de, martijn@brixit.nl, samuel@sholland.org,
heikki.krogerus@linux.intel.com, gregkh@linuxfoundation.org,
linux-usb@vger.kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, devicetree@vger.kernel.org,
megi@xff.cz
Subject: Re: [PATCHv3 1/2] dt-bindings: usb: typec: anx7688: start a binding document
Date: Mon, 8 Apr 2024 13:21:51 +0200 [thread overview]
Message-ID: <ZhPTTxI4oTF3pgrk@duo.ucw.cz> (raw)
In-Reply-To: <ab9affc8-de68-4ec9-bdfc-02131191bc3a@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]
Hi!
> > Add binding for anx7688 usb type-c bridge. I don't have a datasheet,
> > but I did best I could.
> >
> > Signed-off-by: Pavel Machek <pavel@ucw.cz>
>
> ...
>
> > + cabledet-gpios:
> > + maxItems: 1
> > + description: GPIO controlling CABLE_DET (C3) pin.
> > +
> > + avdd10-supply:
> > + description: 1.0V power supply going to AVDD10 (A4, ...) pins
> > +
> > + dvdd10-supply:
> > + description: 1.0V power supply going to DVDD10 (D6, ...) pins
> > +
> > + avdd18-supply:
> > + description: 1.8V power supply going to AVDD18 (E3, ...) pins
> > +
> > + dvdd18-supply:
> > + description: 1.8V power supply going to DVDD18 (G4, ...) pins
> > +
> > + avdd33-supply:
> > + description: 3.3V power supply going to AVDD33 (C4, ...) pins
> > +
> > + i2c-supply: true
> > + vconn-supply: true
>
> There are no such supplies like i2c and vconn on the schematics.
>
> I think this represents some other part of component which was added
> here only for convenience.
Can you give me pointer to documentation you are looking at?
Best regards,
Pavel
--
People of Russia, stop Putin before his war on Ukraine escalates.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2024-04-08 11:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 10:51 [PATCHv3 1/2] dt-bindings: usb: typec: anx7688: start a binding document Pavel Machek
2024-04-08 10:54 ` [PATCHv3 2/2] usb: typec: anx7688: Add driver for ANX7688 USB-C HDMI bridge Pavel Machek
2024-04-09 9:56 ` Heikki Krogerus
2024-04-09 11:04 ` Pavel Machek
2024-04-09 15:35 ` Dmitry Baryshkov
2024-04-10 11:32 ` Ondřej Jirman
2024-04-10 11:35 ` Ondřej Jirman
2024-04-16 7:29 ` Heikki Krogerus
2024-04-08 11:17 ` [PATCHv3 1/2] dt-bindings: usb: typec: anx7688: start a binding document Krzysztof Kozlowski
2024-04-08 11:21 ` Pavel Machek [this message]
2024-04-08 11:24 ` Krzysztof Kozlowski
2024-04-08 11:52 ` Ondřej Jirman
2024-04-08 11:59 ` Krzysztof Kozlowski
2024-04-08 12:48 ` Ondřej Jirman
2024-04-08 13:27 ` Krzysztof Kozlowski
2024-04-08 15:17 ` Ondřej Jirman
2024-04-08 20:12 ` Krzysztof Kozlowski
2024-04-10 2:20 ` Ondřej Jirman
2024-04-11 19:59 ` Krzysztof Kozlowski
2024-04-11 20:17 ` Dmitry Baryshkov
2024-04-08 11:51 ` Ondřej Jirman
2024-04-08 12:01 ` Krzysztof Kozlowski
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=ZhPTTxI4oTF3pgrk@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=devicetree@vger.kernel.org \
--cc=fiona.klute@gmx.de \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=martijn@brixit.nl \
--cc=megi@xff.cz \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=samuel@sholland.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