From: Conor Dooley <conor@kernel.org>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: ajones@ventanamicro.com, apatel@ventanamicro.com,
Atish Patra <atishp@rivosinc.com>,
linux-riscv@lists.infradead.org, leyfoon.tan@starfivetech.com,
jeeheng.sia@starfivetech.com,
Paul Walmsley <paul.walmsley@sifive.com>,
aou@eecs.berkeley.edu
Subject: Re: [RFC v2 PATCH 1/1] riscv: sbi: Introduce system suspend support
Date: Tue, 28 Feb 2023 16:48:19 +0000 [thread overview]
Message-ID: <Y/4wU9fZCDTQrx8E@spud> (raw)
In-Reply-To: <mhng-2b30e6d6-d8bf-4fae-a95c-f9e042ec90d0@palmer-ri-x1c9a>
[-- Attachment #1.1: Type: text/plain, Size: 1012 bytes --]
On Tue, Feb 28, 2023 at 07:54:56AM -0800, Palmer Dabbelt wrote:
> On Wed, 18 Jan 2023 10:03:38 PST (-0800), ajones@ventanamicro.com wrote:
> > When the SUSP SBI extension is present it implies that the standard
> > "suspend to RAM" type is available. Wire it up to the generic
> > platform suspend support, also applying the already present support
> > for non-retentive CPU suspend. When the kernel is built with
> > CONFIG_SUSPEND, one can do 'echo mem > /sys/power/state' to suspend.
> > Resumption will occur when a platform-specific wake-up event arrives.
> >
> The code looks fine, but I can't find the SUSP extension anywhere. There's
> just hart suspend in
> <https://github.com/riscv-non-isa/riscv-sbi-doc/blob/master/riscv-sbi.adoc>.
It's not merged yet, so:
https://lists.riscv.org/g/tech-prs/message/222
&
https://lists.riscv.org/g/tech-prs/message/228
Or on GitHub for those who are not members of the RVI stuff:
https://github.com/jones-drew/riscv-sbi-doc/commits/susp-v1
[-- 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
next prev parent reply other threads:[~2023-02-28 16:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 18:03 [RFC v2 PATCH 0/1] riscv: Introduce system suspend support Andrew Jones
2023-01-18 18:03 ` [RFC v2 PATCH 1/1] riscv: sbi: " Andrew Jones
2023-02-28 15:54 ` Palmer Dabbelt
2023-02-28 16:48 ` Conor Dooley [this message]
2023-02-28 17:05 ` 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=Y/4wU9fZCDTQrx8E@spud \
--to=conor@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=aou@eecs.berkeley.edu \
--cc=apatel@ventanamicro.com \
--cc=atishp@rivosinc.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.