From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Sergio Palumbo <palumbo.ser@outlook.it>
Cc: Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.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 net-next] net: sfp: add quirk for ODI DFP-34X-2C2 GPON ONU SFP
Date: Sun, 28 Jan 2024 14:43:24 +0000 [thread overview]
Message-ID: <ZbZoDIPR3O/iei5z@shell.armlinux.org.uk> (raw)
In-Reply-To: <AS1PR03MB81893D69344708C98EE2B470827F2@AS1PR03MB8189.eurprd03.prod.outlook.com>
Oh, a second repost. What's different from the first repost?
On Sun, Jan 28, 2024 at 03:23:06PM +0100, Sergio Palumbo wrote:
> DFP-34X-2C2 is a GPON spf module working at both 1000baseX
> and 2500baseX.
> Setting the module to LAN_SDS_MODE=6 the module is working
> at 2500baseX with auto negotiation see at
> https://hack-gpon.org/ont-odi-realtek-dfp-34x-2c2/
> Unfortunatly the module's PHY is accessible at 1000baseX only.
> ethtool returning:
> Supported ports: [ Fibre ]
> Supported link modes: 1000baseX/Full
>
> After applying the quirk:
> Supported ports: [ Fibre ]
> Supported link modes: 1000baseX/Full
> 2500baseX/Full
> Tested on BANANA PI R3 in OpenWRT v 23.05.2 Kernel 5.15.137
> Tested on sfp to ethernet Media Converter.
> Autonegotiating 1000baseX or 2500baseX according to the
> connected host speed.
>
> This module is existing in 2 versions:
> Vendor = "ODI"
> Vendor = "OEM"
> This is the patch for vendor "ODI"
>
> Patch has been inserted keeping the list in alphabetical order
> first by vendor first and then by part string.
>
> Signed-off-by: Sergio Palumbo <palumbo.ser@outlook.it>
> ---
> drivers/net/phy/sfp.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/net/phy/sfp.c b/drivers/net/phy/sfp.c
> index 3c0028a4af92..410375bc6b94 100644
> --- a/drivers/net/phy/sfp.c
> +++ b/drivers/net/phy/sfp.c
> @@ -495,6 +495,9 @@ static const struct sfp_quirk sfp_quirks[] = {
> // 2500MBd NRZ in their EEPROM
> SFP_QUIRK_M("Lantech", "8330-262D-E", sfp_quirk_2500basex),
>
> + // ODI DFP-34X-2C2 GPON ONU support 2500base-X
> + SFP_QUIRK_M("ODI", "DFP-34X-2C2", sfp_quirk_2500basex),
> +
> SFP_QUIRK_M("UBNT", "UF-INSTANT", sfp_quirk_ubnt_uf_instant),
>
> // Walsun HXSX-ATR[CI]-1 don't identify as copper, and use the
> --
> 2.34.1
>
>
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2024-01-28 14:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-28 14:23 [PATCH net-next] net: sfp: add quirk for ODI DFP-34X-2C2 GPON ONU SFP Sergio Palumbo
2024-01-28 14:43 ` Russell King (Oracle) [this message]
2024-02-02 17:44 ` Sergio Palumbo
2024-02-02 18:03 ` Russell King (Oracle)
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=ZbZoDIPR3O/iei5z@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@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=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=palumbo.ser@outlook.it \
/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).