From: Michal Simek <michal.simek@amd.com>
To: Tanmay Shah <tanmay.shah@amd.com>, jassisinghbrar@gmail.com
Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] mailbox: zynqmp: setup IPI for each valid child node
Date: Wed, 11 Dec 2024 15:14:06 +0100 [thread overview]
Message-ID: <66ba0a5b-dba5-4162-b83f-2058b0dce3f8@amd.com> (raw)
In-Reply-To: <20241112170612.2577383-1-tanmay.shah@amd.com>
On 11/12/24 18:06, Tanmay Shah wrote:
> As per zynqmp-ipi bindings, zynqmp IPI node can have multiple child nodes.
> Current IPI setup function is set only for first child node. If IPI node
> has multiple child nodes in the device-tree, then IPI setup fails for
> child nodes other than first child node. In such case kernel will crash.
> Fix this crash by registering IPI setup function for each available child
> node.
>
> Signed-off-by: Tanmay Shah <tanmay.shah@amd.com>
> ---
> drivers/mailbox/zynqmp-ipi-mailbox.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/mailbox/zynqmp-ipi-mailbox.c b/drivers/mailbox/zynqmp-ipi-mailbox.c
> index 521d08b9ab47..815e0492f029 100644
> --- a/drivers/mailbox/zynqmp-ipi-mailbox.c
> +++ b/drivers/mailbox/zynqmp-ipi-mailbox.c
> @@ -940,10 +940,10 @@ static int zynqmp_ipi_probe(struct platform_device *pdev)
> pdata->num_mboxes = num_mboxes;
>
> mbox = pdata->ipi_mboxes;
> - mbox->setup_ipi_fn = ipi_fn;
> -
> for_each_available_child_of_node(np, nc) {
> mbox->pdata = pdata;
> + mbox->setup_ipi_fn = ipi_fn;
> +
> ret = zynqmp_ipi_mbox_probe(mbox, nc);
> if (ret) {
> of_node_put(nc);
>
> base-commit: 28955f4fa2823e39f1ecfb3a37a364563527afbc
I think you should add Fixed tag and also cc stable@kernel.org
With that fixed feel free to add
Reviewed-by: Michal Simek <michal.simek@amd.com>
Thanks,
Michal
prev parent reply other threads:[~2024-12-11 14:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 17:06 Tanmay Shah
2024-12-11 14:14 ` Michal Simek [this message]
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=66ba0a5b-dba5-4162-b83f-2058b0dce3f8@amd.com \
--to=michal.simek@amd.com \
--cc=jassisinghbrar@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tanmay.shah@amd.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
all inboxes | Powered by JetHome®