From: Alexander Sverdlin <alexander.sverdlin@gmail.com>
To: Anshumali Gaur <agaur@marvell.com>,
conor.dooley@microchip.com, ulf.hansson@linaro.org,
arnd@arndb.de, linus.walleij@linaro.org,
nikita.shubin@maquefel.me, vkoul@kernel.org, cyy@cyyself.name,
krzysztof.kozlowski@linaro.org, linux-kernel@vger.kernel.org,
sgoutham@marvell.com
Subject: Re: [PATCH 2/4] soc: marvell: rvu-pf: Add PF to AF mailbox communication support.
Date: Sat, 21 Sep 2024 23:43:33 +0200 [thread overview]
Message-ID: <68fa22ebdc896adffe42c0f101339c61f2dce86a.camel@gmail.com> (raw)
In-Reply-To: <20240920112318.2722488-3-agaur@marvell.com>
Hi Anshumali!
On Fri, 2024-09-20 at 16:53 +0530, Anshumali Gaur wrote:
> Resource provisioning for virtual functions (VFs) is done by RVU admin
> function (AF). RVU PF and AF shares a memory region which can be used
> for communication. This patch adds support for mailbox communication
> between PF and AF, notification of messages is via IRQs.
>
> Example mailbox messages types and structures can be found at
> drivers/net/ethernet/marvell/octeontx2/af/mbox.h
>
> Signed-off-by: Anshumali Gaur <agaur@marvell.com>
>
[]
> +#define M(_name, _id, _fn_name, _req_type, _rsp_type) \
> +static struct _req_type __maybe_unused \
> +*gen_pf_mbox_alloc_msg_ ## _fn_name(struct mbox *mbox) \
> +{ \
> + struct _req_type *req; \
> + u16 id = _id; \
> + \
> + req = (struct _req_type *)otx2_mbox_alloc_msg_rsp( \
> + &mbox->mbox, 0, sizeof(struct _req_type), \
> + sizeof(struct _rsp_type)); \
> + if (!req) \
> + return NULL; \
> + req->hdr.sig = OTX2_MBOX_REQ_SIG; \
> + req->hdr.id = id; \
> + trace_otx2_msg_alloc(mbox->mbox.pdev, id, sizeof(*req)); \
> + return req; \
> +}
> +
> +MBOX_MESSAGES
> +#undef M
While checkpatch is wondering about _name:
WARNING: Argument '_name' is not used in function-like macro
#399: FILE: drivers/soc/marvell/rvu_gen_pf/gen_pf.h:77:
+#define M(_name, _id, _fn_name, _req_type, _rsp_type) \
... I ask myself what actually happens here with "M" and "MBOX_MESSAGES"?
--
Alexander Sverdlin.
next prev parent reply other threads:[~2024-09-21 21:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 11:23 [PATCH 0/4] soc: marvell: Add a general purpose RVU physical Anshumali Gaur
2024-09-20 11:23 ` [PATCH 1/4] soc: marvell: Add a general purpose RVU PF driver Anshumali Gaur
2024-09-20 22:30 ` Alexander Sverdlin
2024-09-21 21:38 ` Alexander Sverdlin
2024-09-20 11:23 ` [PATCH 2/4] soc: marvell: rvu-pf: Add PF to AF mailbox communication support Anshumali Gaur
2024-09-21 21:43 ` Alexander Sverdlin [this message]
2024-09-24 23:09 ` Alexander Sverdlin
2024-09-20 11:23 ` [PATCH 3/4] soc: marvell: rvu-pf: Add mailbox communication btw RVU VFs and PF Anshumali Gaur
2024-09-21 22:22 ` Alexander Sverdlin
2024-09-20 11:23 ` [PATCH 4/4] soc: marvell: rvu-pf: Handle function level reset (FLR) IRQs for VFs Anshumali Gaur
2024-09-21 22:49 ` Alexander Sverdlin
2024-09-25 9:13 ` Anshumali Gaur
2024-09-25 9:19 ` Alexander Sverdlin
2024-09-25 12:46 ` Anshumali Gaur
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=68fa22ebdc896adffe42c0f101339c61f2dce86a.camel@gmail.com \
--to=alexander.sverdlin@gmail.com \
--cc=agaur@marvell.com \
--cc=arnd@arndb.de \
--cc=conor.dooley@microchip.com \
--cc=cyy@cyyself.name \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikita.shubin@maquefel.me \
--cc=sgoutham@marvell.com \
--cc=ulf.hansson@linaro.org \
--cc=vkoul@kernel.org \
/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