From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: andrew.gospodarek@broadcom.com, davem@davemloft.net,
edumazet@google.com, jgg@ziepe.ca, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
michael.chan@broadcom.com, netdev@vger.kernel.org,
pabeni@redhat.com, selvin.xavier@broadcom.com
Subject: Re: [PATCH v3 5/6] bnxt_en: Use auxiliary bus calls over proprietary calls
Date: Wed, 9 Nov 2022 10:45:01 -0800 [thread overview]
Message-ID: <CACZ4nhvvGzDKPqsZ5F48oLC1u39a_m+ejRyaDieVOLatMC9Uqw@mail.gmail.com> (raw)
In-Reply-To: <Y2iol/ypwVMqrpQT@unreal>
[-- Attachment #1: Type: text/plain, Size: 2119 bytes --]
On Sun, Nov 6, 2022 at 10:41 PM Leon Romanovsky <leon@kernel.org> wrote:
>
> On Fri, Nov 04, 2022 at 09:27:32AM -0700, Ajit Khaparde wrote:
> > Wherever possible use the function ops provided by auxiliary bus
> > instead of using proprietary ops.
> >
> > Defined bnxt_re_suspend and bnxt_re_resume calls which can be
> > invoked by the bnxt_en driver instead of the ULP stop/start calls.
> >
> > Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
> > Reviewed-by: Andy Gospodarek <andrew.gospodarek@broadcom.com>
> > ---
> > drivers/infiniband/hw/bnxt_re/main.c | 102 +++++++++++-------
> > drivers/net/ethernet/broadcom/bnxt/bnxt_ulp.c | 40 ++++---
> > drivers/net/ethernet/broadcom/bnxt/bnxt_ulp.h | 2 -
> > 3 files changed, 87 insertions(+), 57 deletions(-)
>
> <...>
>
> > void bnxt_ulp_sriov_cfg(struct bnxt *bp, int num_vfs)
> > diff --git a/drivers/net/ethernet/broadcom/bnxt/bnxt_ulp.h b/drivers/net/ethernet/broadcom/bnxt/bnxt_ulp.h
> > index 26b7c627342b..e96f93d38a30 100644
> > --- a/drivers/net/ethernet/broadcom/bnxt/bnxt_ulp.h
> > +++ b/drivers/net/ethernet/broadcom/bnxt/bnxt_ulp.h
> > @@ -29,8 +29,6 @@ struct bnxt_msix_entry {
> > struct bnxt_ulp_ops {
>
> Once you convert to use AUX bus, this struct should go too.
We got rid of the bnxt_en_ops which the bnxt_re driver used to
communicate with bnxt_en.
Similarly We have tried to clean up most of the bnxt_ulp_ops.
In most of the cases we used the functions and entry points provided
by the auxiliary bus driver framework.
As you can see in the v4, there are the minimal functions needed to
support the functionality.
We will try to work on getting rid of the remaining if we find any
other viable alternative for those in future.
>
> > /* async_notifier() cannot sleep (in BH context) */
> > void (*ulp_async_notifier)(void *, struct hwrm_async_event_cmpl *);
> > - void (*ulp_stop)(void *);
> > - void (*ulp_start)(void *);
> > void (*ulp_sriov_config)(void *, int);
> > void (*ulp_shutdown)(void *);
> > void (*ulp_irq_stop)(void *);
> > --
> > 2.37.1 (Apple Git-137.1)
> >
>
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4218 bytes --]
next prev parent reply other threads:[~2022-11-09 18:45 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-24 23:14 [PATCH 0/2] Add Auxiliary driver support Ajit Khaparde
2022-07-24 23:14 ` [PATCH 1/2] net/bnxt: Add auxiliary " Ajit Khaparde
2022-08-02 12:50 ` kernel test robot
2022-07-24 23:14 ` [PATCH 2/2] RDMA/bnxt_re: Use auxiliary driver interface Ajit Khaparde
2022-07-25 12:15 ` Leon Romanovsky
2022-07-26 4:58 ` Ajit Khaparde
2022-07-26 5:36 ` Leon Romanovsky
2022-07-26 14:31 ` Ajit Khaparde
2022-10-25 17:31 ` [PATCH v2 0/6] Add Auxiliary driver support Ajit Khaparde
2022-10-25 17:31 ` [PATCH v2 1/6] bnxt_en: Add auxiliary " Ajit Khaparde
2022-10-25 17:31 ` [PATCH v2 2/6] RDMA/bnxt_re: Use auxiliary driver interface Ajit Khaparde
2022-10-26 9:24 ` Leon Romanovsky
2022-10-26 15:58 ` Ajit Khaparde
2022-11-04 16:27 ` [PATCH v3 0/6] Add Auxiliary driver support Ajit Khaparde
2022-11-04 16:27 ` [PATCH v3 1/6] bnxt_en: Add auxiliary " Ajit Khaparde
2022-11-08 7:21 ` kernel test robot
2022-11-04 16:27 ` [PATCH v3 2/6] RDMA/bnxt_re: Use auxiliary driver interface Ajit Khaparde
2022-11-04 16:27 ` [PATCH v3 3/6] bnxt_en: Remove usage of ulp_id Ajit Khaparde
2022-11-04 16:27 ` [PATCH v3 4/6] bnxt_en: Use direct API instead of indirection Ajit Khaparde
2022-11-04 16:27 ` [PATCH v3 5/6] bnxt_en: Use auxiliary bus calls over proprietary calls Ajit Khaparde
2022-11-07 6:41 ` Leon Romanovsky
2022-11-09 18:45 ` Ajit Khaparde [this message]
2022-11-04 16:27 ` [PATCH v3 6/6] bnxt_en: Remove struct bnxt access from RoCE driver Ajit Khaparde
2022-11-07 6:37 ` [PATCH v3 0/6] Add Auxiliary driver support Leon Romanovsky
2022-11-07 16:06 ` Jakub Kicinski
2022-11-07 17:26 ` Leon Romanovsky
2022-11-07 18:21 ` Ajit Khaparde
2022-10-25 17:31 ` [PATCH v2 3/6] bnxt_en: Remove usage of ulp_id Ajit Khaparde
2022-10-26 0:57 ` kernel test robot
2022-10-25 17:31 ` [PATCH v2 4/6] bnxt_en: Use direct API instead of indirection Ajit Khaparde
2022-10-27 17:56 ` kernel test robot
2022-10-25 17:31 ` [PATCH v2 5/6] bnxt_en: Use auxiliary bus calls over proprietary calls Ajit Khaparde
2022-10-25 21:18 ` kernel test robot
2022-10-26 3:21 ` kernel test robot
2022-10-25 17:31 ` [PATCH v2 6/6] bnxt_en: Remove struct bnxt access from RoCE driver Ajit Khaparde
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=CACZ4nhvvGzDKPqsZ5F48oLC1u39a_m+ejRyaDieVOLatMC9Uqw@mail.gmail.com \
--to=ajit.khaparde@broadcom.com \
--cc=andrew.gospodarek@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jgg@ziepe.ca \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).