Netdev List
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: FUJITA Tomonori <fujita.tomonori@gmail.com>
Cc: netdev@vger.kernel.org, andrew@lunn.ch, horms@kernel.org
Subject: Re: [PATCH net-next v2 0/6] add ethernet driver for Tehuti Networks TN40xx chips
Date: Thu, 25 Apr 2024 13:32:50 +0200	[thread overview]
Message-ID: <Zio_YgfX9SO9DHc4@nanopsycho> (raw)
In-Reply-To: <20240425010354.32605-1-fujita.tomonori@gmail.com>

Thu, Apr 25, 2024 at 03:03:48AM CEST, fujita.tomonori@gmail.com wrote:
>This patchset adds a new 10G ethernet driver for Tehuti Networks
>TN40xx chips. Note in mainline, there is a driver for Tehuti Networks
>(drivers/net/ethernet/tehuti/tehuti.[hc]), which supports TN30xx
>chips.
>
>Multiple vendors (DLink, Asus, Edimax, QNAP, etc) developed adapters
>based on TN40xx chips. Tehuti Networks went out of business but the
>drivers are still distributed under GPL2 with some of the hardware
>(and also available on some sites). With some changes, I try to
>upstream this driver with a new PHY driver in Rust.
>
>The major change is replacing a PHY abstraction layer with
>PHYLIB. TN40xx chips are used with various PHY hardware (AMCC QT2025,
>TI TLK10232, Aqrate AQR105, and Marvell MV88X3120, MV88X3310, and
>MV88E2010). So the original driver has the own PHY abstraction layer
>to handle them.
>
>I've also been working on a new PHY driver for QT2025 in Rust [1]. For
>now, I enable only adapters using QT2025 PHY in the PCI ID table of
>this driver. I've tested this driver and the QT2025 PHY driver with
>Edimax EN-9320 10G adapter. In mainline, there are PHY drivers for
>AQR105 and Marvell PHYs, which could work for some TN40xx adapters
>with this driver.
>
>The other changes are replacing the embedded firmware in a header file
>with the firmware APIs, handling dma mapping errors, removing many
>ifdef, fixing lots of style issues, etc.
>
>To make reviewing easier, this patchset has only basic functions. Once
>merged, I'll submit features like ethtool support.
>
>v2:
>- split mdio patch into mdio and phy support
>- add phylink support
>- clean up mdio read/write
>- use the standard bit operation macros
>- use upper_32/lower_32_bits macro
>- use tn40_ prefix instead of bdx_
>- fix Sparse errors
>- fix compiler warnings
>- fix style issues
>v1: https://lore.kernel.org/netdev/20240415104352.4685-1-fujita.tomonori@gmail.com/
>
>[1] https://lore.kernel.org/netdev/20240415104701.4772-1-fujita.tomonori@gmail.com/
>
>FUJITA Tomonori (6):
>  net: tn40xx: add pci driver for Tehuti Networks TN40xx chips
>  net: tn40xx: add register defines
>  net: tn40xx: add basic Tx handling
>  net: tn40xx: add basic Rx handling
>  net: tn40xx: add mdio bus support
>  net: tn40xx: add PHYLIB support

In all patches, could you please maintain prefixes tn40_/TN40_ for all
function, struct and define names?

  parent reply	other threads:[~2024-04-25 11:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-25  1:03 [PATCH net-next v2 0/6] add ethernet driver for Tehuti Networks TN40xx chips FUJITA Tomonori
2024-04-25  1:03 ` [PATCH net-next v2 1/6] net: tn40xx: add pci " FUJITA Tomonori
2024-04-25 12:54   ` Andrew Lunn
2024-04-25 13:37     ` FUJITA Tomonori
2024-04-25  1:03 ` [PATCH net-next v2 2/6] net: tn40xx: add register defines FUJITA Tomonori
2024-04-25  1:03 ` [PATCH net-next v2 3/6] net: tn40xx: add basic Tx handling FUJITA Tomonori
2024-04-25  1:03 ` [PATCH net-next v2 4/6] net: tn40xx: add basic Rx handling FUJITA Tomonori
2024-04-25  1:03 ` [PATCH net-next v2 5/6] net: tn40xx: add mdio bus support FUJITA Tomonori
2024-04-25  1:03 ` [PATCH net-next v2 6/6] net: tn40xx: add PHYLIB support FUJITA Tomonori
2024-04-25 11:32 ` Jiri Pirko [this message]
2024-04-25 13:40   ` [PATCH net-next v2 0/6] add ethernet driver for Tehuti Networks TN40xx chips FUJITA Tomonori

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=Zio_YgfX9SO9DHc4@nanopsycho \
    --to=jiri@resnulli.us \
    --cc=andrew@lunn.ch \
    --cc=fujita.tomonori@gmail.com \
    --cc=horms@kernel.org \
    --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