From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: Rob Herring <robh@kernel.org>, Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Cc: Felipe Balbi <balbi@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
John Youn <John.Youn@synopsys.com>,
Rob Herring <robh+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v7 1/6] dt-binding: usb: Include USB SSP rates in GenXxY
Date: Sat, 6 Feb 2021 03:14:30 +0000 [thread overview]
Message-ID: <22957a1b-c7c3-c029-fb70-a44b4ef85539@synopsys.com> (raw)
In-Reply-To: <20210205204618.GA3702715@robh.at.kernel.org>
Rob Herring wrote:
> On Tue, 19 Jan 2021 17:36:08 -0800, Thinh Nguyen wrote:
>> According to the USB 3.2 spec, a SuperSpeed Plus device can operate at
>> gen2x2, gen2x1, or gen1x2. If the USB controller device supports
>> multiple lanes at different transfer rates, the user can specify the HW
>> capability via these new speed strings:
>>
>> "super-speed-plus-gen2x2"
>> "super-speed-plus-gen2x1"
>> "super-speed-plus-gen1x2"
>>
>> If the argument is simply "super-speed-plus", USB controllers should
>> default to their maximum transfer rate and number of lanes.
>>
>> Signed-off-by: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
>> ---
>> Changes in v7:
>> - Rebase on Greg's usb-testing branch
>> Changes in v6:
>> - Update the different maximum_speed enums to the usb.yaml
>> - Remove Reviewed-by: Rob Herring <robh@kernel.org> because the commit is updated
>> - Rebase on Greg's usb-testing branch
>> - Update commit message
>> Changes in v5:
>> - Add Reviewed-by: Rob Herring <robh@kernel.org>
>> - Rebase on Felipe's testing/next branch
>> - Changed Signed-off-by email to match From: email header
>> Changes in v4:
>> - None
>> Changes in v3:
>> - Use "maximum-speed" to include both the num-lane and transfer rate for SSP
>> - Remove "num-lanes" and "lane-speed-mantissa-gbps" properties
>> Changes in v2:
>> - Make "num-lanes" and "lane-speed-mantissa-gbps" common USB properties
>>
>> Documentation/devicetree/bindings/usb/usb.yaml | 3 +++
>> 1 file changed, 3 insertions(+)
>>
> Reviewed-by: Rob Herring <robh@kernel.org>
Thanks!
Thinh
next prev parent reply other threads:[~2021-02-06 3:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 1:36 [PATCH v7 0/6] usb: Support USB 3.2 multi-lanes Thinh Nguyen
2021-01-20 1:36 ` [PATCH v7 1/6] dt-binding: usb: Include USB SSP rates in GenXxY Thinh Nguyen
2021-02-05 2:32 ` Thinh Nguyen
2021-02-05 20:46 ` Rob Herring
2021-02-06 3:14 ` Thinh Nguyen [this message]
2021-01-20 1:36 ` [PATCH v7 2/6] usb: common: Parse for USB SSP genXxY Thinh Nguyen
2021-01-20 1:36 ` [PATCH v7 3/6] usb: dwc3: core: Check maximum_speed " Thinh Nguyen
2021-01-20 1:36 ` [PATCH v7 4/6] usb: dwc3: gadget: Implement setting of SSP rate Thinh Nguyen
2021-01-20 1:36 ` [PATCH v7 5/6] usb: dwc3: gadget: Track connected SSP rate and lane count Thinh Nguyen
2021-01-20 1:36 ` [PATCH v7 6/6] usb: dwc3: gadget: Set speed only up to the max supported Thinh Nguyen
2021-02-05 2:39 ` [PATCH v7 0/6] usb: Support USB 3.2 multi-lanes Thinh Nguyen
2021-02-05 6:49 ` Greg Kroah-Hartman
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=22957a1b-c7c3-c029-fb70-a44b4ef85539@synopsys.com \
--to=thinh.nguyen@synopsys.com \
--cc=John.Youn@synopsys.com \
--cc=balbi@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@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).