From: Leon Romanovsky <leon@kernel.org>
To: Selvin Xavier <selvin.xavier@broadcom.com>
Cc: jgg@ziepe.ca, linux-rdma@vger.kernel.org, andrew.gospodarek@broadcom.com
Subject: Re: [PATCH for-next 3/6] RDMA/bnxt_re: Query function capabilities from firmware
Date: Mon, 10 Apr 2023 15:28:15 +0300 [thread overview]
Message-ID: <20230410122815.GR182481@unreal> (raw)
In-Reply-To: <1681125115-7127-4-git-send-email-selvin.xavier@broadcom.com>
On Mon, Apr 10, 2023 at 04:11:52AM -0700, Selvin Xavier wrote:
> Query Function capabilities to enable advanced features.
>
> Signed-off-by: Selvin Xavier <selvin.xavier@broadcom.com>
> ---
> drivers/infiniband/hw/bnxt_re/main.c | 30 ++++++++++++++++++++++++++++++
> 1 file changed, 30 insertions(+)
>
> diff --git a/drivers/infiniband/hw/bnxt_re/main.c b/drivers/infiniband/hw/bnxt_re/main.c
> index a866951..1b69198 100644
> --- a/drivers/infiniband/hw/bnxt_re/main.c
> +++ b/drivers/infiniband/hw/bnxt_re/main.c
> @@ -83,6 +83,7 @@ static int bnxt_re_netdev_event(struct notifier_block *notifier,
> unsigned long event, void *ptr);
> static struct bnxt_re_dev *bnxt_re_from_netdev(struct net_device *netdev);
> static void bnxt_re_dev_uninit(struct bnxt_re_dev *rdev);
> +static int bnxt_re_hwrm_qcaps(struct bnxt_re_dev *rdev);
>
> static void bnxt_re_set_drv_mode(struct bnxt_re_dev *rdev, u8 mode)
> {
> @@ -91,6 +92,9 @@ static void bnxt_re_set_drv_mode(struct bnxt_re_dev *rdev, u8 mode)
> cctx = rdev->chip_ctx;
> cctx->modes.wqe_mode = bnxt_qplib_is_chip_gen_p5(rdev->chip_ctx) ?
> mode : BNXT_QPLIB_WQE_MODE_STATIC;
> + if (bnxt_re_hwrm_qcaps(rdev))
> + dev_err(rdev_to_dev(rdev),
> + "Failed to query hwrm qcaps\n");
You already print error in bnxt_re_hwrm_qcaps()
> }
<...>
> +/* Query function capabilities using common hwrm */
> +int bnxt_re_hwrm_qcaps(struct bnxt_re_dev *rdev)
<...>
> + if (rc) {
> + dev_err(rdev_to_dev(rdev),
> + "Failed to query capabilities, rc = %#x", rc);
> + return rc;
> + }
> + return 0;
> +}
> +
> static int bnxt_re_net_ring_free(struct bnxt_re_dev *rdev,
> u16 fw_ring_id, int type)
> {
> --
> 2.5.5
>
next prev parent reply other threads:[~2023-04-10 12:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 11:11 [PATCH for-next 0/6] RDMA/bnxt_re: driver update for supporting low latency push Selvin Xavier
2023-04-10 11:11 ` [PATCH for-next 1/6] RDMA/bnxt_re: Use the common mmap helper functions Selvin Xavier
2023-04-10 12:20 ` Leon Romanovsky
2023-04-11 16:53 ` Jason Gunthorpe
2023-04-12 6:49 ` Selvin Xavier
2023-04-10 11:11 ` [PATCH for-next 2/6] RDMA/bnxt_re: Add disassociate ucontext support Selvin Xavier
2023-04-10 12:27 ` Leon Romanovsky
2023-04-11 16:49 ` Jason Gunthorpe
2023-04-10 11:11 ` [PATCH for-next 3/6] RDMA/bnxt_re: Query function capabilities from firmware Selvin Xavier
2023-04-10 12:28 ` Leon Romanovsky [this message]
2023-04-10 11:11 ` [PATCH for-next 4/6] RDMA/bnxt_re: Move the interface version to chip context structure Selvin Xavier
2023-04-10 11:11 ` [PATCH for-next 5/6] RDMA/bnxt_re: Reorg the bar mapping Selvin Xavier
2023-04-10 11:11 ` [PATCH for-next 6/6] RDMA/bnxt_re: Enable low latency push Selvin Xavier
2023-04-11 16:56 ` Jason Gunthorpe
2023-04-12 5:58 ` Selvin Xavier
2023-04-10 12:32 ` [PATCH for-next 0/6] RDMA/bnxt_re: driver update for supporting " Leon Romanovsky
2023-04-11 2:29 ` Selvin Xavier
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=20230410122815.GR182481@unreal \
--to=leon@kernel.org \
--cc=andrew.gospodarek@broadcom.com \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--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