[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d02e3393-bd0f-419c-83be-f98a4e794b59@lunn.ch>
Date: Mon, 24 Jun 2024 21:01:22 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Danielle Ratson <danieller@...dia.com>
Cc: netdev@...r.kernel.org, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, corbet@....net,
linux@...linux.org.uk, sdf@...gle.com, kory.maincent@...tlin.com,
maxime.chevallier@...tlin.com, vladimir.oltean@....com,
przemyslaw.kitszel@...el.com, ahmed.zaki@...el.com,
richardcochran@...il.com, shayagr@...zon.com,
paul.greenwalt@...el.com, jiri@...nulli.us,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
mlxsw@...dia.com, idosch@...dia.com, petrm@...dia.com
Subject: Re: [PATCH net-next v7 1/9] ethtool: Add ethtool operation to write
to a transceiver module EEPROM
On Mon, Jun 24, 2024 at 08:51:51PM +0300, Danielle Ratson wrote:
> From: Ido Schimmel <idosch@...dia.com>
>
> Ethtool can already retrieve information from a transceiver module
> EEPROM by invoking the ethtool_ops::get_module_eeprom_by_page operation.
> Add a corresponding operation that allows ethtool to write to a
> transceiver module EEPROM.
>
> The new write operation is purely an in-kernel API and is not exposed to
> user space.
>
> The purpose of this operation is not to enable arbitrary read / write
> access, but to allow the kernel to write to specific addresses as part
> of transceiver module firmware flashing. In the future, more
> functionality can be implemented on top of these read / write
> operations.
>
> Adjust the comments of the 'ethtool_module_eeprom' structure as it is
> no longer used only for read access.
>
> Signed-off-by: Ido Schimmel <idosch@...dia.com>
> Signed-off-by: Danielle Ratson <danieller@...dia.com>
> Reviewed-by: Petr Machata <petrm@...dia.com>
Reviewed-by: Andrew Lunn <andrew@...n.ch>
Andrew
Powered by blists - more mailing lists