From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Felipe Balbi <felipe.balbi@linux.intel.com>, gregkh@linuxfoundation.org
Cc: stern@rowland.harvard.edu, linux-usb@vger.kernel.org
Subject: [1/2] USB: Add support to store lane count used by USB 3.2
Date: Tue, 13 Mar 2018 17:53:23 +0200 [thread overview]
Message-ID: <032703fb-18b4-1ae2-426a-0a0198b8b2aa@linux.intel.com> (raw)
On 13.03.2018 17:29, Felipe Balbi wrote:
>
> Hi,
>
> Mathias Nyman <mathias.nyman@linux.intel.com> writes:
>
>> USB 3.2 specification adds Dual-lane support, doubling the maximum
>> SuperSpeedPlus data rate from 10Gbps to 20Gbps.
>>
>> Dual-lane takes into use a second set of rx and tx wires/pins in the
>> Type-C cable and connector.
>>
>> Add a "lanes" variable to struct usb_device to store the numer of lanes
>> in use. Number of lanes can be read using the extended port status hub
>> request that was introduced in USB 3.1.
>>
>> Extended port status rx and tx lane count are zero based, maximum
>> lanes supported by usb 3.2 is 2 (dual lane).
>> If extended port status is not available then default to one lane.
>>
>> Signed-off-by: Mathias Nyman <mathias.nyman@linux.intel.com>
>> ---
>> drivers/usb/core/hub.c | 6 ++++++
>> include/linux/usb.h | 2 ++
>> 2 files changed, 8 insertions(+)
>>
>> diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c
>> index c5c1f6c..853516d 100644
>> --- a/drivers/usb/core/hub.c
>> +++ b/drivers/usb/core/hub.c
>> @@ -2742,6 +2742,12 @@ static int hub_port_wait_reset(struct usb_hub *hub, int port1,
>> if (!udev)
>> return 0;
>>
>> + if (hub_is_superspeedplus(hub->hdev))
>> + udev->lanes = ((ext_portstatus &
>> + USB_EXT_PORT_STAT_RX_LANES) >> 8) + 1;
>
> should this be udev->rx_lanes instead? We have macros for both TX and RX
> lanes:
>
> #define USB_EXT_PORT_STAT_RX_SPEED_ID 0x0000000f
> #define USB_EXT_PORT_STAT_TX_SPEED_ID 0x000000f0
> #define USB_EXT_PORT_STAT_RX_LANES 0x00000f00
> #define USB_EXT_PORT_STAT_TX_LANES 0x0000f000
>
This is one part of the discussion, For non-SSIC devices, the lane count is
symmetric so rx_lanes = tx_lanes.
The USB 3.2 Gen XxY notion seems to only cover symmetric lane counts as
the "Y" part describes one generic "lane count".
See USB 3.2 section 8.5.6.7:
"Asymmetric Lane Types may only be reported by SuperSpeed Interchip (SSIC) devices. A
Symmetric link is one that has the same Lane Speed and number of lanes for both the Rx and
Tx Sublinks. Enhanced SuperSpeed devices shall only support Symmetric links."
and definition on Gen XxY in section 2. Terms and abbreviations
"X refers to the rate of signaling on the wire (Gen 1, Gen 2, etc.) and Y refers to
the number of lanes."
-Mathias
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-03-13 15:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 15:53 Mathias Nyman [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-13 15:29 [1/2] USB: Add support to store lane count used by USB 3.2 Felipe Balbi
2018-03-13 15:27 Mathias Nyman
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=032703fb-18b4-1ae2-426a-0a0198b8b2aa@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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).