From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 4/8] net: usb: asix: ax88772: add phylib support
Date: Fri, 18 Jun 2021 15:10:11 +0200 [thread overview]
Message-ID: <20210618131011.puodgt4niemsabno@pengutronix.de> (raw)
In-Reply-To: <b3b990b5-d2f6-3e93-effd-44e10c5dfb5e@samsung.com>
On Fri, Jun 18, 2021 at 12:57:13PM +0200, Marek Szyprowski wrote:
> On 18.06.2021 12:45, Marek Szyprowski wrote:
> > On 18.06.2021 12:13, Oleksij Rempel wrote:
> >> thank you for your feedback.
> >>
> >> On Fri, Jun 18, 2021 at 10:39:12AM +0200, Marek Szyprowski wrote:
> >>> On 07.06.2021 10:27, Oleksij Rempel wrote:
> >>>> To be able to use ax88772 with external PHYs and use advantage of
> >>>> existing PHY drivers, we need to port at least ax88772 part of asix
> >>>> driver to the phylib framework.
> >>>>
> >>>> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> >>> I found one more issue with this patch. On one of my test boards
> >>> (Samsung Exynos5250 SoC based Arndale) system fails to establish
> >>> network
> >>> connection just after starting the kernel when the driver is build-in.
> >>>
> >>> --->8---
> >>> # dmesg | grep asix
> >>> [ 2.761928] usbcore: registered new interface driver asix
> >>> [ 5.003110] asix 1-3.2.4:1.0 (unnamed net_device) (uninitialized):
> >>> invalid hw address, using random
> >>> [ 6.065400] asix 1-3.2.4:1.0 eth0: register 'asix' at
> >>> usb-12110000.usb-3.2.4, ASIX AX88772 USB 2.0 Ethernet,
> >>> 7a:9b:9a:f2:94:8e
> >>> [ 14.043868] asix 1-3.2.4:1.0 eth0: Link is Up - 100Mbps/Full - flow
> >>> control off
> >>> # ping -c2 host
> >>> PING host (192.168.100.1) 56(84) bytes of data.
> >>> From 192.168.100.20 icmp_seq=1 Destination Host Unreachable
> >>> From 192.168.100.20 icmp_seq=2 Destination Host Unreachable
> >>>
> >>> --- host ping statistics ---
> >>> 2 packets transmitted, 0 received, +2 errors, 100% packet loss, time
> >>> 59ms
> >>> --->8---
> >> Hm... it looks like different chip variant. My is registered as
> >> "ASIX AX88772B USB", yours is "ASIX AX88772 USB 2.0" - "B" is the
> >> difference. Can you please tell me more about this adapter and if
> >> possible open
> >> tell the real part name.
> > Well, currently I have only remote access to that board. The network
> > chip is soldered on board. Maybe you can read something from the photo
> > on the wiki page: https://en.wikipedia.org/wiki/Arndale_Board
> >> I can imagine that this adapter may using generic PHY driver.
> >> Can you please confirm it by dmesg | grep PHY?
> >> In my case i'll get:
> >> Asix Electronics AX88772C usb-001:003:10: attached PHY driver
> >> (mii_bus:phy_addr=usb-001:003:10, irq=POLL)
> > # dmesg | grep PHY
> > [ 5.700274] Asix Electronics AX88772A usb-001:004:10: attached PHY
> > driver (mii_bus:phy_addr=usb-001:004:10, irq=POLL)
> >> If you have a different PHY, can you please send me the PHY id:
> >> cat /sys/bus/mdio_bus/devices/usb-001\:003\:10/phy_id
> >>
> >> Your usb path will probably be different.
> >
> > # cat /sys/bus/mdio_bus/devices/usb-001\:004\:10/phy_id
> > 0x003b1861
> >
> > > ...
>
> Just for the record, I also have a board with external USB Ethernet
> dongle based on ASIX chip, which works fine with this patch, both when
> driver is built-in or as a module. Here is the log:
>
> # dmesg | grep -i Asix
> [ 1.718349] usbcore: registered new interface driver asix
> [ 2.608596] usb 3-1: Manufacturer: ASIX Elec. Corp.
> [ 3.876279] libphy: Asix MDIO Bus: probed
> [ 3.958105] Asix Electronics AX88772C usb-003:002:10: attached PHY
> driver (mii_bus:phy_addr=usb-003:002:10, irq=POLL)
> [ 3.962728] asix 3-1:1.0 eth0: register 'asix' at
> usb-xhci-hcd.6.auto-1, ASIX AX88772B USB 2.0 Ethernet, 00:50:b6:18:92:f0
> [ 17.488532] asix 3-1:1.0 eth0: Link is Down
> [ 19.557233] asix 3-1:1.0 eth0: Link is Up - 100Mbps/Full - flow
> control off
>
> # cat /sys/bus/mdio_bus/devices/usb-003\:002\:10/phy_id
> 0x003b1881
Ok, this one is different. It is AX88772C variant.
--
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:[~2021-06-18 13:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 8:27 [PATCH net-next v2 0/8] port asix ax88772 to the PHYlib Oleksij Rempel
2021-06-07 8:27 ` [PATCH net-next v2 1/8] net: usb: asix: ax88772_bind: use devm_kzalloc() instead of kzalloc() Oleksij Rempel
2021-06-07 8:27 ` [PATCH net-next v2 2/8] net: usb: asix: refactor asix_read_phy_addr() and handle errors on return Oleksij Rempel
2021-06-07 8:27 ` [PATCH net-next v2 3/8] net: usb/phy: asix: add support for ax88772A/C PHYs Oleksij Rempel
2021-06-07 8:27 ` [PATCH net-next v2 4/8] net: usb: asix: ax88772: add phylib support Oleksij Rempel
[not found] ` <CGME20210609095923eucas1p2e692c9a482151742d543316c91f29802@eucas1p2.samsung.com>
2021-06-09 9:59 ` Marek Szyprowski
2021-06-09 12:46 ` Oleksij Rempel
2021-06-09 13:12 ` Heiner Kallweit
2021-06-10 13:36 ` Oleksij Rempel
2021-06-10 10:31 ` Marek Szyprowski
2021-06-10 12:54 ` Jon Hunter
2021-06-10 14:22 ` Oleksij Rempel
[not found] ` <CGME20210618083914eucas1p240f88e7064a7bf15b68370b7506d24a9@eucas1p2.samsung.com>
2021-06-18 8:39 ` Marek Szyprowski
2021-06-18 10:13 ` Oleksij Rempel
2021-06-18 10:45 ` Marek Szyprowski
2021-06-18 10:57 ` Marek Szyprowski
2021-06-18 13:10 ` Oleksij Rempel [this message]
2021-06-18 11:04 ` Heiner Kallweit
2021-06-18 11:11 ` Marek Szyprowski
2021-06-18 13:20 ` Oleksij Rempel
2021-06-21 6:05 ` Marek Szyprowski
2021-06-23 7:06 ` Oleksij Rempel
2021-06-28 8:27 ` Marek Szyprowski
2021-06-07 8:27 ` [PATCH net-next v2 5/8] net: usb: asix: ax88772: add generic selftest support Oleksij Rempel
2021-06-07 8:27 ` [PATCH net-next v2 6/8] net: usb: asix: add error handling for asix_mdio_* functions Oleksij Rempel
2021-06-07 8:27 ` [PATCH net-next v2 7/8] net: phy: do not print dump stack if device was removed Oleksij Rempel
2021-06-07 8:27 ` [PATCH net-next v2 8/8] usbnet: run unbind() before unregister_netdev() Oleksij Rempel
2021-06-07 20:40 ` [PATCH net-next v2 0/8] port asix ax88772 to the PHYlib patchwork-bot+netdevbpf
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=20210618131011.puodgt4niemsabno@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=m.szyprowski@samsung.com \
--cc=netdev@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).