From: Leon Romanovsky <leonro@nvidia.com>
To: Siva Reddy Kallam <siva.kallam@broadcom.com>
Cc: <jgg@nvidia.com>, <linux-rdma@vger.kernel.org>,
<netdev@vger.kernel.org>, <vikas.gupta@broadcom.com>,
<selvin.xavier@broadcom.com>, <anand.subramanian@broadcom.com>,
<usman.ansari@broadcom.com>
Subject: Re: [PATCH v3 5/8] RDMA/bng_re: Add infrastructure for enabling Firmware channel
Date: Thu, 20 Nov 2025 18:02:44 +0200 [thread overview]
Message-ID: <20251120160244.GW18335@unreal> (raw)
In-Reply-To: <20251117171136.128193-6-siva.kallam@broadcom.com>
On Mon, Nov 17, 2025 at 05:11:23PM +0000, Siva Reddy Kallam wrote:
> Add infrastructure for enabling Firmware channel.
>
> Signed-off-by: Siva Reddy Kallam <siva.kallam@broadcom.com>
> Reviewed-by: Usman Ansari <usman.ansari@broadcom.com>
> ---
> drivers/infiniband/hw/bng_re/bng_dev.c | 120 +++++++-
> drivers/infiniband/hw/bng_re/bng_fw.c | 361 ++++++++++++++++++++++++-
> drivers/infiniband/hw/bng_re/bng_fw.h | 133 ++++++++-
> drivers/infiniband/hw/bng_re/bng_re.h | 45 +++
> drivers/infiniband/hw/bng_re/bng_res.c | 2 +
> drivers/infiniband/hw/bng_re/bng_res.h | 102 +++++++
> drivers/infiniband/hw/bng_re/bng_tlv.h | 128 +++++++++
> 7 files changed, 885 insertions(+), 6 deletions(-)
> create mode 100644 drivers/infiniband/hw/bng_re/bng_tlv.h
<...>
> +int bng_re_rcfw_start_irq(struct bng_re_rcfw *rcfw, int msix_vector,
> + bool need_init)
> +{
> + struct bng_re_creq_ctx *creq;
> + struct bng_re_res *res;
> + int rc;
> +
> + creq = &rcfw->creq;
> + res = rcfw->res;
> +
> + if (creq->irq_handler_avail)
> + return -EFAULT;
> +
> + creq->msix_vec = msix_vector;
> + if (need_init)
> + tasklet_setup(&creq->creq_tasklet, bng_re_service_creq);
> + else
> + tasklet_enable(&creq->creq_tasklet);
I wonder if new drivers need to use workqueues instead.
https://lwn.net/Articles/966894/
Thanks
next prev parent reply other threads:[~2025-11-20 16:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 17:11 [PATCH v3 0/8] Introducing Broadcom BNG_RE RoCE Driver Siva Reddy Kallam
2025-11-17 17:11 ` [PATCH v3 1/8] bng_en: Add RoCE aux device support Siva Reddy Kallam
2025-11-17 17:11 ` [PATCH v3 2/8] RDMA/bng_re: Add Auxiliary interface Siva Reddy Kallam
2025-11-17 17:11 ` [PATCH v3 3/8] RDMA/bng_re: Register and get the resources from bnge driver Siva Reddy Kallam
2025-11-17 17:11 ` [PATCH v3 4/8] RDMA/bng_re: Allocate required memory resources for Firmware channel Siva Reddy Kallam
2025-11-24 16:49 ` Simon Horman
2025-11-25 10:35 ` Siva Reddy Kallam
2025-11-17 17:11 ` [PATCH v3 5/8] RDMA/bng_re: Add infrastructure for enabling " Siva Reddy Kallam
2025-11-20 16:02 ` Leon Romanovsky [this message]
2025-11-24 16:44 ` Simon Horman
2025-11-25 6:33 ` Siva Reddy Kallam
2025-11-17 17:11 ` [PATCH v3 6/8] RDMA/bng_re: Enable Firmware channel and query device attributes Siva Reddy Kallam
2025-11-17 17:11 ` [PATCH v3 7/8] RDMA/bng_re: Add basic debugfs infrastructure Siva Reddy Kallam
2025-11-17 17:11 ` [PATCH v3 8/8] RDMA/bng_re: Initialize the Firmware and Hardware Siva Reddy Kallam
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=20251120160244.GW18335@unreal \
--to=leonro@nvidia.com \
--cc=anand.subramanian@broadcom.com \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=selvin.xavier@broadcom.com \
--cc=siva.kallam@broadcom.com \
--cc=usman.ansari@broadcom.com \
--cc=vikas.gupta@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).