From: Leon Romanovsky <leon@kernel.org>
To: Pavan Chebbi <pavan.chebbi@broadcom.com>
Cc: jgg@ziepe.ca, michael.chan@broadcom.com,
linux-kernel@vger.kernel.org, dave.jiang@intel.com,
saeedm@nvidia.com, Jonathan.Cameron@huawei.com,
gospo@broadcom.com, selvin.xavier@broadcom.com,
kalesh-anakkur.purayil@broadcom.com
Subject: Re: [PATCH v2 fwctl 2/5] fwctl/bnxt_en: Refactor aux bus functions to be more generic
Date: Thu, 29 Jan 2026 15:32:48 +0200 [thread overview]
Message-ID: <20260129133248.GJ10992@unreal> (raw)
In-Reply-To: <20260126053710.3474483-3-pavan.chebbi@broadcom.com>
On Sun, Jan 25, 2026 at 09:37:07PM -0800, Pavan Chebbi wrote:
> Up until now there was only one auxiliary device that bnxt
> created and that was for RoCE driver. bnxt fwctl is also
> going to use an aux bus device that bnxt should create.
> This requires some nomenclature changes and refactoring of
> the existing bnxt aux dev functions.
>
> Convert 'aux_priv' and 'edev' members of struct bnxt into
> arrays where each element contains supported auxbus device's
> data. Move struct bnxt_aux_priv from bnxt.h to ulp.h because
> that is where it belongs. Make aux bus init/uninit/add/del
> functions more generic which will loop through all the aux
> device types. Make bnxt_ulp_start/stop functions (the only
> other common functions applicable to any aux device) loop
> through the aux devices to update their config and states.
> Make callers of bnxt_ulp_start() call it only when there
> are no errors.
>
> Also, as an improvement in code, bnxt_register_dev() can skip
> unnecessary dereferencing of edev from bp, instead use the
> edev pointer from the function parameter.
>
> Future patches will reuse these functions to add an aux bus
> device for fwctl.
>
> Reviewed-by: Andy Gospodarek <gospo@broadcom.com>
> Signed-off-by: Pavan Chebbi <pavan.chebbi@broadcom.com>
> ---
> drivers/net/ethernet/broadcom/bnxt/bnxt.c | 47 ++-
> drivers/net/ethernet/broadcom/bnxt/bnxt.h | 19 +-
> .../net/ethernet/broadcom/bnxt/bnxt_devlink.c | 8 +-
> .../net/ethernet/broadcom/bnxt/bnxt_ethtool.c | 2 +-
> drivers/net/ethernet/broadcom/bnxt/bnxt_ulp.c | 334 +++++++++++-------
> include/linux/bnxt/ulp.h | 25 +-
> 6 files changed, 271 insertions(+), 164 deletions(-)
<...>
> +static void bnxt_auxdev_set_state(struct bnxt *bp, int idx, int state)
> +{
> + mutex_lock(&bp->auxdev_lock);
> + bp->auxdev_state[idx] = state;
> + mutex_unlock(&bp->auxdev_lock);
> +}
> +
> +static bool bnxt_auxdev_is_init(struct bnxt *bp, int idx)
> +{
> + bool ret;
> +
> + mutex_lock(&bp->auxdev_lock);
> + ret = (bp->auxdev_state[idx] == BNXT_ADEV_STATE_INIT);
> + mutex_unlock(&bp->auxdev_lock);
> + return ret;
> +}
> +
> +static bool bnxt_auxdev_is_active(struct bnxt *bp, int idx)
> +{
> + bool ret;
> +
> + mutex_lock(&bp->auxdev_lock);
> + ret = (bp->auxdev_state[idx] == BNXT_ADEV_STATE_ADD);
> + mutex_unlock(&bp->auxdev_lock);
> + return ret;
> +}
<...>
> void bnxt_ulp_stop(struct bnxt *bp)
> {
> - struct bnxt_aux_priv *aux_priv = bp->aux_priv;
> - struct bnxt_en_dev *edev = bp->edev;
> -
> - if (!edev)
> - return;
> + int i;
>
> - mutex_lock(&edev->en_dev_lock);
> - if (!bnxt_ulp_registered(edev) ||
> - (edev->flags & BNXT_EN_FLAG_ULP_STOPPED))
> - goto ulp_stop_exit;
> -
> - edev->flags |= BNXT_EN_FLAG_ULP_STOPPED;
> - if (aux_priv) {
> + for (i = 0; i < __BNXT_AUXDEV_MAX; i++) {
> + struct bnxt_aux_priv *aux_priv;
> struct auxiliary_device *adev;
> + struct bnxt_en_dev *edev;
> +
> + if (!bnxt_auxdev_is_active(bp, i))
It’s good that you stopped using atomic_t for state variables, but the
locking is still incorrect. It’s not enough to hold the lock only while
reading the state; you need to keep the lock for the entire period during
which the auxdev is expected to remain active.
Thanks
next prev parent reply other threads:[~2026-01-29 13:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 5:37 [PATCH v2 fwctl 0/5] fwctl/bnxt_fwctl: fwctl for Broadcom Netxtreme devices Pavan Chebbi
2026-01-26 5:37 ` [PATCH v2 fwctl 1/5] fwctl/bnxt_en: Move common definitions to include/linux/bnxt/ Pavan Chebbi
2026-01-26 5:37 ` [PATCH v2 fwctl 2/5] fwctl/bnxt_en: Refactor aux bus functions to be more generic Pavan Chebbi
2026-01-29 13:32 ` Leon Romanovsky [this message]
2026-01-29 13:55 ` Pavan Chebbi
2026-01-26 5:37 ` [PATCH v2 fwctl 3/5] fwctl/bnxt_en: Create an aux device for fwctl Pavan Chebbi
2026-01-29 13:36 ` Leon Romanovsky
2026-01-29 13:56 ` Pavan Chebbi
2026-01-26 5:37 ` [PATCH v2 fwctl 4/5] fwctl/bnxt_fwctl: Add bnxt fwctl device Pavan Chebbi
2026-01-26 5:37 ` [PATCH v2 fwctl 5/5] fwctl/bnxt_fwctl: Add documentation entries Pavan Chebbi
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=20260129133248.GJ10992@unreal \
--to=leon@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=dave.jiang@intel.com \
--cc=gospo@broadcom.com \
--cc=jgg@ziepe.ca \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.chan@broadcom.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
all inboxes | Powered by JetHome®