From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Cc: Felipe Balbi <balbi@kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
John Youn <John.Youn@synopsys.com>
Subject: Re: [PATCH v7 0/6] usb: Support USB 3.2 multi-lanes
Date: Fri, 5 Feb 2021 07:49:42 +0100 [thread overview]
Message-ID: <YBzqhlNeKf+lgA+8@kroah.com> (raw)
In-Reply-To: <04cc67bd-29b0-91d7-6144-a3f4dc6661f9@synopsys.com>
On Fri, Feb 05, 2021 at 02:39:41AM +0000, Thinh Nguyen wrote:
> Hi Felipe, Greg,
>
> Thinh Nguyen wrote:
> > A USB SuperSpeed Plus device may operate at different speed and lane count
> > (i.e. gen2x2, gen1x2, or gen2x1). The DWC_usb32 IP supports SuperSpeed Plus
> > gen2x2. To support this, this series update a few things to the USB gadget
> > stack and dwc3 driver:
> >
> > * Accept and parse new maximum_speed devicetree property strings
> > * Introduce enum usb_ssp_rate to describe the speed in SuperSpeed Plus genXxY
> > * Capture the connected and max supported usb_ssp_rate
> > * Report the device sublink speeds base on the usb_ssp_rate in the BOS
> > descriptor
> > * Introduce gadget ops to select SuperSpeed Plus various transfer rate and lane
> > count
> > * Update dwc3 driver to support the above changes
> >
> > Changes in v7:
> > - Greg picked up the first few patches of the series to his usb-testing
> > branch. Rebase the remaining patches on Greg's usb-testing branch
> >
> > Changes in v6:
> > - Rebase on Greg's usb-testing branch
> > - Update cover letter and title since there are many updates
> > * Previous version 5: https://lore.kernel.org/linux-usb/cover.1601001199.git.Thinh.Nguyen@synopsys.com/
> > - To simplify things, use usb_ssp_rate enum to specify the signaling rate
> > generation and lane count instead of separately tracking them.
> > - Convert the sublink speed attributes to macros and move it to uapi
> > - Remove usb_sublink_speed struct
> > - Remove "usb: dwc3: gadget: Report sublink speed capability"
> > - Update dwc3 to support the new changes
> >
> > Changes in v5:
> > - Rebase on Felipe's testing/next branch
> > - Changed Signed-off-by email to match From: email header
> > - Add Rob's Reviewed-by
> >
> > Changes in v4:
> > - Instead of using a single function to parse "maximum-speed" property for
> > speed, gen X, and number of lanes, split those tasks to separate common
> > functions
> > - Revise DWC3 driver to use those new common functions
> > - Fix checkpatch warnings for using "unsigned" rather than "unsigned int" and
> > missing identifier name in udc_set_num_lanes_and_speed gadget ops
> >
> > Changes in v3:
> > - Remove "num-lanes" and "lane-speed-mantissa-gbps" common properties
> > - Remove "num-lanes" and "lane-speed-mantissa-gbps" properties validation in dwc3
> > - Update "maximum-speed" to support variations of SSP Gen X x Y
> > - Update common function to parse new strings for "maximum-speed"
> > - Update commit messages for the new changes
> >
> > Changes in v2:
> > - Move usb_sublink_speed attribute struct and enum to include/linux/usb/ch9.h
> > - Use "num-lanes" and "lane-speed-mantissa-gbps" as common properties instead
> > - Add common functions to get num-lanes and lsm properties
> > - Fix missing gen1x2 sublink speed attribute check report in dwc3
> >
> >
> > Thinh Nguyen (6):
> > dt-binding: usb: Include USB SSP rates in GenXxY
> > usb: common: Parse for USB SSP genXxY
> > usb: dwc3: core: Check maximum_speed SSP genXxY
> > usb: dwc3: gadget: Implement setting of SSP rate
> > usb: dwc3: gadget: Track connected SSP rate and lane count
> > usb: dwc3: gadget: Set speed only up to the max supported
> >
> > .../devicetree/bindings/usb/usb.yaml | 3 +
> > drivers/usb/common/common.c | 26 +++++-
> > drivers/usb/dwc3/core.c | 37 +++++++++
> > drivers/usb/dwc3/core.h | 9 +++
> > drivers/usb/dwc3/gadget.c | 80 ++++++++++++++++++-
> > include/linux/usb/ch9.h | 11 +++
> > 6 files changed, 162 insertions(+), 4 deletions(-)
> >
> >
> > base-commit: 7a79f1f7f7e75e532c5a803ab3ebf42a3e79497c
>
> Let me know if there's any issue with these remaining patches. It'd be
> great if they can go on the "next" branch at some point.
I was waiting for Rob's review of the dt changes...
prev parent reply other threads:[~2021-02-05 6:51 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
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 [this message]
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=YBzqhlNeKf+lgA+8@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=John.Youn@synopsys.com \
--cc=Thinh.Nguyen@synopsys.com \
--cc=balbi@kernel.org \
--cc=devicetree@vger.kernel.org \
--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).