From: Simon Horman <horms@kernel.org>
To: Danielle Ratson <danieller@nvidia.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, yuehaibing@huawei.com,
linux-kernel@vger.kernel.org, petrm@nvidia.com,
Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH net-next v2 2/2] net: ethtool: Add support for writing firmware blocks using EPL payload
Date: Wed, 11 Sep 2024 08:32:34 +0100 [thread overview]
Message-ID: <20240911073234.GJ572255@kernel.org> (raw)
In-Reply-To: <20240910090217.3044324-3-danieller@nvidia.com>
+ Andrew Lunn
On Tue, Sep 10, 2024 at 12:02:17PM +0300, Danielle Ratson wrote:
> In the CMIS specification for pluggable modules, LPL (Local Payload) and
> EPL (Extended Payload) are two types of data payloads used for managing
> various functions and features of the module.
>
> EPL payloads are used for more complex and extensive management
> functions that require a larger amount of data, so writing firmware
> blocks using EPL is much more efficient.
>
> Currently, only LPL payload is supported for writing firmware blocks to
> the module.
>
> Add support for writing firmware block using EPL payload, both to
> support modules that supports only EPL write mechanism, and to optimize
> the flashing process of modules that support LPL and EPL.
>
> Signed-off-by: Danielle Ratson <danieller@nvidia.com>
> Reviewed-by: Petr Machata <petrm@nvidia.com>
> ---
>
> Notes:
> v2:
> * Initialize the variable 'bytes_written' before the first
> iteration.
Hi Danielle,
Thanks for the update. From a doing-what-it-says-on-the-wrapper
perspective, this looks good to me.
Reviewed-by: Simon Horman <horms@kernel.org>
I do note that there were some questions from Andrew Lunn (CCed) in v1
regarding the size of transfers over the bus. I see that you responded to
that. Thanks! But I do wonder if he has any further comments.
https://lore.kernel.org/all/DM6PR12MB45163C3543368036C03B6E05D8982@DM6PR12MB4516.namprd12.prod.outlook.com/
...
next prev parent reply other threads:[~2024-09-11 7:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 9:02 [PATCH net-next v2 0/2] ethtool: Add support for writing firmware Danielle Ratson
2024-09-10 9:02 ` [PATCH net-next v2 1/2] net: ethtool: Add new parameters and a function to support EPL Danielle Ratson
2024-09-11 7:32 ` Simon Horman
2024-09-10 9:02 ` [PATCH net-next v2 2/2] net: ethtool: Add support for writing firmware blocks using EPL payload Danielle Ratson
2024-09-11 7:32 ` Simon Horman [this message]
2024-09-11 12:26 ` Andrew Lunn
2024-09-11 15:41 ` Danielle Ratson
2024-09-11 17:38 ` Andrew Lunn
2024-09-13 7:29 ` Danielle Ratson
2024-09-15 17:17 ` [PATCH net-next v2 0/2] ethtool: Add support for writing firmware 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=20240911073234.GJ572255@kernel.org \
--to=horms@kernel.org \
--cc=andrew@lunn.ch \
--cc=danieller@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=yuehaibing@huawei.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.