From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 220286] New: asix 88772c does not work when chip is in RMII mode
Date: Fri, 27 Jun 2025 19:55:00 +0000 [thread overview]
Message-ID: <bug-220286-208809@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=220286
Bug ID: 220286
Summary: asix 88772c does not work when chip is in RMII mode
Product: Drivers
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: USB
Assignee: drivers_usb@kernel-bugs.kernel.org
Reporter: dtyree@newagemicro.com
Regression: No
I have two asix 88772c boards, with the standard module the board with (MAC ->
PHY ) presents the proper ethernet interface. With the second board confiured
for RMII (MAC->MAC) the following dmesg occurs:
[442357.683804] usb 1-1.3: new high-speed USB device number 4 using xhci_hcd
[442357.796351] usb 1-1.3: New USB device found, idVendor=0b95, idProduct=772b,
bcdDevice= 0.02
[442357.796380] usb 1-1.3: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[442357.796393] usb 1-1.3: Product: AX88772C
[442357.796403] usb 1-1.3: Manufacturer: ASIX Elec. Corp.
[442357.796412] usb 1-1.3: SerialNumber: 0037BC
[442358.469226] asix 1-1.3:1.0 (unnamed net_device) (uninitialized): PHY
[usb-001:004:10] driver [Asix Electronics AX88772C] (irq=POLL)
[442358.472403] Asix Electronics AX88772C usb-001:004:10: attached PHY driver
(mii_bus:phy_addr=usb-001:004:10, irq=POLL)
[442358.472895] asix 1-1.3:1.0 eth1: register 'asix' at usb-0000:01:00.0-1.3,
ASIX AX88772B USB 2.0 Ethernet, 00:0e:c6:00:37:bc
[442358.472995] usbcore: registered new interface driver asix
[442358.541752] asix 1-1.3:1.0 eth1: configuring for phy/internal link mode
[442360.596155] asix 1-1.3:1.0 eth1: Link is Up - 100Mbps/Full - flow control
rx/tx
[443025.975392] usb 1-1.3: USB disconnect, device number 4
[443025.975978] asix 1-1.3:1.0 eth1: unregister 'asix' usb-0000:01:00.0-1.3,
ASIX AX88772B USB 2.0 Ethernet
[443025.976091] asix 1-1.3:1.0 eth1: Failed to write reg index 0x0000: -19
[443025.976108] asix 1-1.3:1.0 eth1: Failed to enable software MII access
[443025.976153] asix 1-1.3:1.0 eth1: Failed to write reg index 0x0000: -19
[443025.976167] asix 1-1.3:1.0 eth1: Failed to write Medium Mode mode to
0x0000: ffffffed
[443025.976181] asix 1-1.3:1.0 eth1: Link is Down
[443026.003862] asix 1-1.3:1.0 eth1 (unregistered): Failed to write reg index
0x0000: -19
[443026.003896] asix 1-1.3:1.0 eth1 (unregistered): Failed to enable software
MII access
The current drivers from asix are able to work.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
reply other threads:[~2025-06-27 19:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-220286-208809@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--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 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.