From: Andrew Lunn <andrew@lunn.ch>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: "Jonas Jelonek" <jelonek.jonas@gmail.com>,
"Russell King" <linux@armlinux.org.uk>,
"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,
"Bjørn Mork" <bjorn@mork.no>
Subject: Re: [PATCH net-next v5] net: sfp: extend SMBus support
Date: Fri, 16 Jan 2026 15:25:50 +0100 [thread overview]
Message-ID: <fe1bf7b6-d024-447c-a672-e84f4e77f8d7@lunn.ch> (raw)
In-Reply-To: <fcf7b3f2-eaf3-4da6-ab9a-a83acc9692b0@bootlin.com>
> > Is there a use case for odd lengths? Apart from 1.
>
> There's sfp_cotsworks_fixup_check() that does a 3-byte access :
>
> id->base.phys_id = SFF8024_ID_SFF_8472;
> id->base.phys_ext_id = SFP_PHYS_EXT_ID_SFP;
> id->base.connector = SFF8024_CONNECTOR_LC;
> sfp_write(sfp, false, SFP_PHYS_ID, &id->base, 3);
Ah, fixing those broken cotsworks PHYs.
> It may be possible to turn that into 2 2-byte accesses if we write
>
> id->base.phys_id = SFF8024_ID_SFF_8472;
> id->base.phys_ext_id = SFP_PHYS_EXT_ID_SFP;
>
> and then
>
> id->base.phys_ext_id = SFP_PHYS_EXT_ID_SFP;
> id->base.connector = SFF8024_CONNECTOR_LC;
Or just don't bother fixing the EEPROM, leave it broken, but use the
corrected values internally.
> But let's first figure-out if word-only smbus are really a thing
Some grep foo on /drivers/i2c/busses might answer that.
Andrew
next prev parent reply other threads:[~2026-01-16 14:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 11:31 [PATCH net-next v5] net: sfp: extend SMBus support Jonas Jelonek
2026-01-16 13:23 ` Maxime Chevallier
2026-01-16 13:43 ` Jonas Jelonek
2026-01-16 14:00 ` Maxime Chevallier
2026-01-16 14:07 ` Andrew Lunn
2026-01-16 14:16 ` Maxime Chevallier
2026-01-16 14:25 ` Andrew Lunn [this message]
2026-01-18 9:43 ` Jonas Jelonek
2026-01-18 10:08 ` Russell King (Oracle)
2026-01-18 15:36 ` Andrew Lunn
2026-01-18 15:39 ` Andrew Lunn
2026-01-22 10:14 ` Jonas Jelonek
2026-01-22 16:04 ` Andrew Lunn
2026-01-22 16:22 ` Russell King (Oracle)
2026-01-16 13:57 ` Russell King (Oracle)
2026-01-19 19:41 ` [net-next,v5] " Jakub Kicinski
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=fe1bf7b6-d024-447c-a672-e84f4e77f8d7@lunn.ch \
--to=andrew@lunn.ch \
--cc=bjorn@mork.no \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=jelonek.jonas@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox