From: Simon Horman <horms@kernel.org>
To: Lee Trager <lee@trager.us>
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>,
Kalesh AP <kalesh-anakkur.purayil@broadcom.com>,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 2/2] eth: fbnic: Add devlink dev flash support
Date: Tue, 12 Nov 2024 17:42:43 +0000 [thread overview]
Message-ID: <20241112174243.GU4507@kernel.org> (raw)
In-Reply-To: <20241111043058.1251632-3-lee@trager.us>
On Sun, Nov 10, 2024 at 08:28:42PM -0800, 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
...
> +/**
> + * fbnic_flash_component - Flash a component of the QSPI
> + * @context: PLDM FW update structure
> + * @component: The component table to send to FW
> + *
> + * Map contents of component and make it available for FW to download
> + * so that it can update the contents of the QSPI Flash.
> + *
> + * Return: zero on success
> + * negative error code on failure
> + */
> +static int fbnic_flash_component(struct pldmfw *context,
> + struct pldmfw_component *component)
> +{
> + const u8 *data = component->component_data;
> + u32 size = component->component_size;
> + struct fbnic_fw_completion *fw_cmpl;
> + struct device *dev = context->dev;
> + struct pci_dev *pdev = to_pci_dev(dev);
> + u16 id = component->identifier;
> + const char *component_name;
> + int retries = 2;
> + int err;
> +
> + struct devlink *devlink;
> + struct fbnic_dev *fbd;
Hi Lee,
Please consider arranging local variables in reverse xmas tree order -
longest line to shortest. Without any blank lines. I think that in this
case that could be:
const u8 *data = component->component_data;
u32 size = component->component_size;
struct fbnic_fw_completion *fw_cmpl;
struct device *dev = context->dev;
u16 id = component->identifier;
const char *component_name;
struct devlink *devlink;
struct fbnic_dev *fbd;
struct pci_dev *pdev;
int retries = 2;
int err;
N.B. pdev is initialised below.
> +
> + switch (id) {
> + case QSPI_SECTION_CMRT:
> + component_name = "boot1";
> + break;
> + case QSPI_SECTION_CONTROL_FW:
> + component_name = "boot2";
> + break;
> + case QSPI_SECTION_OPTION_ROM:
> + component_name = "option-rom";
> + break;
> + default:
> + dev_err(dev, "Unknown component ID %u\n", id);
> + return -EINVAL;
> + }
> +
> + fw_cmpl = kzalloc(sizeof(*fw_cmpl), GFP_KERNEL);
> + if (!fw_cmpl)
> + return -ENOMEM;
> +
> + pdev = to_pci_dev(dev);
> + fbd = pci_get_drvdata(pdev);
> + devlink = priv_to_devlink(fbd);
...
prev parent reply other threads:[~2024-11-12 17:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 4:28 [PATCH net-next v3 0/2] eth: fbnic: Add devlink dev flash support Lee Trager
2024-11-11 4:28 ` [PATCH net-next v3 1/2] eth: fbnic: Add mailbox support for PLDM updates Lee Trager
2024-11-11 4:28 ` [PATCH net-next v3 2/2] eth: fbnic: Add devlink dev flash support Lee Trager
2024-11-12 3:19 ` Jakub Kicinski
2024-11-12 17:42 ` Simon Horman [this message]
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=20241112174243.GU4507@kernel.org \
--to=horms@kernel.org \
--cc=alexanderduyck@fb.com \
--cc=andrew+netdev@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=lee@trager.us \
--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 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.