[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200330192347.GA6388@bogus>
Date: Mon, 30 Mar 2020 13:23:47 -0600
From: Rob Herring <robh@...nel.org>
To: rentao.bupt@...il.com
Cc: Felipe Balbi <balbi@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Joel Stanley <joel@....id.au>,
Andrew Jeffery <andrew@...id.au>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Chunfeng Yun <chunfeng.yun@...iatek.com>,
Colin Ian King <colin.king@...onical.com>,
Stephen Boyd <swboyd@...omium.org>,
Mark Rutland <mark.rutland@....com>, linux-usb@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-aspeed@...ts.ozlabs.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, openbmc@...ts.ozlabs.org,
taoren@...com
Subject: Re: [PATCH v2 6/6] dt-bindings: usb: document aspeed vhub device
ID/string properties
On Sun, Mar 15, 2020 at 12:16:32PM -0700, rentao.bupt@...il.com wrote:
> From: Tao Ren <rentao.bupt@...il.com>
>
> Update device tree binding document for aspeed vhub's device IDs and
> string properties.
>
> Signed-off-by: Tao Ren <rentao.bupt@...il.com>
> ---
> No change in v2:
> - the patch is added into the series since v2.
>
> .../bindings/usb/aspeed,usb-vhub.yaml | 68 +++++++++++++++++++
> 1 file changed, 68 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/usb/aspeed,usb-vhub.yaml b/Documentation/devicetree/bindings/usb/aspeed,usb-vhub.yaml
> index 06399ba0d9e4..5b2e8d867219 100644
> --- a/Documentation/devicetree/bindings/usb/aspeed,usb-vhub.yaml
> +++ b/Documentation/devicetree/bindings/usb/aspeed,usb-vhub.yaml
> @@ -52,6 +52,59 @@ properties:
> minimum: 1
> maximum: 21
>
> + vhub-vendor-id:
> + description: vhub Vendor ID
> + allOf:
> + - $ref: /schemas/types.yaml#/definitions/uint32
> + - maximum: 65535
> +
> + vhub-product-id:
> + description: vhub Product ID
> + allOf:
> + - $ref: /schemas/types.yaml#/definitions/uint32
> + - maximum: 65535
There's already standard 'vendor-id' and 'device-id' properties. Use
those.
> +
> + vhub-device-revision:
Specific to USB, not vhub.
> + description: vhub Device Revision in binary-coded decimal
> + allOf:
> + - $ref: /schemas/types.yaml#/definitions/uint32
> + - maximum: 65535
> +
> + vhub-strings:
> + type: object
> +
> + properties:
> + '#address-cells':
> + const: 1
> +
> + '#size-cells':
> + const: 0
> +
> + patternProperties:
> + '^string@[0-9a-f]+$':
> + type: object
> + description: string descriptors of the specific language
> +
> + properties:
> + reg:
> + maxItems: 1
> + description: 16-bit Language Identifier defined by USB-IF
> +
> + manufacturer:
> + description: vhub manufacturer
> + allOf:
> + - $ref: /schemas/types.yaml#/definitions/string
> +
> + product:
> + description: vhub product name
> + allOf:
> + - $ref: /schemas/types.yaml#/definitions/string
> +
> + serial-number:
> + description: vhub device serial number
> + allOf:
> + - $ref: /schemas/types.yaml#/definitions/string
For all of this, it's USB specific, not vhub specific. I'm not sure this
is the right approach. It might be better to just define properties
which are just raw USB descriptors rather than inventing some DT format
that then has to be converted into USB descriptors.
Rob
Powered by blists - more mailing lists