From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Chris Morgan <macroalpha82@gmail.com>
Cc: netdev@vger.kernel.org, andrew@lunn.ch, hkallweit1@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, Chris Morgan <macromorgan@hotmail.com>
Subject: Re: [PATCH v3] net: sfp: add quirk for Potron SFP+ XGSPON ONU Stick
Date: Mon, 16 Jun 2025 10:38:29 +0100 [thread overview]
Message-ID: <aE_mFWgIuuIn06E3@shell.armlinux.org.uk> (raw)
In-Reply-To: <20250613171002.50749-1-macroalpha82@gmail.com>
On Fri, Jun 13, 2025 at 12:10:02PM -0500, Chris Morgan wrote:
> @@ -409,7 +414,19 @@ static void sfp_fixup_halny_gsfp(struct sfp *sfp)
> * these are possibly used for other purposes on this
> * module, e.g. a serial port.
> */
> - sfp->state_hw_mask &= ~(SFP_F_TX_FAULT | SFP_F_LOS);
> + sfp_fixup_ignore_hw(sfp, (SFP_F_TX_FAULT | SFP_F_LOS));
> +}
> +
> +static void sfp_fixup_potron(struct sfp *sfp)
> +{
> + /*
> + * The TX_FAULT and LOS pins on this device are used for serial
> + * communication, so ignore them. Additionally, provide extra
> + * time for this device to fully start up.
> + */
> +
> + sfp_fixup_long_startup(sfp);
> + sfp_fixup_ignore_hw(sfp, (SFP_F_TX_FAULT | SFP_F_LOS));
There's no need for parens around the second argument to
sfp_fixup_ignore_hw() - the bitwise OR is unambiguous.
Apart from that, the patch looks fine, 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-16 9:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 17:10 [PATCH v3] net: sfp: add quirk for Potron SFP+ XGSPON ONU Stick Chris Morgan
2025-06-16 9:38 ` Russell King (Oracle) [this message]
2025-06-16 16:21 ` Chris Morgan
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=aE_mFWgIuuIn06E3@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.