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 3/6] bnxt_en: Make a lookup table for supported aux bus devices
Date: Tue, 23 Sep 2025 11:49:35 +0100 [thread overview]
Message-ID: <20250923114935.00001730@huawei.com> (raw)
In-Reply-To: <20250923095825.901529-4-pavan.chebbi@broadcom.com>
On Tue, 23 Sep 2025 02:58:22 -0700
Pavan Chebbi <pavan.chebbi@broadcom.com> wrote:
> We could maintain a look up table of aux bus devices supported
> by bnxt. This way, the aux bus init/add/uninit/del could have
> generic code to work on any of bnxt's aux devices.
>
> Reviewed-by: Andy Gospodarek <gospo@broadcom.com>
> Signed-off-by: Pavan Chebbi <pavan.chebbi@broadcom.com>
Ah. Ok. This does make it more generic. Smash this and patch 2 together
so we don't have the intermediate state where stuff is partly generic.
Key is perhaps to remember that reviewers almost always end up looking at patches
in isolation before they look at the overall result.
Jonathan
> ---
> drivers/net/ethernet/broadcom/bnxt/bnxt_ulp.c | 105 ++++++++++++++++--
> 1 file changed, 93 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/net/ethernet/broadcom/bnxt/bnxt_ulp.c b/drivers/net/ethernet/broadcom/bnxt/bnxt_ulp.c
> index 665850753f90..ecad1947ccb5 100644
> --- a/drivers/net/ethernet/broadcom/bnxt/bnxt_ulp.c
> +++ b/drivers/net/ethernet/broadcom/bnxt/bnxt_ulp.c
> @@ -29,6 +29,70 @@
>
> static DEFINE_IDA(bnxt_rdma_aux_dev_ids);
>
> +struct bnxt_aux_device {
> + const char *name;
> + const u32 id;
> + u32 (*alloc_ida)(void);
> + void (*free_ida)(struct bnxt_aux_priv *priv);
> + void (*release)(struct device *dev);
> + void (*set_priv)(struct bnxt *bp, struct bnxt_aux_priv *priv);
> + struct bnxt_aux_priv *(*get_priv)(struct bnxt *bp);
> + void (*set_edev)(struct bnxt *bp, struct bnxt_en_dev *edev);
> + struct bnxt_en_dev *(*get_edev)(struct bnxt *bp);
> + struct auxiliary_device *(*get_auxdev)(struct bnxt *bp);
> +};
next prev parent reply other threads:[~2025-09-23 10:49 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 [this message]
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
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=20250923114935.00001730@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).