Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
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 v4 for-next 3/6] RDMA/bnxt_re: Query function capabilities from firmware
Date: Sun, 11 Jun 2023 16:04:20 +0300	[thread overview]
Message-ID: <20230611130420.GD12152@unreal> (raw)
In-Reply-To: <1685617837-15725-4-git-send-email-selvin.xavier@broadcom.com>

On Thu, Jun 01, 2023 at 04:10:34AM -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 | 23 +++++++++++++++++++++++
>  1 file changed, 23 insertions(+)
> 
> diff --git a/drivers/infiniband/hw/bnxt_re/main.c b/drivers/infiniband/hw/bnxt_re/main.c
> index 9cc652e..da99f69 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");
>  }
>  
>  static void bnxt_re_destroy_chip_ctx(struct bnxt_re_dev *rdev)
> @@ -340,6 +344,25 @@ static void bnxt_re_fill_fw_msg(struct bnxt_fw_msg *fw_msg, void *msg,
>  	fw_msg->timeout = timeout;
>  }
>  
> +/* Query function capabilities using common hwrm */
> +int bnxt_re_hwrm_qcaps(struct bnxt_re_dev *rdev)
> +{
> +	struct bnxt_en_dev *en_dev = rdev->en_dev;
> +	struct hwrm_func_qcaps_output resp = {0};
> +	struct hwrm_func_qcaps_input req = {0};

There is no need in 0 here, just use {}

> +	struct bnxt_qplib_chip_ctx *cctx;
> +	struct bnxt_fw_msg fw_msg;

Initialize it to zero from the beginning and remove memset()

> +
> +	cctx = rdev->chip_ctx;
> +	memset(&fw_msg, 0, sizeof(fw_msg));
> +	bnxt_re_init_hwrm_hdr(rdev, (void *)&req,
> +			      HWRM_FUNC_QCAPS, -1, -1);

All callers to bnxt_re_init_hwrm_hdr() provide "-1, -1" and rdev is not
used at all.

> +	req.fid = cpu_to_le16(0xffff);
> +	bnxt_re_fill_fw_msg(&fw_msg, (void *)&req, sizeof(req), (void *)&resp,
> +			    sizeof(resp), DFLT_HWRM_CMD_TIMEOUT);
> +	return bnxt_send_msg(en_dev, &fw_msg);
> +}
> +
>  static int bnxt_re_net_ring_free(struct bnxt_re_dev *rdev,
>  				 u16 fw_ring_id, int type)
>  {
> -- 
> 2.5.5
> 



  reply	other threads:[~2023-06-11 13:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-01 11:10 [PATCH v4 for-next 0/6] RDMA/bnxt_re: driver update for supporting low latency push Selvin Xavier
2023-06-01 11:10 ` [PATCH v4 for-next 1/6] RDMA/bnxt_re: Use the common mmap helper functions Selvin Xavier
2023-06-01 11:10 ` [PATCH v4 for-next 2/6] RDMA/bnxt_re: Add disassociate ucontext support Selvin Xavier
2023-06-01 11:10 ` [PATCH v4 for-next 3/6] RDMA/bnxt_re: Query function capabilities from firmware Selvin Xavier
2023-06-11 13:04   ` Leon Romanovsky [this message]
2023-06-12  5:50     ` Selvin Xavier
2023-06-01 11:10 ` [PATCH v4 for-next 4/6] RDMA/bnxt_re: Move the interface version to chip context structure Selvin Xavier
2023-06-01 11:10 ` [PATCH v4 for-next 5/6] RDMA/bnxt_re: Reorg the bar mapping Selvin Xavier
2023-06-01 11:10 ` [PATCH v4 for-next 6/6] RDMA/bnxt_re: Enable low latency push 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=20230611130420.GD12152@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