From: jszhang@marvell.com (Jisheng Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [Query] How to pass reboot arguments to secure firmware with PSCI spec
Date: Fri, 1 Aug 2014 19:02:27 +0800 [thread overview]
Message-ID: <20140801190227.116f4c39@xhacker> (raw)
In-Reply-To: <53DB6A18.5050904@arm.com>
Hi Sudeep,
On Fri, 1 Aug 2014 03:21:12 -0700
Sudeep Holla <sudeep.holla@arm.com> wrote:
>
>
> On 01/08/14 11:06, Jisheng Zhang wrote:
> > Hi Catalin and Will,
> >
> > I noticed that the following commit implement reboot via. PSCI
> > SYSTEM_RESET function. So my question is how to handle the reboot
> > arguments?
> >
>
> What reboot arguments do you want to handle ?
man 2 reboot
...
int reboot(int magic, int magic2, int cmd, void *arg);
...
I want to pass "void *arg" to secure firmware.
>
> >
> >> static void psci_sys_reset(enum reboot_mode reboot_mode, const char *cmd)
> >> {
> >> invoke_psci_fn(PSCI_0_2_FN_SYSTEM_RESET, 0, 0, 0);
> >
> > How to pass cmd to secure firmware?
> >
>
> What cmd do you want to pass ? The function id is already handled. What
> else do you want to pass ?
the "const char *cmd", usually this is the "abc" if user type "reboot abc"
under shell.
For example, android usually type "reboot recovery", the "recovery" will be
passed to next boot kernel boot args.
>
> If you see PSCI v0.2 spec, the SYSTEM_RESET and SYSTEM_SHUTDOWN takes no
> parameters.
Yes. I know it. That's why I need your help/suggestions about how to handle
the situation above.
Thanks for your input,
Jisheng
next prev parent reply other threads:[~2014-08-01 11:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 10:06 [Query] How to pass reboot arguments to secure firmware with PSCI spec Jisheng Zhang
2014-08-01 10:21 ` Sudeep Holla
2014-08-01 11:02 ` Jisheng Zhang [this message]
2014-08-01 14:00 ` Sudeep Holla
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=20140801190227.116f4c39@xhacker \
--to=jszhang@marvell.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).