From: Michal Simek <michal.simek@xilinx.com>
To: Sudeep Holla <sudeep.holla@arm.com>,
Michal Simek <michal.simek@xilinx.com>,
<linux-arm-kernel@lists.infradead.org>
Cc: Mark Rutland <mark.rutland@arm.com>, Will Wong <WILLW@xilinx.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
<linux-kernel@vger.kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: [PATCH v2] firmware/psci: add support for SYSTEM_RESET2
Date: Mon, 30 Jul 2018 10:59:21 +0200 [thread overview]
Message-ID: <d73d3580-4ec1-a281-4585-5c776fc08c79@xilinx.com> (raw)
In-Reply-To: <74f80458-2d04-c161-c82d-55739e46e661@arm.com>
Hi Sudeep,
On 26.7.2018 15:29, Sudeep Holla wrote:
> Hi Michal,
>
> Sorry somehow missed this email.
>
> On 19/07/18 11:47, Michal Simek wrote:
>> On 9.7.2018 15:21, Sudeep Holla wrote:
>
> [...]
>
>>>
>>> I think with efi_reboot, if user execute the command "reboot warm", it
>>> will set REBOOT_WARM. I was thinking something similar for psci too. I
>>> can drop REBOOT_SOFT if that's not correct.
>>
>> Have you found more details about efi_reboot and passing information in
>> case of reboot warm?
>>
>
> I was just referring to drivers/firmware/efi/reboot.c- function efi_reboot.
>
> Anyways the function reboot_setup in kernel/reboot.c sets the reboot
> mode parsing the string passed by the user(e.g.: warm, cold, hard, gpio,
> soft,..etc it just scans the first character TBH)
ok. I see. It is just reusing that reboot=X passed via kernel command line.
Thanks,
Michal
prev parent reply other threads:[~2018-07-30 8:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 14:51 [PATCH] " Sudeep Holla
2018-05-01 17:59 ` Florian Fainelli
2018-05-02 10:20 ` Sudeep Holla
2018-05-02 10:30 ` [PATCH v2] " Sudeep Holla
2018-07-09 12:17 ` Michal Simek
2018-07-09 12:36 ` Sudeep Holla
2018-07-09 13:13 ` Michal Simek
2018-07-09 13:21 ` Sudeep Holla
2018-07-19 10:47 ` Michal Simek
2018-07-26 13:29 ` Sudeep Holla
2018-07-30 8:59 ` 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=d73d3580-4ec1-a281-4585-5c776fc08c79@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=WILLW@xilinx.com \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=sudeep.holla@arm.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®