[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180620132507.GE6242@sirena.org.uk>
Date: Wed, 20 Jun 2018 14:25:07 +0100
From: Mark Brown <broonie@...nel.org>
To: "Rafael J. Wysocki" <rafael@...nel.org>
Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Geert Uytterhoeven <geert+renesas@...der.be>,
Pavel Machek <pavel@....cz>, Len Brown <len.brown@...el.com>,
Marek Vasut <marek.vasut+renesas@...il.com>,
Liam Girdwood <lgirdwood@...il.com>,
Linux PM list <linux-pm@...r.kernel.org>,
Linux-Renesas <linux-renesas-soc@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 1/2] PM / wakeup: Add callback for wake-up change
notification
On Wed, Jun 20, 2018 at 02:15:38PM +0200, Rafael J. Wysocki wrote:
> On Wed, Jun 20, 2018 at 12:35 PM, Mark Brown <broonie@...nel.org> wrote:
> > The flip side of that is that either suspend and resume or poweroff are
> > broken for userspace unless they know about this magic sysfs file which
> > isn't great either.
> But to me that isn't that much different from an RTC wake alarm, say.
> Enabling it to wake up the system in general isn't sufficient, you
> also need to actually set the alarm using a different interface.
It seems more like hardware breakage we're trying to fix than a feature
- it's not like it's adding something we didn't have already (like
setting a time in an alarm where the alarm is an additional thing), more
just trying to execute on an existing user interface successfully. I
can see that there's a case that it doesn't map very well onto the
standard interfaces so perhaps we have to add something on the side as
the hardware is just too horrible to fit in with the standard interfaces
and we have to do that.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists