From: "Miao.Zhu" <Miao.Zhu@synopsys.com>
To: gregkh@linuxfoundation.org, robh@kernel.org, xu.yang_2@nxp.com,
andre.draszik@linaro.org, dan.carpenter@linaro.org,
emanuele.ghidoli@toradex.com, heikki.krogerus@linux.intel.com,
m.felsch@pengutronix.de, rdbabiera@google.com,
u.kleine-koenig@baylibre.com, conor+dt@kernel.org,
jun.li@nxp.com
Cc: "Miao.Zhu" <Miao.Zhu@synopsys.com>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
devicetree@vger.kernel.org, Jianheng.Zhang@synopsys.com,
James.Li1@synopsys.com, Martin.McKenny@synopsys.com
Subject: [PATCH v4 2/2] dt-bindings: usb: ptn5110: add TCPC properties
Date: Wed, 18 Dec 2024 09:59:33 +0100 [thread overview]
Message-ID: <20241218085933.2790127-3-miao@synopsys.com> (raw)
In-Reply-To: <20241218085933.2790127-1-miao@synopsys.com>
The TCPCI driver has flags to configure its protperties but
no way to enable these flags yet. Add these flags into DT
so that the driver can be compatible with TCPCI Spec R2 V1.0.
Signed-off-by: Miao.Zhu <miao@synopsys.com>
---
V3 -> V4: refine description to follow DTS coding style
V2 -> V3: add description and type for new properties
V1 -> V2: new patch
---
.../devicetree/bindings/usb/nxp,ptn5110.yaml | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/Documentation/devicetree/bindings/usb/nxp,ptn5110.yaml b/Documentation/devicetree/bindings/usb/nxp,ptn5110.yaml
index 65a8632..f5059dc7 100644
--- a/Documentation/devicetree/bindings/usb/nxp,ptn5110.yaml
+++ b/Documentation/devicetree/bindings/usb/nxp,ptn5110.yaml
@@ -21,6 +21,28 @@ properties:
interrupts:
maxItems: 1
+ TX_BUF_BYTE_x_hidden:
+ description:
+ True when TX_BUF_BYTE_x can only be accessed through
+ I2C_WRITE_BYTE_COUNT.
+ type: boolean
+
+ RX_BUF_BYTE_x_hidden:
+ description:
+ True when RX_BUF_BYTE_x can only be accessed through
+ READABLE_BYTE_COUNT.
+ type: boolean
+
+ auto_discharge_disconnect:
+ description:
+ True when TCPC can autonomously discharge vbus on disconnect.
+ type: boolean
+
+ vbus_vsafe0v:
+ description:
+ True when TCPC can detect whether vbus is at VSAFE0V.
+ type: boolean
+
connector:
type: object
$ref: /schemas/connector/usb-connector.yaml#
--
2.9.3
next prev parent reply other threads:[~2024-12-18 9:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 8:59 [PATCH v4 0/2] usb: typec: tcpci: Make the driver be compatible with TCPCI Spec Miao.Zhu
2024-12-18 8:59 ` [PATCH v4 1/2] usb: typec: tcpm: tcpci: Make the driver be compatible with the TCPCI spec [Rev 2.0 Ver 1.0, October 2017] Miao.Zhu
2024-12-18 9:33 ` Dan Carpenter
2024-12-18 15:41 ` Dan Carpenter
2024-12-18 8:59 ` Miao.Zhu [this message]
2024-12-18 17:08 ` [PATCH v4 2/2] dt-bindings: usb: ptn5110: add TCPC properties Conor Dooley
2024-12-19 8:02 ` 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=20241218085933.2790127-3-miao@synopsys.com \
--to=miao.zhu@synopsys.com \
--cc=James.Li1@synopsys.com \
--cc=Jianheng.Zhang@synopsys.com \
--cc=Martin.McKenny@synopsys.com \
--cc=andre.draszik@linaro.org \
--cc=conor+dt@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=emanuele.ghidoli@toradex.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jun.li@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=rdbabiera@google.com \
--cc=robh@kernel.org \
--cc=u.kleine-koenig@baylibre.com \
--cc=xu.yang_2@nxp.com \
/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