public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "Jonas Jelonek" <jelonek.jonas@gmail.com>,
	"Maxime Chevallier" <maxime.chevallier@bootlin.com>,
	"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: Thu, 22 Jan 2026 16:22:44 +0000	[thread overview]
Message-ID: <aXJO1GMQp2Z3UVmf@shell.armlinux.org.uk> (raw)
In-Reply-To: <92538fd0-aa1f-429b-9984-89bcd46e2a28@lunn.ch>

On Thu, Jan 22, 2026 at 05:04:29PM +0100, Andrew Lunn wrote:
> On Thu, Jan 22, 2026 at 11:14:03AM +0100, Jonas Jelonek wrote:
> > Hi Andrew,
> > 
> > On 18.01.26 16:39, Andrew Lunn wrote:
> > > On Sun, Jan 18, 2026 at 10:43:12AM +0100, Jonas Jelonek wrote:
> > >> Hi,
> > >>
> > >> On 16.01.26 15:25, Andrew Lunn wrote:
> > >>>> But let's first figure-out if word-only smbus are really a thing
> > >>> Some grep foo on /drivers/i2c/busses might answer that.
> > >> Did that and haven't found any driver in mainline which is word-only.
> > >> All drivers with word access capability have byte access too.
> > > So for the moment, maybe add a WARN_ON() for an I2C bus that only
> > > supports word access, and we can deal with it only if we ever get a
> > > report of it firing.
> > 
> > Should it just have a WARN_ON and continue (so it may work in some cases)
> > or fail at that point? 
> 
> I guess doing a word access when a byte access is wanted will either
> work, or immediately kill the I2C bus because the SFP is broken and
> only supports byte access, and the dead I2C bus will cause a cascade
> of errors.

RTL8672 / RTL9601C based xPON SFPs are an example, they need single
byte access.

Conversely, we have the Nokia 3FE46541AA GPON module which locks up
the I2C bus if one reads the EEPROM (i2c 0x50) offset 0x51 using a
single byte read.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!

  reply	other threads:[~2026-01-22 16:22 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
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) [this message]
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=aXJO1GMQp2Z3UVmf@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=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=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