From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Fabrice Gasnier <fabrice.gasnier@foss.st.com>,
robh+dt@kernel.org, heikki.krogerus@linux.intel.com,
gregkh@linuxfoundation.org
Cc: krzysztof.kozlowski+dt@linaro.org, devicetree@vger.kernel.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
amelie.delaunay@foss.st.com, alexandre.torgue@foss.st.com
Subject: Re: [PATCH 1/4] dt-bindings: usb: typec: add bindings for stm32g0 controller
Date: Fri, 24 Jun 2022 18:16:27 +0200 [thread overview]
Message-ID: <ddb0e946-c955-1404-c1cd-c2548f34ec35@linaro.org> (raw)
In-Reply-To: <20220624155413.399190-2-fabrice.gasnier@foss.st.com>
On 24/06/2022 17:54, Fabrice Gasnier wrote:
> This patch adds DT schema documentation for the STM32G0 Type-C controller.
No "This patch"
https://elixir.bootlin.com/linux/v5.17.1/source/Documentation/process/submitting-patches.rst#L95
> STM32G0 provides an integrated USB Type-C and power delivery interface.
> It can be programmed with a firmware to handle UCSI protocol over I2C
> interface. A GPIO is used as an interrupt line.
> It may be used as a wakeup source, so use optional "wakeup-source" and
> "power-domains" properties to support wakeup.
>
> Signed-off-by: Fabrice Gasnier <fabrice.gasnier@foss.st.com>
> ---
> .../bindings/usb/st,typec-stm32g0.yaml | 83 +++++++++++++++++++
> 1 file changed, 83 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/usb/st,typec-stm32g0.yaml
>
> diff --git a/Documentation/devicetree/bindings/usb/st,typec-stm32g0.yaml b/Documentation/devicetree/bindings/usb/st,typec-stm32g0.yaml
> new file mode 100644
> index 0000000000000..b2729bd015a1a
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/usb/st,typec-stm32g0.yaml
> @@ -0,0 +1,83 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: "http://devicetree.org/schemas/usb/st,typec-stm32g0.yaml#"
> +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
No quotes.
> +
> +title: STMicroelectronics STM32G0 Type-C controller bindings
s/bindings//
> +
> +description: |
> + The STM32G0 MCU can be programmed to control Type-C connector(s) through I2C
> + typically using the UCSI protocol over I2C, with a dedicated alert
> + (interrupt) pin.
> +
> +maintainers:
> + - Fabrice Gasnier <fabrice.gasnier@foss.st.com>
> +
> +properties:
> + compatible:
> + const: st,stm32g0-typec
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + connector:
> + type: object> + allOf:
> + - $ref: ../connector/usb-connector.yaml#
Full path, so /schemas/connector/...
unevaluatedProperties: false
> +
> + firmware-name:
> + description: |
> + Should contain the name of the default firmware image
> + file located on the firmware search path
> +
> + wakeup-source: true
> + power-domains: true
maxItems
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/irq.h>
> + i2c5 {
Just "i2c"
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + stm32g0@53 {
Generic node name describing class of the device.
> + compatible = "st,stm32g0-typec";
> + reg = <0x53>;
> + /* Alert pin on GPIO PE12 */
> + interrupts = <12 IRQ_TYPE_EDGE_FALLING>;
> + interrupt-parent = <&gpioe>;
> +
> + /* Example with one type-C connector */
> + connector {
> + compatible = "usb-c-connector";
> + label = "USB-C";
> +
> + port {
This does not look like proper schema of connector.yaml.
> + con_usb_c_ep: endpoint {
> + remote-endpoint = <&usbotg_hs_ep>;
> + };
> + };
> + };
> + };
> + };
> +
> + usbotg_hs {
Generic node names, no underscores in node names.
> + usb-role-switch;
> + port {
> + usbotg_hs_ep: endpoint {
> + remote-endpoint = <&con_usb_c_ep>;
> + };
> + };
> + };
> +...
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-06-24 16:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 15:54 [PATCH 0/4] usb: typec: ucsi: add support for stm32g0 Fabrice Gasnier
2022-06-24 15:54 ` [PATCH 1/4] dt-bindings: usb: typec: add bindings for stm32g0 controller Fabrice Gasnier
2022-06-24 16:16 ` Krzysztof Kozlowski [this message]
2022-06-27 14:21 ` Fabrice Gasnier
2022-06-28 10:28 ` Krzysztof Kozlowski
2022-06-28 17:01 ` Fabrice Gasnier
2022-06-29 5:54 ` Krzysztof Kozlowski
2022-07-01 10:04 ` Fabrice Gasnier
2022-07-04 7:55 ` Krzysztof Kozlowski
2022-07-04 9:08 ` Fabrice Gasnier
2022-07-06 7:06 ` Krzysztof Kozlowski
2022-06-24 15:54 ` [PATCH 2/4] usb: typec: ucsi: stm32g0: add support for stm32g0 i2c controller Fabrice Gasnier
2022-06-25 6:37 ` Christophe JAILLET
2022-06-27 13:17 ` Heikki Krogerus
2022-06-28 7:21 ` Fabrice Gasnier
2022-06-28 9:56 ` Heikki Krogerus
2022-06-24 15:54 ` [PATCH 3/4] usb: typec: ucsi: stm32g0: add bootloader support Fabrice Gasnier
2022-06-24 15:54 ` [PATCH 4/4] usb: typec: ucsi: stm32g0: add support for power management Fabrice Gasnier
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=ddb0e946-c955-1404-c1cd-c2548f34ec35@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alexandre.torgue@foss.st.com \
--cc=amelie.delaunay@foss.st.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrice.gasnier@foss.st.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-usb@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).