From: Andrew Lunn <andrew@lunn.ch>
To: Birger Koblitz <mail@birger-koblitz.de>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Russell King <linux@armlinux.org.uk>,
Heiner Kallweit <hkallweit1@gmail.com>,
linux-usb@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, Jianhui Xu <neuromoments@gmail.com>
Subject: Re: [PATCH net-next v9 06/15] ax88179_178a: Add HW support for AX179A-based chips
Date: Wed, 2 Sep 2026 22:54:33 +0200 [thread overview]
Message-ID: <b87d751c-f736-4cf9-b3f3-88ae2bc9ade1@lunn.ch> (raw)
In-Reply-To: <20260902-ax88179a-v9-6-8e6d7710a2ae@birger-koblitz.de>
On Wed, Sep 02, 2026 at 06:57:20PM +0200, Birger Koblitz wrote:
> This adds bindings and HW support for AX179A-based USB-Ethernet
> controllers. The AX179A-family of chips consists of the
> AX88279 (2.5GBit PHY)
> AX88179A/B (1GBit PHY, B variant has wider temperature range)
> AX772D/E (100Mbit PHY)
>
> The controllers all have the same vendor and device ID
> (0x0b95, 0x1790) and are distinguished by their BCD device versions,
> which are
> 2.00 AX88179A/B
> 3.00 AX88772D/E
> 4.00 AX88279
>
> For all chips, the driver calls the same ax88179a_bind() function
> and the chips are then distinguished by the chip version and
> BCD device ID. The AX179A-based chips all provide both a CDC-NCM
> compatible USB interface, and a proprietary vendor interface. By default,
> the proprietary vendor interface is not active and Linux will load the
> CDC-NCM driver to support the devices. If the ax88179_178a module is
> configured by the OS to have precedence over CDC-NCM, then this driver
> will switch the device to use the vendor interface, and the device will
> be controlled by the ax88179_178a driver when the device is probed again
> after an automatic reset by the device.
>
> Signed-off-by: Birger Koblitz <mail@birger-koblitz.de>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2026-09-02 20:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 16:57 [PATCH net-next v9 00/15] ax88179_178a: Add support for AX88179A-based chips Birger Koblitz
2026-09-02 16:57 ` [PATCH net-next v9 01/15] phylink: Add phylink_mac_interrupt Birger Koblitz
2026-09-02 16:57 ` [PATCH net-next v9 02/15] phylib: Add support for PHYs with broken forced mode Birger Koblitz
2026-09-02 16:57 ` [PATCH net-next v9 03/15] ax88179_178a: Fix endianness of pause watermark register Birger Koblitz
2026-09-02 16:57 ` [PATCH net-next v9 04/15] ax88179_178a: Split driver into library and device specific code Birger Koblitz
2026-09-02 16:57 ` [PATCH net-next v9 05/15] ax88179_178a: Add netdev2data() convenience function Birger Koblitz
2026-09-02 16:57 ` [PATCH net-next v9 06/15] ax88179_178a: Add HW support for AX179A-based chips Birger Koblitz
2026-09-02 20:54 ` Andrew Lunn [this message]
2026-09-02 16:57 ` [PATCH net-next v9 07/15] ax88179_178a: Add EEE configuration support for AX88179A MACs Birger Koblitz
2026-09-02 16:57 ` [PATCH net-next v9 08/15] ax88179_178a: Add EEE configuration support for AX88179A PHYs Birger Koblitz
2026-09-02 16:57 ` [PATCH net-next v9 09/15] ax88179_178a: Add VLAN offload support for AX88179A Birger Koblitz
2026-09-02 16:57 ` [PATCH net-next v9 10/15] ax88179_178a: Add AX179A/AX279 multicast configuration Birger Koblitz
2026-09-02 16:57 ` [PATCH net-next v9 11/15] ax88179_178a: Add Suspend/resume support for AX88179A/772D/279 Birger Koblitz
2026-09-02 16:57 ` [PATCH net-next v9 12/15] ax88179_178a: Add ethtool get_drvinfo Birger Koblitz
2026-09-02 16:57 ` [PATCH net-next v9 13/15] ax88179_178a: Update driver name and information Birger Koblitz
2026-09-02 16:57 ` [PATCH net-next v9 14/15] ax88179_178a: Add support for AX88179A/772D/279 EEPROM access Birger Koblitz
2026-09-02 16:57 ` [PATCH net-next v9 15/15] ax88796b: Add support for AX88772D, AX88179A and AX88279 Birger Koblitz
2026-09-02 20:56 ` 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=b87d751c-f736-4cf9-b3f3-88ae2bc9ade1@lunn.ch \
--to=andrew@lunn.ch \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mail@birger-koblitz.de \
--cc=netdev@vger.kernel.org \
--cc=neuromoments@gmail.com \
--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