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>
---
V1 -> V2: no changes
---
Documentation/devicetree/bindings/usb/nxp,ptn5110.yaml | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Documentation/devicetree/bindings/usb/nxp,ptn5110.yaml b/Documentation/devicetree/bindings/usb/nxp,ptn5110.yaml
index 65a8632..c31ec7e 100644
--- a/Documentation/devicetree/bindings/usb/nxp,ptn5110.yaml
+++ b/Documentation/devicetree/bindings/usb/nxp,ptn5110.yaml
@@ -21,6 +21,11 @@ properties:
interrupts:
maxItems: 1
+ TX_BUF_BYTE_x_hidden: true
+ RX_BUF_BYTE_x_hidden: true
+ auto_discharge_disconnect: true
+ vbus_vsafe0v: true
+
connector:
type: object
$ref: /schemas/connector/usb-connector.yaml#
--
2.9.3
On Wed, 18 Dec 2024 02:07:18 +0100, Miao.Zhu wrote: > 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> > --- > V1 -> V2: no changes > --- > Documentation/devicetree/bindings/usb/nxp,ptn5110.yaml | 5 +++++ > 1 file changed, 5 insertions(+) > My bot found errors running 'make dt_binding_check' on your patch: yamllint warnings/errors: dtschema/dtc warnings/errors: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/usb/nxp,ptn5110.yaml: TX_BUF_BYTE_x_hidden: missing type definition /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/usb/nxp,ptn5110.yaml: RX_BUF_BYTE_x_hidden: missing type definition /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/usb/nxp,ptn5110.yaml: auto_discharge_disconnect: missing type definition /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/usb/nxp,ptn5110.yaml: vbus_vsafe0v: missing type definition doc reference errors (make refcheckdocs): See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20241218010718.224530-3-miao@synopsys.com The base for the series is generally the latest rc1. A different dependency should be noted in *this* patch. If you already ran 'make dt_binding_check' and didn't see the above error(s), then make sure 'yamllint' is installed and dt-schema is up to date: pip3 install dtschema --upgrade Please check and re-submit after running the above command yourself. Note that DT_SCHEMA_FILES can be set to your schema file to speed up checking your schema. However, it must be unset to test all examples with your schema.
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>
---
V2 -> V3: Add description and type for new properties:
V1 -> V2: No changes
---
.../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..29d6aed 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:
+ When set, TX_BUF_BYTE_x can only be accessed through
+ I2C_WRITE_BYTE_COUNT.
+ type: boolean
+
+ RX_BUF_BYTE_x_hidden:
+ description:
+ When set, RX_BUF_BYTE_x can only be accessed through
+ READABLE_BYTE_COUNT.
+ type: boolean
+
+ auto_discharge_disconnect:
+ description:
+ When set, TCPC autonomously discharges vbus on disconnect.
+ type: boolean
+
+ vbus_vsafe0v:
+ description:
+ When set, TCPC can detect whether vbus is at VSAFE0V.
+ type: boolean
+
connector:
type: object
$ref: /schemas/connector/usb-connector.yaml#
--
2.9.3
From: Miao Zhu <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>
---
V2 -> V3: Add description and type for new properties:
---
.../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..29d6aed 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:
+ When set, TX_BUF_BYTE_x can only be accessed through
+ I2C_WRITE_BYTE_COUNT.
+ type: boolean
+
+ RX_BUF_BYTE_x_hidden:
+ description:
+ When set, RX_BUF_BYTE_x can only be accessed through
+ READABLE_BYTE_COUNT.
+ type: boolean
+
+ auto_discharge_disconnect:
+ description:
+ When set, TCPC autonomously discharges vbus on disconnect.
+ type: boolean
+
+ vbus_vsafe0v:
+ description:
+ When set, TCPC can detect whether vbus is at VSAFE0V.
+ type: boolean
+
connector:
type: object
$ref: /schemas/connector/usb-connector.yaml#
--
2.9.3
On 18/12/2024 06:22, Miao.Zhu wrote: > From: Miao Zhu <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. Do not attach (thread) your patchsets to some other threads (unrelated or older versions). This buries them deep in the mailbox and might interfere with applying entire sets. <form letter> Please use scripts/get_maintainers.pl to get a list of necessary people and lists to CC (and consider --no-git-fallback argument, so you will not CC people just because they made one commit years ago). It might happen, that command when run on an older kernel, gives you outdated entries. Therefore please be sure you base your patches on recent Linux kernel. Tools like b4 or scripts/get_maintainer.pl provide you proper list of people, so fix your workflow. Tools might also fail if you work on some ancient tree (don't, instead use mainline) or work on fork of kernel (don't, instead use mainline). Just use b4 and everything should be fine, although remember about `b4 prep --auto-to-cc` if you added new patches to the patchset. </form letter> > > Signed-off-by: Miao.Zhu <miao@synopsys.com> > --- > V2 -> V3: Add description and type for new properties: > --- > .../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..29d6aed 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: Follow DTS coding style. > + description: > + When set, TX_BUF_BYTE_x can only be accessed through > + I2C_WRITE_BYTE_COUNT. You described the desired Linux feature or behavior, not the actual hardware. The bindings are about the latter, so instead you need to rephrase the property and its description to match actual hardware capabilities/features/configuration etc. Best regards, Krzysztof
On 18/12/2024 09:04, Krzysztof Kozlowski wrote: >> interrupts: >> maxItems: 1 >> >> + TX_BUF_BYTE_x_hidden: > > Follow DTS coding style. > >> + description: >> + When set, TX_BUF_BYTE_x can only be accessed through >> + I2C_WRITE_BYTE_COUNT. > You described the desired Linux feature or behavior, not the actual > hardware. The bindings are about the latter, so instead you need to > rephrase the property and its description to match actual hardware > capabilities/features/configuration etc. I forgot: missing vendor prefix, missing type. Please see how other bindings are written. example-schema is also good to start with. Best regards, Krzysztof
© 2016 - 2025 Red Hat, Inc.