From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: Kai Ruhnau <kai.ruhnau@target-sg.com>,
"linux-usb\@vger.kernel.org" <linux-usb@vger.kernel.org>,
Peter Chen <peter.chen@nxp.com>
Subject: RE: No carrier lost information with gadget RNDIS/ECM
Date: Thu, 27 Jun 2019 09:21:49 +0300 [thread overview]
Message-ID: <871rzffszm.fsf@linux.intel.com> (raw)
In-Reply-To: <AM0PR02MB384108B692229DF41816A363C5E20@AM0PR02MB3841.eurprd02.prod.outlook.com>
Hi,
Kai Ruhnau <kai.ruhnau@target-sg.com> writes:
>>> I have activated CONFIG_USB_GADGET_DEBUG_FILES, and the contents of
>>> /proc/driver/rndis-000 don't change when I pull the cable:
>>>
>>> Config Nr. 0
>>> used : y
>>> state : RNDIS_DATA_INITIALIZED
>>> medium : 0x00000000
>>> speed : 425984000
>>> cable : connected
>>> vendor ID : 0x00000000
>>> vendor : (null)
>>>
>>> Only when changing the host to a Mac, it's different:
>>> Config Nr. 0
>>> used : y
>>> state : RNDIS_UNINITIALIZED
>>> medium : 0x00000000
>>> speed : 425984000
>>> cable : connected
>>> vendor ID : 0x00000000
>>> vendor : (null)
>>>
>>> Thanks for any help.
>>
>> Which peripheral controller is this board using? Is it chipidea? dwc2?
>> dwc3? High Speed or Super Speed?
>
> According to the device tree it's 'fsl,imx6sx-usb' driven by chipidea/ci_hdrc_imx.c
> When connecting to Windows, the dmesg shows:
> configfs-gadget gadget: high-speed config #2: c
Okay, adding Peter (chipidea maintainer) to the loop here. There are a
few changes on UDC side of chipidea between 4.9 and 5.1:
$ git --no-pager log --no-merges --oneline v4.9..v5.1 -- drivers/usb/chipidea/udc.c
16caf1fa37db usb: chipidea: Add dynamic pinctrl selection
51b751f112dc USB: chipidea: Remove redundant license text
5fd54ace4721 USB: add SPDX identifiers to all remaining files in drivers/usb/
fc5b920c3b9b usb: chipidea: do charger detection in vbus session
581821ae7f7e usb: chipidea: udc: Support SKB alignment quirk
734c58aefcc4 usb: chipidea: udc: compress return logic into line
aa1f058d7d92 usb: chipidea: udc: fix NULL pointer dereference if udc_start failed
a932a8041ff9 usb: chipidea: core: add sysfs group
aeb78cda5100 usb: chipidea: use bus->sysdev for DMA configuration
4f4555cfe704 usb: chipidea: udc: update gadget state after bus resume
afff6067b305 usb: chipidea: Drop lock across event_notify during gadget stop
732a4af85e87 usb: chipidea: Remove locking in ci_udc_start()
34445fb4333f usb: chipidea: Properly mark little endian descriptors
63b9e901e461 usb: chipidea: udc: remove unnecessary & operation
a98e25e71d11 usb: chipidea: udc: make use of new usb_endpoint_maxp_mult()
Peter, have you seen the problem described before?
--
balbi
next prev parent reply other threads:[~2019-06-27 6:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 12:00 No carrier lost information with gadget RNDIS/ECM Kai Ruhnau
2019-06-26 12:13 ` Felipe Balbi
2019-06-26 12:53 ` Kai Ruhnau
2019-06-27 6:21 ` Felipe Balbi [this message]
2019-06-27 15:50 ` Kai Ruhnau
2019-06-28 1:20 ` Peter Chen
2019-06-28 8:30 ` Kai Ruhnau
2019-06-28 13:28 ` Kai Ruhnau
2019-07-01 6:44 ` Peter Chen
2019-07-01 10:54 ` Kai Ruhnau
2019-07-02 2:18 ` Peter Chen
2019-07-02 6:48 ` Kai Ruhnau
2019-07-02 8:29 ` Peter Chen
2019-07-02 12:56 ` Kai Ruhnau
2019-07-04 6:07 ` Peter Chen
2019-07-05 7:21 ` Kai Ruhnau
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=871rzffszm.fsf@linux.intel.com \
--to=felipe.balbi@linux.intel.com \
--cc=kai.ruhnau@target-sg.com \
--cc=linux-usb@vger.kernel.org \
--cc=peter.chen@nxp.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).