From: Andrew Lunn <andrew@lunn.ch>
To: FUJITA Tomonori <fujita.tomonori@gmail.com>
Cc: netdev@vger.kernel.org, rust-for-linux@vger.kernel.org,
tmgross@umich.edu, miguel.ojeda.sandonis@gmail.com,
benno.lossin@proton.me, aliceryhl@google.com
Subject: Re: [PATCH net-next v3 0/6] net: phy: add Applied Micro QT2025 PHY driver
Date: Mon, 5 Aug 2024 03:10:50 +0200 [thread overview]
Message-ID: <174bf437-5adf-4ebf-b909-036d6443dcf5@lunn.ch> (raw)
In-Reply-To: <20240804233835.223460-1-fujita.tomonori@gmail.com>
On Mon, Aug 05, 2024 at 08:38:29AM +0900, FUJITA Tomonori wrote:
> This patchset adds a PHY driver for Applied Micro Circuits Corporation
> QT2025.
>
> The first patch adds Rust equivalent to include/linux/sizes.h, makes
> code more readable. The 2-5th patches update the PHYLIB Rust bindings.
>
> QT2025 PHY support was implemented as a part of an Ethernet driver for
> Tehuti Networks TN40xx chips. Multiple vendors (DLink, Asus, Edimax,
> QNAP, etc) developed adapters based on TN40xx chips. Tehuti Networks
> went out of business and the driver wasn't merged into mainline. But
> it's still distributed with some of the hardware (and also available
> on some vendor sites).
>
> The original driver handles multiple PHY hardware (AMCC QT2025, TI
> TLK10232, Aqrate AQR105, and Marvell MV88X3120, MV88X3310, and
> MV88E2010). I divided the original driver into MAC and PHY drivers and
> implemented a QT2025 PHY driver in Rust.
>
> The MAC driver for Tehuti Networks TN40xx chips was already merged in
> 6.11-rc1. The MAC and this PHY drivers have been tested with Edimax
> EN-9320SFP+ 10G network adapter.
Sorry about being slow reviewing this. I will get to it by the middle
of the week.
Andrew
next prev parent reply other threads:[~2024-08-05 1:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-04 23:38 [PATCH net-next v3 0/6] net: phy: add Applied Micro QT2025 PHY driver FUJITA Tomonori
2024-08-04 23:38 ` [PATCH net-next v3 1/6] rust: sizes: add commonly used constants FUJITA Tomonori
2024-08-16 0:37 ` Andrew Lunn
2024-08-16 5:21 ` FUJITA Tomonori
2024-08-04 23:38 ` [PATCH net-next v3 2/6] rust: net::phy support probe callback FUJITA Tomonori
2024-08-16 0:40 ` Andrew Lunn
2024-08-16 5:21 ` FUJITA Tomonori
2024-08-04 23:38 ` [PATCH net-next v3 3/6] rust: net::phy implement AsRef<kernel::device::Device> trait FUJITA Tomonori
2024-08-16 0:41 ` Andrew Lunn
2024-08-04 23:38 ` [PATCH net-next v3 4/6] rust: net::phy unified read/write API for C22 and C45 registers FUJITA Tomonori
2024-08-16 1:09 ` Andrew Lunn
2024-08-16 5:27 ` FUJITA Tomonori
2024-08-04 23:38 ` [PATCH net-next v3 5/6] rust: net::phy unified genphy_read_status function " FUJITA Tomonori
2024-08-16 1:19 ` Andrew Lunn
2024-08-16 5:30 ` FUJITA Tomonori
2024-08-16 20:41 ` Andrew Lunn
2024-08-04 23:38 ` [PATCH net-next v3 6/6] net: phy: add Applied Micro QT2025 PHY driver FUJITA Tomonori
2024-08-16 1:45 ` Andrew Lunn
2024-08-16 6:17 ` FUJITA Tomonori
2024-08-16 20:47 ` Andrew Lunn
2024-08-17 4:50 ` FUJITA Tomonori
2024-08-05 1:10 ` Andrew Lunn [this message]
2024-08-14 2:57 ` [PATCH net-next v3 0/6] " 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=174bf437-5adf-4ebf-b909-036d6443dcf5@lunn.ch \
--to=andrew@lunn.ch \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=fujita.tomonori@gmail.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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