From: Ruifeng Zhang <ruifeng.zhang0110@gmail.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
ruifeng.zhang1@unisoc.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Chunyan Zhang <chunyan.zhang@unisoc.com>
Subject: Re: [PATCH] RFC syscore: add suspend type to syscore
Date: Thu, 4 Feb 2021 17:09:17 +0800 [thread overview]
Message-ID: <CAG7+-3PuA3CdZAL5_m9aEuEdw7yaguXCFvasLjk==P9URNZ4QA@mail.gmail.com> (raw)
In-Reply-To: <CAJZ5v0iS92CN5MKHu8tOpQR6mOWu=4=PLqN84qXG+v+64Ro99Q@mail.gmail.com>
Rafael J. Wysocki <rafael@kernel.org> 于2021年1月29日周五 下午9:50写道:
>
> On Fri, Jan 29, 2021 at 9:27 AM Ruifeng Zhang
> <ruifeng.zhang0110@gmail.com> wrote:
> >
> > From: Ruifeng Zhang <ruifeng.zhang1@unisoc.com>
> >
> > Suspend type contains s2ram and s2idle, but syscore is only
> > available for S2RAM.
> >
> > S2idle requires a similar feature,
>
> No, it doesn't.
Why s2idle don't requires this feature ?
I'm need use it for vendor watchdog driver.
Rafael J. Wysocki <rafael@kernel.org> 于2021年1月29日周五 下午9:50写道:
>
> On Fri, Jan 29, 2021 at 9:27 AM Ruifeng Zhang
> <ruifeng.zhang0110@gmail.com> wrote:
> >
> > From: Ruifeng Zhang <ruifeng.zhang1@unisoc.com>
> >
> > Suspend type contains s2ram and s2idle, but syscore is only
> > available for S2RAM.
> >
> > S2idle requires a similar feature,
>
> No, it doesn't.
prev parent reply other threads:[~2021-02-04 9:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210129082726.19406-1-ruifeng.zhang0110@gmail.com>
[not found] ` <YBPNAoitmgnTxiqQ@kroah.com>
2021-02-04 9:06 ` [PATCH] RFC syscore: add suspend type to syscore Ruifeng Zhang
2021-02-04 10:32 ` Greg KH
2021-02-04 13:38 ` Rafael J. Wysocki
2021-02-05 10:27 ` Ruifeng Zhang
2021-02-05 11:39 ` Rafael J. Wysocki
2021-02-05 20:03 ` Ruifeng Zhang
[not found] ` <CAJZ5v0iS92CN5MKHu8tOpQR6mOWu=4=PLqN84qXG+v+64Ro99Q@mail.gmail.com>
2021-02-04 9:09 ` Ruifeng Zhang [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='CAG7+-3PuA3CdZAL5_m9aEuEdw7yaguXCFvasLjk==P9URNZ4QA@mail.gmail.com' \
--to=ruifeng.zhang0110@gmail.com \
--cc=chunyan.zhang@unisoc.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=ruifeng.zhang1@unisoc.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;
as well as URLs for NNTP newsgroup(s).