From: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
To: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, linux-usb@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: jtornosm@redhat.com
Subject: [PATCH] net: usb: ax88179_178a: avoid failed operations when device is disconnected
Date: Wed, 29 Nov 2023 16:16:11 +0100 [thread overview]
Message-ID: <20231129151618.455618-1-jtornosm@redhat.com> (raw)
When the device is disconnected we get the following messages showing
failed operations:
Nov 28 20:22:11 localhost kernel: usb 2-3: USB disconnect, device number 2
Nov 28 20:22:11 localhost kernel: ax88179_178a 2-3:1.0 enp2s0u3: unregister 'ax88179_178a' usb-0000:02:00.0-3, ASIX AX88179 USB 3.0 Gigabit Ethernet
Nov 28 20:22:11 localhost kernel: ax88179_178a 2-3:1.0 enp2s0u3: Failed to read reg index 0x0002: -19
Nov 28 20:22:11 localhost kernel: ax88179_178a 2-3:1.0 enp2s0u3: Failed to write reg index 0x0002: -19
Nov 28 20:22:11 localhost kernel: ax88179_178a 2-3:1.0 enp2s0u3 (unregistered): Failed to write reg index 0x0002: -19
Nov 28 20:22:11 localhost kernel: ax88179_178a 2-3:1.0 enp2s0u3 (unregistered): Failed to write reg index 0x0001: -19
Nov 28 20:22:11 localhost kernel: ax88179_178a 2-3:1.0 enp2s0u3 (unregistered): Failed to write reg index 0x0002: -19
The reason is that although the device is detached, normal stop and
unbind operations are commanded. Avoid these unnecessary operations
when the device is detached (state is USB_STATE_NOTATTACHED) so as
not to get the error messages.
Fixes: e2ca90c276e1f ("ax88179_178a: ASIX AX88179_178A USB 3.0/2.0 to gigabit ethernet adapter driver")
Signed-off-by: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
---
drivers/net/usb/ax88179_178a.c | 26 +++++++++++++++-----------
1 file changed, 15 insertions(+), 11 deletions(-)
diff --git a/drivers/net/usb/ax88179_178a.c b/drivers/net/usb/ax88179_178a.c
index 4ea0e155bb0d..e78d555dd95e 100644
--- a/drivers/net/usb/ax88179_178a.c
+++ b/drivers/net/usb/ax88179_178a.c
@@ -1308,16 +1308,18 @@ static void ax88179_unbind(struct usbnet *dev, struct usb_interface *intf)
struct ax88179_data *ax179_data = dev->driver_priv;
u16 tmp16;
- /* Configure RX control register => stop operation */
- tmp16 = AX_RX_CTL_STOP;
- ax88179_write_cmd(dev, AX_ACCESS_MAC, AX_RX_CTL, 2, 2, &tmp16);
+ if (dev->udev->state != USB_STATE_NOTATTACHED) {
+ /* Configure RX control register => stop operation */
+ tmp16 = AX_RX_CTL_STOP;
+ ax88179_write_cmd(dev, AX_ACCESS_MAC, AX_RX_CTL, 2, 2, &tmp16);
- tmp16 = 0;
- ax88179_write_cmd(dev, AX_ACCESS_MAC, AX_CLK_SELECT, 1, 1, &tmp16);
+ tmp16 = 0;
+ ax88179_write_cmd(dev, AX_ACCESS_MAC, AX_CLK_SELECT, 1, 1, &tmp16);
- /* Power down ethernet PHY */
- tmp16 = 0;
- ax88179_write_cmd(dev, AX_ACCESS_MAC, AX_PHYPWR_RSTCTL, 2, 2, &tmp16);
+ /* Power down ethernet PHY */
+ tmp16 = 0;
+ ax88179_write_cmd(dev, AX_ACCESS_MAC, AX_PHYPWR_RSTCTL, 2, 2, &tmp16);
+ }
kfree(ax179_data);
}
@@ -1663,11 +1665,13 @@ static int ax88179_stop(struct usbnet *dev)
{
u16 tmp16;
- ax88179_read_cmd(dev, AX_ACCESS_MAC, AX_MEDIUM_STATUS_MODE,
+ if (dev->udev->state != USB_STATE_NOTATTACHED) {
+ ax88179_read_cmd(dev, AX_ACCESS_MAC, AX_MEDIUM_STATUS_MODE,
2, 2, &tmp16);
- tmp16 &= ~AX_MEDIUM_RECEIVE_EN;
- ax88179_write_cmd(dev, AX_ACCESS_MAC, AX_MEDIUM_STATUS_MODE,
+ tmp16 &= ~AX_MEDIUM_RECEIVE_EN;
+ ax88179_write_cmd(dev, AX_ACCESS_MAC, AX_MEDIUM_STATUS_MODE,
2, 2, &tmp16);
+ }
return 0;
}
--
2.43.0
next reply other threads:[~2023-11-29 15:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 15:16 Jose Ignacio Tornos Martinez [this message]
2023-11-29 15:33 ` [PATCH] net: usb: ax88179_178a: avoid failed operations when device is disconnected Oliver Neukum
2023-11-29 15:40 ` Alan Stern
2023-11-30 8:41 ` Jose Ignacio Tornos Martinez
2023-11-30 15:50 ` Alan Stern
2023-11-30 17:25 ` Jose Ignacio Tornos Martinez
2023-11-30 18:13 ` Alan Stern
2023-12-01 10:46 ` Jose Ignacio Tornos Martinez
2023-12-01 11:51 ` [PATCH v2] " Jose Ignacio Tornos Martinez
2023-12-01 12:25 ` Greg KH
2023-12-01 13:26 ` [PATCH v3] " Jose Ignacio Tornos Martinez
2023-12-01 16:13 ` Alan Stern
2023-12-01 17:27 ` Jose Ignacio Tornos Martinez
2023-12-01 20:14 ` Oliver Neukum
2023-12-04 11:31 ` Jose Ignacio Tornos Martinez
2023-12-05 13:51 ` [PATCH v4] " Jose Ignacio Tornos Martinez
2023-12-05 18:07 ` Alan Stern
2023-12-06 12:17 ` Jose Ignacio Tornos Martinez
2023-12-07 11:42 ` [PATCH v5] " Jose Ignacio Tornos Martinez
2023-12-07 16:41 ` Alan Stern
2023-12-07 17:50 ` [PATCH v6] " Jose Ignacio Tornos Martinez
2023-12-07 20:23 ` Alan Stern
2023-12-07 20:32 ` Jakub Kicinski
2023-12-08 4:56 ` Greg KH
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=20231129151618.455618-1-jtornosm@redhat.com \
--to=jtornosm@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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