All of lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Andrew Jones <ajones@ventanamicro.com>
Cc: linux-riscv@lists.infradead.org,
	'Anup Patel ' <apatel@ventanamicro.com>,
	'Albert Ou ' <aou@eecs.berkeley.edu>,
	'Paul Walmsley ' <paul.walmsley@sifive.com>,
	'Sia Jee Heng ' <jeeheng.sia@starfivetech.com>,
	'Palmer Dabbelt ' <palmer@dabbelt.com>,
	'Ley Foon Tan ' <leyfoon.tan@starfivetech.com>
Subject: Re: [RFC PATCH 0/1] riscv: Introduce system suspend support
Date: Tue, 17 Jan 2023 22:34:59 +0000	[thread overview]
Message-ID: <Y8cikxHHxXPeGKyF@spud> (raw)
In-Reply-To: <20230106113216.443057-1-ajones@ventanamicro.com>


[-- Attachment #1.1: Type: text/plain, Size: 1082 bytes --]

Hey Drew!

On Fri, Jan 06, 2023 at 12:32:15PM +0100, Andrew Jones wrote:
> Booting with an OpenSBI including the RFC series[1] implementing the
> draft proposal for SBI system suspend[2] we can add system support to
> Linux. This support implements "suspend-to-RAM", which means when a
> kernel is built with CONFIG_SUSPEND 'echo mem > /sys/power/state' will
> initiate a suspension.
> 
> This has only been tested on QEMU using the OpenSBI system suspend
> test. The test just waits 5 seconds and then resumes. To truly use
> system suspend a platform must have a low-level firmware implementation
> and provide at least one wake-up event, such as from a wakeup-capable
> RTC alarm, to resume.
> 
> [1] https://github.com/jones-drew/opensbi/commits/susp-rfc
>     Posting: http://lists.infradead.org/pipermail/opensbi/2023-January/004091.html
> [2] https://github.com/jones-drew/riscv-sbi-doc/commit/d9e43e9a938fc3eb510e023c3f352462876f7785

In case you don't get alerts from GH, I left one *tiny* comment on this.
And I really mean tiny!

Thanks,
Conor.


[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  parent reply	other threads:[~2023-01-17 22:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-06 11:32 [RFC PATCH 0/1] riscv: Introduce system suspend support Andrew Jones
2023-01-06 11:32 ` [RFC PATCH 1/1] riscv: sbi: " Andrew Jones
2023-01-10 14:55   ` Leyfoon Tan
2023-01-10 15:52     ` Andrew Jones
2023-01-10 22:23   ` Conor Dooley
2023-01-11  8:52     ` Andrew Jones
2023-01-11  9:06       ` Conor Dooley
2023-01-11  9:16         ` Andrew Jones
2023-01-17 22:34 ` Conor Dooley [this message]
2023-01-18 11:55   ` [RFC PATCH 0/1] riscv: " Andrew Jones

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=Y8cikxHHxXPeGKyF@spud \
    --to=conor@kernel.org \
    --cc=ajones@ventanamicro.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=apatel@ventanamicro.com \
    --cc=jeeheng.sia@starfivetech.com \
    --cc=leyfoon.tan@starfivetech.com \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.