From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Chris Morgan <macromorgan@hotmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Chris Morgan <macroalpha82@gmail.com>,
netdev@vger.kernel.org, hkallweit1@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com
Subject: Re: [PATCH V2] net: sfp: add quirk for Potron SFP+ XGSPON ONU Stick
Date: Fri, 6 Jun 2025 17:51:01 +0100 [thread overview]
Message-ID: <aEMcdcnY6CwEvOBZ@shell.armlinux.org.uk> (raw)
In-Reply-To: <SN6PR1901MB46541BA6488F73EB49EBCDDFA56EA@SN6PR1901MB4654.namprd19.prod.outlook.com>
On Fri, Jun 06, 2025 at 09:44:48AM -0500, Chris Morgan wrote:
> On Fri, Jun 06, 2025 at 02:53:46PM +0200, Andrew Lunn wrote:
> > On Thu, Jun 05, 2025 at 09:22:03PM -0500, Chris Morgan wrote:
> > > From: Chris Morgan <macromorgan@hotmail.com>
> > >
> > > Add quirk for Potron SFP+ XGSPON ONU Stick (YV SFP+ONT-XGSPON).
> > >
> > > This device uses pins 2 and 7 for UART communication, so disable
> > > TX_FAULT and LOS. Additionally as it is an embedded system in an
> > > SFP+ form factor provide it enough time to fully boot before we
> > > attempt to use it.
> > >
> > > https://www.potrontec.com/index/index/list/cat_id/2.html#11-83
> > > https://pon.wiki/xgs-pon/ont/potron-technology/x-onu-sfpp/
> > >
> > > Signed-off-by: Chris Morgan <macromorgan@hotmail.com>
> > > ---
> > >
> > > Changes since V1:
> > > - Call sfp_fixup_ignore_tx_fault() and sfp_fixup_ignore_los() instead
> > > of setting the state_hw_mask.
> >
> > https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html
> >
> > You are supposed to wait 24 hours before posting a new version. We are
> > also in the merge window at the moment, so please post patches as RFC.
>
> Sorry, I'll make sure to slow down the commits moving forward.
>
> >
> > Russell asked the question, what does the SFP report about soft LOS in
> > its EEPROM? Does it correctly indicate it supports soft LOS? Does it
> > actually support soft LOS? Do we need to force on soft LOS? Maybe we
> > need a helper sfp_fixup_force_soft_los()?
>
> So I'm a bit out of my element here and not sure how to check that. I
> bought this module and had a hell of a time getting it to work on my
> Banana Pi R4 because of the UART triggering repeated tx faults. After
> applying these updates I was able to get it to work, so I figured it
> would be a courtesy to upstream these for others not to suffer. I was
> going to get this upstreamed, then request OpenWRT backport the fix,
> then move this device to replace my current router (which might be why
> I am guilty of rushing, sorry again). That said, I'm not sure how to
> check if the module supports soft LOS or not. I did a dump with
> ethtool -m but didn't see any references to LOS. Is there a bit on the
> EEPROM I can check?
Please send me (privately) the binary of:
ethtool -m ethX raw on > ethX.eeprom.bin
so I can see fully what it's reporting - I should then be able to make
further suggestions.
Thanks.
--
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:[~2025-06-06 16:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 2:22 [PATCH V2] net: sfp: add quirk for Potron SFP+ XGSPON ONU Stick Chris Morgan
2025-06-06 12:53 ` Andrew Lunn
2025-06-06 14:44 ` Chris Morgan
2025-06-06 15:33 ` Andrew Lunn
2025-06-06 18:54 ` Chris Morgan
2025-06-06 21:21 ` Russell King (Oracle)
2025-06-06 22:32 ` Chris Morgan
2025-06-06 22:47 ` Russell King (Oracle)
2025-06-11 3:43 ` Chris Morgan
2025-06-11 8:31 ` Russell King (Oracle)
2025-06-06 16:51 ` Russell King (Oracle) [this message]
2025-06-06 16:47 ` 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=aEMcdcnY6CwEvOBZ@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=macroalpha82@gmail.com \
--cc=macromorgan@hotmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.