From: Hariprasad Kelam <hkelam@marvell.com>
To: Lorenz Brun <lorenz@brun.one>
Cc: Igor Russkikh <irusskikh@marvell.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] net: atlantic: support reading SFP module info
Date: Fri, 18 Oct 2024 22:38:40 +0530 [thread overview]
Message-ID: <ZxKWGBAMsVqsnS87@test-OptiPlex-Tower-Plus-7010> (raw)
In-Reply-To: <20241018154741.2565618-1-lorenz@brun.one>
On 2024-10-18 at 21:17:38, Lorenz Brun (lorenz@brun.one) wrote:
> Add support for reading SFP module info and digital diagnostic
> monitoring data if supported by the module. The only Aquantia
> controller without an integrated PHY is the AQC100 which belongs to
> the B0 revision, that's why it's only implemented there.
>
> The register information was extracted from a diagnostic tool made
> publicly available by Dell, but all code was written from scratch by me.
>
> This has been tested to work with a variety of both optical and direct
> attach modules I had lying around and seems to work fine with all of
> them, including the diagnostics if supported by an optical module.
> All tests have been done with an AQC100 on an TL-NT521F card on firmware
> version 3.1.121 (current at the time of this patch).
>
> Signed-off-by: Lorenz Brun <lorenz@brun.one>
> ---
Since this is not a fix, please submit this patch to "net-next"
tree by changing the subject prefix.
prev parent reply other threads:[~2024-10-18 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 15:47 [PATCH v3] net: atlantic: support reading SFP module info Lorenz Brun
2024-10-18 17:08 ` Hariprasad Kelam [this message]
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=ZxKWGBAMsVqsnS87@test-OptiPlex-Tower-Plus-7010 \
--to=hkelam@marvell.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=irusskikh@marvell.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenz@brun.one \
--cc=netdev@vger.kernel.org \
--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