From: Andrew Lunn <andrew@lunn.ch>
To: Fabio Estevam <festevam@gmail.com>
Cc: Schrempf Frieder <frieder.schrempf@kontron.de>,
Martyn Welch <martyn.welch@collabora.com>,
Marek Vasut <marex@denx.de>, USB list <linux-usb@vger.kernel.org>,
oneukum@suse.com, Adam Ford <aford173@gmail.com>,
peter.chen@kernel.org,
Steve Glendinning <steve.glendinning@shawell.net>,
fntoth@gmail.com
Subject: Re: smsc9511: Register access happens after unregistration
Date: Fri, 4 Mar 2022 15:51:33 +0100 [thread overview]
Message-ID: <YiIndfh0B87LRYnI@lunn.ch> (raw)
In-Reply-To: <CAOMZO5CioYoddT0kqtf+wOTvvxArm9ipW2bAj84qKM_eQgMcjg@mail.gmail.com>
> # echo -n "2-1" > /sys/bus/usb/drivers/usb/unbind
> usb 2-1.1: USB disconnect, device number 3
> smsc95xx 2-1.1:1.0 eth1: unregister 'smsc95xx' usb-ci_hdrc.1-1.1,
> smsc95xx USB 2.0 Ethernet
> smsc95xx 2-1.1:1.0 eth1: Failed to read reg index 0x00000114: -19
> smsc95xx 2-1.1:1.0 eth1: Error reading MII_ACCESS
> *********** smsc95xx_unbind: calling phy_disconnect
> smsc95xx 2-1.1:1.0 eth1: __smsc95xx_mdio_read: MII is busy
> libphy: *********** phy_disconnect: 1
> libphy: *********** phy_disconnect: 2
> *************** phy_stop
> smsc95xx 2-1.1:1.0 eth1: Failed to read reg index 0x00000114: -19
> smsc95xx 2-1.1:1.0 eth1: Error reading MII_ACCESS
> smsc95xx 2-1.1:1.0 eth1: __smsc95xx_mdio_read: MII is busy
> smsc95xx 2-1.1:1.0 eth1: Failed to read reg index 0x00000114: -19
> smsc95xx 2-1.1:1.0 eth1: Error reading MII_ACCESS
> smsc95xx 2-1.1:1.0 eth1: __smsc95xx_mdio_read: MII is busy
> *********** smsc95xx_stop
> smsc95xx 2-1.1:1.0 eth1: hardware isn't capable of remote wakeup
> usb 2-1.4: USB disconnect, device number 4
>
> Maybe the -19 errors should be ignored?
But why does it return ENODEV? It seems to me, ignoring it is papering
over the cracks. Why cannot we access to the PHY?
Andrew
next prev parent reply other threads:[~2022-03-04 14:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 13:14 smsc9511: Register access happens after unregistration Fabio Estevam
2022-03-04 13:58 ` Fabio Estevam
2022-03-04 14:11 ` Andrew Lunn
2022-03-04 14:18 ` Martyn Welch
2022-03-04 14:45 ` Andrew Lunn
2022-03-04 14:40 ` Fabio Estevam
2022-03-04 14:51 ` Andrew Lunn [this message]
2022-03-04 15:57 ` Fabio Estevam
2022-03-04 18:01 ` Fabio Estevam
2022-03-04 23:59 ` Andrew Lunn
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=YiIndfh0B87LRYnI@lunn.ch \
--to=andrew@lunn.ch \
--cc=aford173@gmail.com \
--cc=festevam@gmail.com \
--cc=fntoth@gmail.com \
--cc=frieder.schrempf@kontron.de \
--cc=linux-usb@vger.kernel.org \
--cc=marex@denx.de \
--cc=martyn.welch@collabora.com \
--cc=oneukum@suse.com \
--cc=peter.chen@kernel.org \
--cc=steve.glendinning@shawell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.