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>
Subject: Re: No carrier lost information with gadget RNDIS/ECM
Date: Wed, 26 Jun 2019 15:13:26 +0300 [thread overview]
Message-ID: <87o92kk0ih.fsf@linux.intel.com> (raw)
In-Reply-To: <AM0PR02MB3841F110F7B6931A087DF566C5E20@AM0PR02MB3841.eurprd02.prod.outlook.com>
Hi,
Kai Ruhnau <kai.ruhnau@target-sg.com> writes:
> On my i.MX6 SoloX, I have configured one of the OTG ports for a
> combined RNDIS/ECM gadget. After boot, I have two network interfaces
> (usb0 and usb1) which are managed by systemd-networkd.
>
> With kernel 4.9.153, systemd-networkd reports an immediate carrier
> loss when I pull the USB cable from a Windows or macOS host. With
> 4.19.53 or 5.1.15 that carrier loss is only reported when I re-attach
> the cable, meaning there is a "Lost carrier" for the last used
> interface immediately followed by a "Gained carrier" for the newly
> connected interface.
First of all, thanks for actually testing the most recent stable
kernels. Much appreciated :-)
> 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?
--
balbi
next prev parent reply other threads:[~2019-06-26 12:13 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 [this message]
2019-06-26 12:53 ` Kai Ruhnau
2019-06-27 6:21 ` Felipe Balbi
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=87o92kk0ih.fsf@linux.intel.com \
--to=felipe.balbi@linux.intel.com \
--cc=kai.ruhnau@target-sg.com \
--cc=linux-usb@vger.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).