From: Jonathan Cameron <jonathan.cameron@huawei.com>
To: Pavan Chebbi <pavan.chebbi@broadcom.com>
Cc: <jgg@ziepe.ca>, <michael.chan@broadcom.com>,
<dave.jiang@intel.com>, <saeedm@nvidia.com>,
<davem@davemloft.net>, <corbet@lwn.net>, <edumazet@google.com>,
<gospo@broadcom.com>, <kuba@kernel.org>, <netdev@vger.kernel.org>,
<pabeni@redhat.com>, <andrew+netdev@lunn.ch>,
<selvin.xavier@broadcom.com>, <leon@kernel.org>,
<kalesh-anakkur.purayil@broadcom.com>
Subject: Re: [PATCH net-next v2 4/6] bnxt_en: Create an aux device for fwctl
Date: Tue, 23 Sep 2025 11:56:06 +0100 [thread overview]
Message-ID: <20250923115606.00003c67@huawei.com> (raw)
In-Reply-To: <20250923095825.901529-5-pavan.chebbi@broadcom.com>
On Tue, 23 Sep 2025 02:58:23 -0700
Pavan Chebbi <pavan.chebbi@broadcom.com> wrote:
> Create an additional auxiliary device to support fwctl.
> The next patch will create bnxt_fwctl and bind to this
> device.
>
> Reviewed-by: Andy Gospodarek <gospo@broadcom.com>
> Signed-off-by: Pavan Chebbi <pavan.chebbi@broadcom.com>
Just a few minor comments in here.
> diff --git a/drivers/net/ethernet/broadcom/bnxt/bnxt.h b/drivers/net/ethernet/broadcom/bnxt/bnxt.h
> index b2f139eddfec..1eeea0884e09 100644
> --- a/drivers/net/ethernet/broadcom/bnxt/bnxt.h
> +++ b/drivers/net/ethernet/broadcom/bnxt/bnxt.h
> @@ -2340,6 +2340,8 @@ struct bnxt {
>
> struct bnxt_napi **bnapi;
>
> + struct bnxt_en_dev *edev_fwctl;
> + struct bnxt_aux_priv *aux_priv_fwctl;
> struct bnxt_rx_ring_info *rx_ring;
> struct bnxt_tx_ring_info *tx_ring;
> u16 *tx_ring_map;
> diff --git a/drivers/net/ethernet/broadcom/bnxt/bnxt_ulp.c b/drivers/net/ethernet/broadcom/bnxt/bnxt_ulp.c
> index ecad1947ccb5..c06a9503b551 100644
> --- a/drivers/net/ethernet/broadcom/bnxt/bnxt_ulp.c
> +++ b/drivers/net/ethernet/broadcom/bnxt/bnxt_ulp.c
> +static u32 bnxt_fwctl_aux_dev_alloc_ida(void)
> +{
> + return ida_alloc(&bnxt_fwctl_aux_dev_ids, GFP_KERNEL);
Could maybe add a pointer to the ida to the type specific structure instead of a callback?
Small increase in shared code.
> +}
> +
> +static void bnxt_fwctl_aux_dev_free_ida(struct bnxt_aux_priv *aux_priv)
> +{
> + ida_free(&bnxt_fwctl_aux_dev_ids, aux_priv->id);
> +}
>
> @@ -536,12 +589,27 @@ void bnxt_aux_device_add(struct bnxt *bp, enum bnxt_ulp_auxdev_type auxdev_type)
> aux_dev = bnxt_aux_devices[auxdev_type].get_auxdev(bp);
> rc = auxiliary_device_add(aux_dev);
> if (rc) {
> - netdev_warn(bp->dev, "Failed to add auxiliary device for ROCE\n");
> + netdev_warn(bp->dev, "Failed to add auxiliary device for auxdev type %d\n",
> + auxdev_type);
> auxiliary_device_uninit(aux_dev);
> - bp->flags &= ~BNXT_FLAG_ROCE_CAP;
> + if (auxdev_type == BNXT_AUXDEV_RDMA)
> + bp->flags &= ~BNXT_FLAG_ROCE_CAP;
Same comment as below.
> }
> }
> @@ -611,5 +679,6 @@ void bnxt_aux_device_init(struct bnxt *bp,
> aux_dev_uninit:
> auxiliary_device_uninit(aux_dev);
> exit:
> - bp->flags &= ~BNXT_FLAG_ROCE_CAP;
> + if (auxdev_type == BNXT_AUXDEV_RDMA)
Mixing and matching between a 'type' specific structure and specific
ID based checks normally doesn't scale well if you ever end up adding more
types. I'd suggest moving this to data or a callback in the bnxt_auxdev struture.
> + bp->flags &= ~BNXT_FLAG_ROCE_CAP;
> }
>
next prev parent reply other threads:[~2025-09-23 10:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 9:58 [PATCH net-next v2 0/6] bnxt_fwctl: fwctl for Broadcom Netxtreme devices Pavan Chebbi
2025-09-23 9:58 ` [PATCH net-next v2 1/6] bnxt_en: Move common definitions to include/linux/bnxt/ Pavan Chebbi
2025-09-23 10:35 ` Jonathan Cameron
2025-09-23 16:33 ` Saeed Mahameed
2025-09-23 17:16 ` Pavan Chebbi
2025-09-23 18:00 ` Pavan Chebbi
2025-09-23 9:58 ` [PATCH net-next v2 2/6] bnxt_en: Refactor aux bus functions to be generic Pavan Chebbi
2025-09-23 10:46 ` Jonathan Cameron
2025-09-23 9:58 ` [PATCH net-next v2 3/6] bnxt_en: Make a lookup table for supported aux bus devices Pavan Chebbi
2025-09-23 10:49 ` Jonathan Cameron
2025-09-23 12:21 ` Pavan Chebbi
2025-09-23 9:58 ` [PATCH net-next v2 4/6] bnxt_en: Create an aux device for fwctl Pavan Chebbi
2025-09-23 10:56 ` Jonathan Cameron [this message]
2025-09-23 9:58 ` [PATCH net-next v2 5/6] bnxt_fwctl: Add bnxt fwctl device Pavan Chebbi
2025-09-23 11:17 ` Jonathan Cameron
2025-09-23 12:19 ` Pavan Chebbi
2025-09-23 20:00 ` [External] : " ALOK TIWARI
2025-09-24 22:31 ` Dave Jiang
2025-09-25 4:31 ` Pavan Chebbi
2025-09-25 15:46 ` Dave Jiang
2025-09-25 18:17 ` Dave Jiang
2025-09-26 4:00 ` Pavan Chebbi
2025-09-23 9:58 ` [PATCH net-next v2 6/6] bnxt_fwctl: Add documentation entries Pavan Chebbi
2025-09-23 10:31 ` Jonathan Cameron
2025-09-24 22:40 ` Dave Jiang
2025-09-23 16:25 ` [PATCH net-next v2 0/6] bnxt_fwctl: fwctl for Broadcom Netxtreme devices Saeed Mahameed
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=20250923115606.00003c67@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=andrew+netdev@lunn.ch \
--cc=corbet@lwn.net \
--cc=dave.jiang@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gospo@broadcom.com \
--cc=jgg@ziepe.ca \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=saeedm@nvidia.com \
--cc=selvin.xavier@broadcom.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;
as well as URLs for NNTP newsgroup(s).