Re: [PATCH] RFC syscore: add suspend type to syscore

From: Greg KH
Date: Thu Feb 04 2021 - 05:35:06 EST


On Thu, Feb 04, 2021 at 05:06:25PM +0800, Ruifeng Zhang wrote:
> Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> 于2021年1月29日周五 下午4:53写道:
> >
> > On Fri, Jan 29, 2021 at 04:27:26PM +0800, Ruifeng Zhang wrote:
> > > From: Ruifeng Zhang <ruifeng.zhang1@xxxxxxxxxx>
> > >
> > > Suspend type contains s2ram and s2idle, but syscore is only
> > > available for S2RAM.
> >
> > Who else needs this?
> In the s2idle suspend and resume, some vendors want to do some
> things, for example the vendor implemented the watchdog driver.

We can not add things to the kernel for code that is not in the kernel
tree itself, you know this. Please don't try to go around this
well-known rule.

> The GKI requires that no modification of the kernel source is allowed,
> so an syscore_s2idle is added for use.

I have no idea what "GKI" is with regards to the kernel project, sorry.

> The reason device_suspend was not chosen was that I wanted it to
> monitor for longer periods, such as between device_suspend and
> syscore_suspend.

Why does that matter? What do you do with that information?

> > > S2idle requires a similar feature, so a new parameter
> > > "enum suspend_type" is added to distinguish it.
> >
> > Who requires this export?
> >
> > I don't see a user of this new code/api in this patch, so why would it
> > be accepted?
> >
> > Also, you are doing many different things in the same patch, please
> > break this up into a patch series where you only do one logical change
> > at a time.
> I think it's only one things in patch
> 0001-RFC-syscore-add-suspend-type-to-syscore.patch,

I do not understand what you mean here, emails do not name patches :)

> add a new s2ildle type for syscore.

But why is that needed?

thanks,

greg k-h