From: Rob Herring <robh@kernel.org>
To: rentao.bupt@gmail.com
Cc: Felipe Balbi <balbi@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Joel Stanley <joel@jms.id.au>, Andrew Jeffery <andrew@aj.id.au>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Chunfeng Yun <chunfeng.yun@mediatek.com>,
Colin Ian King <colin.king@canonical.com>,
Stephen Boyd <swboyd@chromium.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-usb@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, openbmc@lists.ozlabs.org,
taoren@fb.com
Subject: Re: [PATCH v2 6/6] dt-bindings: usb: document aspeed vhub device ID/string properties
Date: Mon, 30 Mar 2020 13:23:47 -0600 [thread overview]
Message-ID: <20200330192347.GA6388@bogus> (raw)
In-Reply-To: <20200315191632.12536-7-rentao.bupt@gmail.com>
On Sun, Mar 15, 2020 at 12:16:32PM -0700, rentao.bupt@gmail.com wrote:
> From: Tao Ren <rentao.bupt@gmail.com>
>
> Update device tree binding document for aspeed vhub's device IDs and
> string properties.
>
> Signed-off-by: Tao Ren <rentao.bupt@gmail.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
next prev parent reply other threads:[~2020-03-30 19:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-15 19:16 [PATCH v2 0/6] usb: gadget: aspeed: allow to customize vhub device rentao.bupt
2020-03-15 19:16 ` [PATCH v2 1/6] usb: gadget: aspeed: support multiple language strings rentao.bupt
2020-03-15 19:16 ` [PATCH v2 2/6] usb: gadget: add "usb_validate_langid" function rentao.bupt
2020-03-15 19:16 ` [PATCH v2 3/6] usb: gadget: aspeed: allow to set usb strings in device tree rentao.bupt
2020-03-15 19:16 ` [PATCH v2 4/6] usb: gadget: aspeed: allow to set device IDs " rentao.bupt
2020-03-15 19:16 ` [PATCH v2 5/6] usb: gadget: aspeed: fixup usb1 device descriptor at init time rentao.bupt
2020-03-15 19:16 ` [PATCH v2 6/6] dt-bindings: usb: document aspeed vhub device ID/string properties rentao.bupt
2020-03-30 19:23 ` Rob Herring [this message]
2020-03-31 0:13 ` Benjamin Herrenschmidt
2020-03-31 16:21 ` Rob Herring
2020-04-01 0:47 ` Tao Ren
2020-04-02 10:37 ` Benjamin Herrenschmidt
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=20200330192347.GA6388@bogus \
--to=robh@kernel.org \
--cc=andrew@aj.id.au \
--cc=balbi@kernel.org \
--cc=benh@kernel.crashing.org \
--cc=chunfeng.yun@mediatek.com \
--cc=colin.king@canonical.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=openbmc@lists.ozlabs.org \
--cc=rentao.bupt@gmail.com \
--cc=swboyd@chromium.org \
--cc=taoren@fb.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;
as well as URLs for NNTP newsgroup(s).