From: Felipe Balbi <balbi@kernel.org>
To: Sid Spry <sid@aeam.us>, linux-usb@vger.kernel.org
Subject: Re: ConfigFS: bcdUSB forced to 0x0210
Date: Sat, 03 Oct 2020 09:07:57 +0300 [thread overview]
Message-ID: <87d01zyh8i.fsf@kernel.org> (raw)
In-Reply-To: <7d974f24-c297-4e4f-97aa-76ae85f897db@www.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 3061 bytes --]
Hi,
"Sid Spry" <sid@aeam.us> writes:
>> >> "Sid Spry" <sid@aeam.us> writes:
>> >> > Hi, I can't enable USB3 with e.g. f_ncm because bcdUSB is always reset to 0x0210:
>> >> >
>> >> > $ sudo sh -c 'echo "0x0300" > /sys/kernel/config/usb_gadget/g11/bcdUSB'
>> >> > $ cat /sys/kernel/config/usb_gadget/g11/bcdUSB
>> >> > 0x0300
>> >> > $ sudo sh -c 'echo "fe800000.usb" > /sys/kernel/config/usb_gadget/g11/UDC'
>> >> > $ cat /sys/kernel/config/usb_gadget/g11/bcdUSB
>> >> > 0x0210
>> >> > $ tree /sys/kernel/config/usb_gadget/g11
>> >> > /sys/kernel/config/usb_gadget/g11
>> >> > ├── bcdDevice
>> >> > ├── bcdUSB
>> >> > ├── bDeviceClass
>> >> > ├── bDeviceProtocol
>> >> > ├── bDeviceSubClass
>> >> > ├── bMaxPacketSize0
>> >> > ├── configs
>> >> > │ └── c.1
>> >> > │ ├── bmAttributes
>> >> > │ ├── MaxPower
>> >> > │ ├── ncm.0 -> ../../../../usb_gadget/g11/functions/ncm.0
>> >> > │ └── strings
>> >> > │ └── 0x409
>> >> > │ └── configuration
>> >> > ├── functions
>> >> > │ └── ncm.0
>> >> > │ ├── dev_addr
>> >> > │ ├── host_addr
>> >> > │ ├── ifname
>> >> > │ ├── os_desc
>> >> > │ │ └── interface.ncm
>> >> > │ │ ├── compatible_id
>> >> > │ │ └── sub_compatible_id
>> >> > │ └── qmult
>> >> > ├── idProduct
>> >> > ├── idVendor
>> >> > ├── max_speed
>> >> > ├── os_desc
>> >> > │ ├── b_vendor_code
>> >> > │ ├── qw_sign
>> >> > │ └── use
>> >> > ├── strings
>> >> > │ └── 0x409
>> >> > │ ├── manufacturer
>> >> > │ ├── product
>> >> > │ └── serialnumber
>> >> > └── UDC
>> >> >
>> >> > Board is a RK3399 based RockPro64.
>> >>
>> >> what's your max_speed?
>> >>
>> >
>> > $ cat /sys/kernel/config/usb_gadget/g11/max_speed
>> > super-speed
>> >
>> > Looks ok. From Windows, the xHCI driver reports that the device supports
>> > super speed but chooses high speed. I can't see this info from a Linux host.
>>
>> It's probably failing Rx.Detect and falling back to high-speed. Which
>> USB Peripheral Controller is that?
>>
>
> It's a dwc3. I recently found that if I plug the device into itself (there are two
> dwc3, one on a C port, one on a female A port) the device enumerates at
> superspeed with the NCM configfs driver. But connecting to my x86 machines
> fails.
>
> In an earlier thread I found that the type C port would not work with USB2
> or 3 if in the "normal" direction (as opposed to "reversed").
sounds like a board layout problem to me. Can you capture dwc3
tracepoints? More information here:
https://www.kernel.org/doc/html/latest/driver-api/usb/dwc3.html#reporting-bugs
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 857 bytes --]
prev parent reply other threads:[~2020-10-03 6:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 2:40 ConfigFS: bcdUSB forced to 0x0210 Sid Spry
2020-09-29 6:33 ` Felipe Balbi
2020-09-29 23:16 ` Sid Spry
2020-10-02 6:54 ` Felipe Balbi
2020-10-03 2:07 ` Sid Spry
2020-10-03 6:07 ` Felipe Balbi [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=87d01zyh8i.fsf@kernel.org \
--to=balbi@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sid@aeam.us \
/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).