From: 乱石 <zhangliguang@linux.alibaba.com>
To: James Morse <james.morse@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firmware: arm_sdei: pass sdei_api_event_register right parameters
Date: Fri, 24 Sep 2021 21:34:11 +0800 [thread overview]
Message-ID: <f0dac2f4-60f5-b200-47f1-0b845cfa02a6@linux.alibaba.com> (raw)
In-Reply-To: <20210910040117.98736-1-zhangliguang@linux.alibaba.com>
Hi James,
Gentle ping! Any comments on this patch?
在 2021/9/10 12:01, Liguang Zhang 写道:
> Function _local_event_enable is used for private sdei event
> registeration called by sdei_event_register. We should pass
> sdei_api_event_register right flag and mpidr parameters, otherwise atf
> may trigger assert errors.
>
> Signed-off-by: Liguang Zhang <zhangliguang@linux.alibaba.com>
> ---
> drivers/firmware/arm_sdei.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/firmware/arm_sdei.c b/drivers/firmware/arm_sdei.c
> index a7e762c352f9..0736752dadde 100644
> --- a/drivers/firmware/arm_sdei.c
> +++ b/drivers/firmware/arm_sdei.c
> @@ -558,14 +558,16 @@ static int sdei_api_event_register(u32 event_num, unsigned long entry_point,
> static void _local_event_register(void *data)
> {
> int err;
> + u64 mpidr;
> struct sdei_registered_event *reg;
> struct sdei_crosscall_args *arg = data;
>
> WARN_ON(preemptible());
>
> + mpidr = read_cpuid_mpidr();
> reg = per_cpu_ptr(arg->event->private_registered, smp_processor_id());
> err = sdei_api_event_register(arg->event->event_num, sdei_entry_point,
> - reg, 0, 0);
> + reg, SDEI_EVENT_REGISTER_RM_PE, mpidr);
>
> sdei_cross_call_return(arg, err);
> }
next prev parent reply other threads:[~2021-09-24 13:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 4:01 Liguang Zhang
2021-09-24 13:34 ` 乱石 [this message]
2021-10-08 17:39 ` James Morse
2021-10-11 10:37 ` 乱石
[not found] ` <b93cf74a-ec1a-dcfc-990b-d3dbc4b55c3d@linux.alibaba.com>
2021-10-18 17:32 ` James Morse
2021-10-19 3:35 ` 乱石
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=f0dac2f4-60f5-b200-47f1-0b845cfa02a6@linux.alibaba.com \
--to=zhangliguang@linux.alibaba.com \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®