[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <18ac05fb-a78d-4e95-a73d-461f509cdc5f@linaro.org>
Date: Sun, 11 Feb 2024 14:39:36 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Stephen Boyd <swboyd@...omium.org>, chrome-platform@...ts.linux.dev
Cc: linux-kernel@...r.kernel.org, patches@...ts.linux.dev,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
linux-arm-msm@...r.kernel.org, Douglas Anderson <dianders@...omium.org>,
Pin-yen Lin <treapking@...omium.org>, Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>, Benson Leung <bleung@...omium.org>,
Guenter Roeck <groeck@...omium.org>
Subject: Re: [PATCH 18/22] dt-bindings: chrome: Add binding for ChromeOS Pogo
pin connector
On 10/02/2024 08:09, Stephen Boyd wrote:
> Describe the set of pins used to connect the detachable keyboard on
> detachable ChromeOS devices. The set of pins is called the "pogo pins".
> It's basically USB 2.0 with an extra pin for base detection. We expect
> to find a keyboard on the other side of this connector with a specific
> vid/pid, so describe that as a child device at the port of the usb
> device connected upstream.
>
> Cc: Rob Herring <robh+dt@...nel.org>
> Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>
> Cc: Conor Dooley <conor+dt@...nel.org>
> Cc: Benson Leung <bleung@...omium.org>
> Cc: Guenter Roeck <groeck@...omium.org>
> Cc: <devicetree@...r.kernel.org>
> Cc: <chrome-platform@...ts.linux.dev>
> Cc: Pin-yen Lin <treapking@...omium.org>
> Signed-off-by: Stephen Boyd <swboyd@...omium.org>
> ---
> .../chrome/google,pogo-pin-connector.yaml | 61 +++++++++++++++++++
> 1 file changed, 61 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/chrome/google,pogo-pin-connector.yaml
>
> diff --git a/Documentation/devicetree/bindings/chrome/google,pogo-pin-connector.yaml b/Documentation/devicetree/bindings/chrome/google,pogo-pin-connector.yaml
> new file mode 100644
> index 000000000000..5ba68fd95fcd
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/chrome/google,pogo-pin-connector.yaml
> @@ -0,0 +1,61 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/chrome/google,pogo-pin-connector.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Google Pogo Pin Connector
> +
> +maintainers:
> + - Stephen Boyd <swboyd@...omium.org>
> +
Missing description describing the hardware.
> +properties:
> + compatible:
> + const: google,pogo-pin-connector
> +
> + "#address-cells":
> + const: 1
> +
> + "#size-cells":
> + const: 0
> +
> + port:
> + $ref: /schemas/graph.yaml#/properties/port
> + description: Connection to USB2 port providing USB signals
> + required:
> + - endpoint
Drop required.
> +
> +patternProperties:
> + "^keyboard@[0-9a-f]{1,2}$":
> + description: The detachable keyboard
If this is detachable why do you define it in DT? Only hard-wired USB
devices, which need some sort of special handling. are described in DT.
> + type: object
> + $ref: /schemas/usb/usb-device.yaml
On this level:
unevaluatedProperties: false
> +
> +required:
> + - compatible
> + - '#address-cells'
> + - '#size-cells'
Use one type of quotes, either ' or ".
> + - port
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + connector {
> + compatible = "google,pogo-pin-connector";
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + keyboard@2 {
> + compatible = "usb18d1,504c";
Messed indentation.
> + reg = <2>;
> + };
> +
Best regards,
Krzysztof
Powered by blists - more mailing lists