From: Sascha Hauer <s.hauer@pengutronix.de>
To: Paul Cercueil <paul@crapouillou.net>
Cc: linux-usb@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH 1/2] usb: gadget: u_ether: Do not make UDC parent of the net device
Date: Thu, 9 Feb 2023 12:41:03 +0100 [thread overview]
Message-ID: <20230209114103.GQ10447@pengutronix.de> (raw)
In-Reply-To: <6d618e518de06854727f26de950404f02ec61c64.camel@crapouillou.net>
On Thu, Feb 09, 2023 at 10:37:05AM +0000, Paul Cercueil wrote:
> Hi Sascha,
>
> Le jeudi 09 février 2023 à 11:18 +0100, Sascha Hauer a écrit :
> > Hi Paul,
> >
> > On Wed, Feb 01, 2023 at 01:32:51PM +0000, Paul Cercueil wrote:
> > > Hi Sascha, Greg,
> > >
> > > I have a breakage in 6.2-rc* that I eventually bisected to this
> > > commit,
> > > on a Ingenic SoC (using the jz4740 musb driver) with ECM or RNDIS
> > > configured through gadgetfs.
> > >
> > > When plugging the board to my PC, the USB network interface is
> > > recognized, but 'ip link' sees it as 'NO-CARRIER'. With this commit
> > > reverted on v6.2-rc5, everything works fine.
> >
> > I don't have this hardware available. I just tried with a i.MX
> > hardware
> > and it works as expected. I have no idea where the jz4740 musb could
> > behave differently.
> >
> > Here's exactly what I did:
> >
> > mkdir -p /sys/kernel/config/usb_gadget/mygadget
> > cd /sys/kernel/config/usb_gadget/mygadget
> > mkdir -p configs/c.1/strings/0x409
> > echo "C1:Composite Device" > configs/c.1/strings/0x409/configuration
> > mkdir -p functions/ecm.usb0
> > ln -s functions/ecm.usb0 configs/c.1/
> > echo "ci_hdrc.0" > UDC
> >
> > Did you do something differently apart from the "ci_hdrc.0" of
> > course?
>
> Nothing very different, no.
>
> I do:
>
> cd /sys/kernel/config/usb_gadget
> mkdir mtp \
> mtp/strings/0x409 \
> mtp/configs/c.1 \
> mtp/configs/c.1/strings/0x409 \
> mtp/functions/ffs.mtp \
> mtp/functions/ecm.net \
> mtp/functions/rndis.net
>
> echo 0x80 > mtp/configs/c.1/bmAttributes
> echo 500 > mtp/configs/c.1/MaxPower
>
> echo 0x049f > mtp/idVendor
> echo 0x505a > mtp/idProduct
> echo cdc > mtp/configs/c.1/strings/0x409/configuration
> ln -s mtp/functions/ecm.net mtp/configs/c.1/ecm.net
>
> echo ci_hdrc.0 > mtp/UDC
>
> > BTW when you say 'NO-CARRIER' is it on the PC side, board side, or
> > both?
>
> PC side. I don't know what it says on the board side, I can't
> telnet/SSH.
I just checked on the host side: With or without my patch I get
NO-CARRIER on the host. I have to do a 'ip link set usb0 up' on
the device side, with that I get a <BROADCAST,MULTICAST,UP,LOWER_UP>
on the host side.
Could it be that my patch breaks something on the device side that
prevents the device from bringing the link up?
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2023-02-09 11:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 13:10 [PATCH 0/2] use-after-free issues in configfs Sascha Hauer
2022-11-04 13:10 ` [PATCH 1/2] usb: gadget: u_ether: Do not make UDC parent of the net device Sascha Hauer
2023-02-01 13:32 ` Paul Cercueil
2023-02-03 12:46 ` Linux kernel regression tracking (#adding)
2023-02-16 11:07 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-02-08 12:06 ` Greg Kroah-Hartman
2023-02-08 13:45 ` Paul Cercueil
2023-02-09 10:18 ` Sascha Hauer
2023-02-09 10:37 ` Paul Cercueil
2023-02-09 11:41 ` Sascha Hauer [this message]
2023-02-09 15:05 ` Alan Stern
2023-02-10 14:49 ` Sascha Hauer
2023-02-10 15:45 ` Alan Stern
2023-02-10 18:46 ` Sascha Hauer
2023-09-04 13:14 ` Ondřej Jirman
2023-09-05 0:12 ` Ondřej Jirman
2022-11-04 13:10 ` [PATCH 2/2] usb: gadget: f_ecm: Always set current gadget in ecm_bind() Sascha Hauer
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=20230209114103.GQ10447@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=paul@crapouillou.net \
/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