mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lee Trager <lee@trager.us>
To: Simon Horman <horms@kernel.org>
Cc: Alexander Duyck <alexanderduyck@fb.com>,
	Jakub Kicinski <kuba@kernel.org>,
	kernel-team@meta.com, "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>, Jonathan Corbet <corbet@lwn.net>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	Sanman Pradhan <sanmanpradhan@meta.com>,
	Al Viro <viro@zeniv.linux.org.uk>,
	Mohsin Bashir <mohsin.bashr@gmail.com>,
	netdev@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 2/2] eth: fbnic: Add devlink dev flash support
Date: Fri, 25 Oct 2024 15:32:32 -0700	[thread overview]
Message-ID: <13229808-dde5-4805-b908-ce65c8b342b4@trager.us> (raw)
In-Reply-To: <20241024091032.GI402847@kernel.org>


On 10/24/24 2:10 AM, Simon Horman wrote:
> On Mon, Oct 21, 2024 at 06:42:24PM -0700, Lee Trager wrote:
>> fbnic supports updating firmware using a PLDM image signed and distributed
>> by Meta. PLDM images are written into stored flashed. Flashing does not
>> interrupt operation.
>>
>> On host reboot the newly flashed UEFI driver will be used. To run new
>> control or cmrt firmware the NIC must be power cycled.
>>
>> Signed-off-by: Lee Trager <lee@trager.us>
> ...
>
>> diff --git a/drivers/net/ethernet/meta/fbnic/fbnic_devlink.c b/drivers/net/ethernet/meta/fbnic/fbnic_devlink.c
> ...
>
>> @@ -109,8 +110,274 @@ static int fbnic_devlink_info_get(struct devlink *devlink,
>>   	return 0;
>>   }
>>
>> +/**
>> + * fbnic_send_package_data - Send record package data to firmware
>> + * @context: PLDM FW update structure
>> + * @data: pointer to the package data
>> + * @length: length of the package data
>> + *
>> + * Send a copy of the package data associated with the PLDM record matching
>> + * this device to the firmware.
>> + *
>> + * Return: zero on success
>> + *	    negative error code on failure
>> + */
>> +static int fbnic_send_package_data(struct pldmfw *context, const u8 *data,
>> +				   u16 length)
>> +{
>> +	struct device *dev = context->dev;
>> +
>> +	/* Temp placeholder required by devlink */
>> +	dev_info(dev,
>> +		 "Sending %u bytes of PLDM record package data to firmware\n",
>> +		 length);
> Could you clarify what is meant by "Temp placeholder" here and in
> fbnic_send_component_table(). And what plans there might be for
> a non-temporary solution.

Temp placeholder may not have been the best wording here. pldmfw 
requires all ops to be defined as they are always called[1] when 
updating. fbnic has an info message here so its doing something but we 
have no current plans to expand on fbnic_send_package_data nor 
fbnic_finalize_update.

[1] 
https://elixir.bootlin.com/linux/v6.12-rc4/source/lib/pldmfw/pldmfw.c#L723

>
>> +
>> +	return 0;
>> +}
>> +
>> +/**
>> + * fbnic_send_component_table - Send PLDM component table to the firmware
>> + * @context: PLDM FW update structure
>> + * @component: The component to send
>> + * @transfer_flag: Flag indication location in component tables
>> + *
>> + * Read relevant data from component table and forward it to the firmware.
>> + * Check response to verify if the firmware indicates that it wishes to
>> + * proceed with the update.
>> + *
>> + * Return: zero on success
>> + *	    negative error code on failure
>> + */
>> +static int fbnic_send_component_table(struct pldmfw *context,
>> +				      struct pldmfw_component *component,
>> +				      u8 transfer_flag)
>> +{
>> +	struct device *dev = context->dev;
>> +	u16 id = component->identifier;
>> +	u8 test_string[80];
>> +
>> +	switch (id) {
>> +	case QSPI_SECTION_CMRT:
>> +	case QSPI_SECTION_CONTROL_FW:
>> +	case QSPI_SECTION_OPTION_ROM:
>> +		break;
>> +	default:
>> +		dev_err(dev, "Unknown component ID %u\n", id);
>> +		return -EINVAL;
>> +	}
>> +
>> +	dev_dbg(dev, "Sending PLDM component table to firmware\n");
>> +
>> +	/* Temp placeholder */
>> +	strscpy(test_string, component->version_string,
>> +		min_t(u8, component->version_len, 79));
>> +	dev_info(dev, "PLDMFW: Component ID: %u version %s\n",
>> +		 id, test_string);
>> +
>> +	return 0;
>> +}
> ...
>

  reply	other threads:[~2024-10-25 22:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-12  2:34 [PATCH net-next 0/2] " Lee Trager
2024-10-12  2:34 ` [PATCH net-next 1/2] eth: fbnic: Add mailbox support for PLDM updates Lee Trager
2024-10-14 11:05   ` Vadim Fedorenko
2024-10-12  2:34 ` [PATCH net-next 2/2] eth: fbnic: Add devlink dev flash support Lee Trager
2024-10-14 11:18   ` Vadim Fedorenko
2024-10-15 10:43     ` Simon Horman
2024-10-18 22:48       ` Lee Trager
2024-10-19  9:34         ` Simon Horman
2024-10-22  1:37 ` [PATCH net-next v2 0/2] " Lee Trager
2024-10-22  1:37 ` [PATCH net-next v2 1/2] eth: fbnic: Add mailbox support for PLDM updates Lee Trager
2024-10-26 15:12   ` Simon Horman
2024-10-22  1:42 ` [PATCH net-next v2 2/2] eth: fbnic: Add devlink dev flash support Lee Trager
2024-10-24  9:10   ` Simon Horman
2024-10-25 22:32     ` Lee Trager [this message]
2024-10-26 15:12       ` Simon Horman

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=13229808-dde5-4805-b908-ce65c8b342b4@trager.us \
    --to=lee@trager.us \
    --cc=alexanderduyck@fb.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kernel-team@meta.com \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mohsin.bashr@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sanmanpradhan@meta.com \
    --cc=viro@zeniv.linux.org.uk \
    /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

all inboxes | Powered by JetHome®