On Thursday, January 21, 2016 05:05:47 PM Colin King wrote:
> From: Colin Ian King
>
> BugLink: https://bugs.launchpad.net/bugs/1529381
>
> Some HP laptops seem to have invalid 64 bit FADT X_PM* addresses
> which are causing various boot issues. In these cases, it
wanting hibernation can turn off kASLR by adding "nokaslr" to the kernel
> command line.
>
> Suggested-by: Linus Torvalds <torva...@linux-foundation.org>
> Signed-off-by: Kees Cook <keesc...@chromium.org>
Acked-by: Rafael J. Wysocki <rafael.j.wyso...@intel.com&g
On Wed, Apr 6, 2016 at 11:29 PM, Saravana Kannan <skan...@codeaurora.org> wrote:
> On 04/06/2016 02:21 PM, Rafael J. Wysocki wrote:
>>
>> On Wed, Apr 6, 2016 at 10:30 PM, Saravana Kannan <skan...@codeaurora.org>
>> wrote:
>>>
>>> On 09/09
On Wed, Apr 6, 2016 at 11:56 PM, Ingo Molnar <mi...@kernel.org> wrote:
>
> * Rafael J. Wysocki <raf...@kernel.org> wrote:
>
>> On Wed, Apr 6, 2016 at 9:44 PM, Kees Cook <keesc...@chromium.org> wrote:
>> > When building with both CONFIG_HIBERNATION and CO
Hi Jon,
This is a new (and hopefully final) iteration of the series of patches starting
the conversion of power management driver API documentation.
Patch [1/3] updates kerneldoc comments in include/linux/pm.h (to make the
documentation generated out of them look better), patch [2/3] converts
On Monday, January 09, 2017 02:34:39 AM Lukas Wunner wrote:
> On Fri, Jan 06, 2017 at 02:38:13AM +0100, Rafael J. Wysocki wrote:
> > I sent patches [1-2/3] previosly a couple of weeks ago and there have not
> > been any comments since then, so either they are fine by everybody or
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Refresh the struct dev_pm_ops kerneldoc comment, so that it looks
better and is more readable after processing by Sphinx, and drop
the kerneldoc marker from a few other comments ("PM_EVENT_ messages"
and a couple of enum ty
On Mon, Feb 6, 2017 at 7:28 PM, Jonathan Corbet <cor...@lwn.net> wrote:
> On Thu, 02 Feb 2017 01:30:08 +0100
> "Rafael J. Wysocki" <r...@rjwysocki.net> wrote:
>
>> This is a new (and hopefully final) iteration of the series of patches
>> starting
>&
On Tuesday, February 21, 2017 10:30:10 AM Viresh Kumar wrote:
> On 20-02-17, 14:58, Rafael J. Wysocki wrote:
> > Yes, it is called for new and inactive policies.
> >
> > For new policies it has to populate policy->cpus (because otherwise the core
> > doesn't know wha
Hi Jon,
These two patches fix references to struct data types in two documents that
did those things more or less incorrectly.
Both of them fix existing commits, one in the mainline and one in your tree.
Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
On Monday, February 20, 2017 03:26:08 PM Viresh Kumar wrote:
> On 18-02-17, 02:36, Rafael J. Wysocki wrote:
> > +CPU Initialization
> > +==
> > +
>
>
> > +Next, the scaling driver's ``->init()`` callback is invoked with the polic
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
There is a better way to represent structure references than it was
done in device.rst by commit 730c4c053012 (PM / sleep / docs: Convert
PM notifiers document to reST), which is to use "struct name" as a
link caption (e.g.
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
The format of the structure references in device_link.rst is
incorrect, because it doesn't cause proper references to the
struct data types to be generated (for struct dev_pm_domain in
particular).
Fix that by using the :c:type:`struc
On Monday, February 20, 2017 02:58:27 PM Rafael J. Wysocki wrote:
> On Monday, February 20, 2017 03:26:08 PM Viresh Kumar wrote:
> > On 18-02-17, 02:36, Rafael J. Wysocki wrote:
> > > +CPU Initialization
> > > +==
> > > +
> >
>
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
The user/admin documentation of cpufreq is badly outdated. It
conains stale and/or inaccurate information along with things
that are not particularly useful. Also, some of the important
pieces are missing from it.
For this reason, add
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
The user/admin documentation of cpufreq is badly outdated. It
conains stale and/or inaccurate information along with things
that are not particularly useful. Also, some of the important
pieces are missing from it.
For this reason, add
e the stats code non-modular")
Cc: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Cc: Viresh Kumar <viresh.ku...@linaro.org>
---
Documentation/cpu-freq/cpufreq-stats.txt |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-4.8-rc5.orig/Documentation/cpu-freq/cpufreq
On Monday, September 12, 2016 06:14:44 PM Peter Zijlstra wrote:
> On Mon, Sep 12, 2016 at 12:01:58PM -0400, Chris Metcalf wrote:
> > On 9/7/2016 5:11 PM, Francis Giraldeau wrote:
> > >When running only the test_jitter(), the isolation mode is lost:
> > >
> > > [ 6741.566048] isolation/9515:
On Monday, September 12, 2016 11:15:45 PM Rafael J. Wysocki wrote:
> On Monday, September 12, 2016 06:14:44 PM Peter Zijlstra wrote:
> > On Mon, Sep 12, 2016 at 12:01:58PM -0400, Chris Metcalf wrote:
> > > On 9/7/2016 5:11 PM, Francis Giraldeau wrote:
> > > >Whe
On Wed, Jan 4, 2017 at 11:20 PM, Jonathan Corbet <cor...@lwn.net> wrote:
> On Wed, 04 Jan 2017 23:11:30 +0100
> "Rafael J. Wysocki" <r...@rjwysocki.net> wrote:
>
>> I'm assuming then, that you're going to handle cpufreq docs changes in the
>> future.
>
On Wednesday, January 04, 2017 02:35:27 PM Jonathan Corbet wrote:
> On Mon, 2 Jan 2017 12:38:15 +0530
> Viresh Kumar wrote:
>
> > > +The following POWER processors are supported in powernv mode:
> > > +POWER8
> > > +POWER9
>
> I've applied this to the docs tree, thanks.
Hi Everyone,
I sent patches [1-2/3] previosly a couple of weeks ago and there have not been
any comments since then, so either they are fine by everybody or the timing
was particularly bad and no one had the time to look at them. Admittedly, the
former is more attractive to me, so I'll assume
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Move the document describing PM notifiers (used during system sleep
state transitions) to Documentation/driver-api/pm/, convert it to reST
and update it to (a) follow the actual code better and (b) use current
terminology.
Also r
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Refresh the struct dev_pm_ops kerneldoc comment, so that it looks
better and is more readable after processing by Sphinx, and drop
the kerneldoc marker from a few other comments ("PM_EVENT_ messages"
and a couple of enum ty
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Move the document describing the system sleep state transitions API
for devices to Documentation/driver-api/pm/, convert it to reST and
update it to use current terminology. Also remove the remaining
reference to the old version of i
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Refresh the struct dev_pm_ops kerneldoc comment, so that it looks
better and is more readable after processing by Sphinx, and drop
the kerneldoc marker from a few other comments ("PM_EVENT_ messages"
and a couple of enum ty
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Move the document describing the system sleep state transitions API
for devices to Documentation/driver-api/pm/, convert it to reST and
update it to use current terminology. Also remove the remaining
reference to the old version of i
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Move the document describing PM notifiers (used during system sleep
state transitions) to Documentation/driver-api/pm/, convert it to reST
and update it to use current terminology. Also replace the remaining
references to the old v
On Monday, December 19, 2016 09:40:20 PM Rafael J. Wysocki wrote:
> Hi Everyone,
>
> These two patches update kerneldoc comments in include/linux/pm.h ([1/2]) and
> convert Documentation/power/devices.txt to reST ([2/2], RFC).
>
> Please have a look, especially at patch [2/2
Hi Everyone,
These two patches update kerneldoc comments in include/linux/pm.h ([1/2]) and
convert Documentation/power/devices.txt to reST ([2/2], RFC).
Please have a look, especially at patch [2/2], and let me know what can be done
in a better way.
Thanks,
Rafael
--
To unsubscribe from this
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Refresh the struct dev_pm_ops kerneldoc comment, so that it looks
better and is more readable after processing by Sphinx, and drop
the kerneldoc marker from the "PM_EVENT_ messages" comment which
is not a proper kerneldoc a
On Thu, Mar 23, 2017 at 1:27 AM, Kees Cook wrote:
> This is a modified revert of commit 65fe935dd238 ("x86/KASLR, x86/power:
> Remove x86 hibernation restrictions"), since it appears that 32-bit
> hibernation still can't support KASLR. 64-bit is fine. Since people have
>
On Thu, Mar 23, 2017 at 2:23 PM, Evgenii Shatokhin
wrote:
> On 23.03.2017 03:27, Kees Cook wrote:
>>
>> This is a modified revert of commit 65fe935dd238 ("x86/KASLR, x86/power:
>> Remove x86 hibernation restrictions"), since it appears that 32-bit
>> hibernation still
+linux-doc (sorry for omitting it in the first place)
On Thursday, March 09, 2017 04:28:32 PM Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
>
> The user/admin documentation of cpufreq is badly outdated. It
> conains stale and/or inaccurate
On Monday, March 13, 2017 04:54:38 PM Jonathan Corbet wrote:
> On Thu, 09 Mar 2017 16:28:32 +0100
> "Rafael J. Wysocki" <r...@rjwysocki.net> wrote:
>
> > The user/admin documentation of cpufreq is badly outdated. It
> > conains stale and/or ina
On Wednesday, July 19, 2017 03:42:40 PM Viresh Kumar wrote:
> Hi Rafael,
>
> This series tries to cleanup the code around transition-latency and its
> users. Some of the old legacy code, which may not make much sense now,
> is dropped as well. And some code consolidation is also done across
>
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Reorganize the power management part of admin-guide by adding a
description of major power management strategies supported by the
kernel (system-wide and working-state power management) to it and
dividing the rest of the ma
On Sun, Aug 20, 2017 at 8:23 PM, Lukas Wunner <lu...@wunner.de> wrote:
> On Sun, Aug 20, 2017 at 06:05:05PM +0200, Rafael J. Wysocki wrote:
>> From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
>>
>> Reorganize the power management part of admin-guide by addin
On Friday, May 05, 2017 11:38:42 PM Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
>
> Add a document describing the current behavior and user space
> interface of the intel_pstate driver in the RST format and
> drop the existing outdated inte
On Friday, May 12, 2017 03:20:48 PM Jonathan Corbet wrote:
> On Fri, 12 May 2017 22:47:25 +0200
> "Rafael J. Wysocki" <r...@rjwysocki.net> wrote:
>
> > > Hi Jon,
> > >
> > > All of the dependencies for this patch have been merged, so I can rou
: dbx500: add a Kconfig symbol
Dan Carpenter (1):
PowerCap: Fix an error code in powercap_register_zone()
Juri Lelli (1):
cpufreq: schedutil: use now as reference when aggregating shared
policy requests
Pushkar Jambhlekar (1):
PM / hibernate: Declare variables as static
Rafael J
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Add a document describing the current behavior and user space
interface of the intel_pstate driver in the RST format and
drop the existing outdated intel_pstate.txt document.
Also update admin-guide/pm/cpufreq.rst with proper RST refe
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Drop an excess "`" from Documentation/driver-api/pm/devices.rst.
Fixes: 2728b2d2e5be (PM / core / docs: Convert sleep states API document to
reST)
Signed-off-by: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
---
Docum
On Tue, Oct 10, 2017 at 7:36 PM, Tom Saeger <tom.sae...@oracle.com> wrote:
> Make driver-api document refs valid.
>
> Signed-off-by: Tom Saeger <tom.sae...@oracle.com>
Acked-by: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
> ---
> Documentation/po
On Tue, Oct 10, 2017 at 7:36 PM, Tom Saeger <tom.sae...@oracle.com> wrote:
> Make admin-guide document refs valid.
>
> Signed-off-by: Tom Saeger <tom.sae...@oracle.com>
Acked-by: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
> ---
> Documentation/ABI/sta
On Friday, October 13, 2017 8:48:30 AM CEST Ulf Hansson wrote:
> On 13 October 2017 at 02:33, Rafael J. Wysocki <r...@rjwysocki.net> wrote:
> > From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
> >
> > Fix kerneldoc comments of __device_suspend_n
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Define and document a new driver flag, DPM_FLAG_AVOID_RPM, to inform
the PM core and middle layer code that the driver has something
significant to do in its ->suspend and/or ->resume callbacks and
runtime PM should be disabled fo
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Move the LPSS-specific code from acpi_lpss_runtime_suspend()
and acpi_lpss_runtime_resume() into separate functions,
acpi_lpss_suspend() and acpi_lpss_resume(), respectively, and
make acpi_lpss_suspend_late() and acpi_lpss_resume_early
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Optimize the power management in i2c-designware-platdrv by making it
set the DPM_FLAG_SMART_SUSPEND and DPM_FLAG_LEAVE_SUSPENDED which
allows some code to be dropped from its PM callbacks.
First, setting DPM_FLAG_SMART_SUSPEND causes the
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Make the ACPI PM domain take DPM_FLAG_SMART_SUSPEND into account in
its system suspend callbacks.
[Note that the pm_runtime_suspended() check in acpi_dev_needs_resume()
is an optimization, because if is not passed, all of the subsequent
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Define and document a new driver flag, DPM_FLAG_LEAVE_SUSPENDED, to
instruct the PM core that it is desirable to leave the device in
runtime suspend after system resume (for example, the device may be
slow to resume and it may be
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Make the PCI bus type take DPM_FLAG_SMART_SUSPEND into account in its
system suspend callbacks and make sure that all code that should not
run in parallel with pci_pm_runtime_resume() is executed in the "late"
phases of system
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Define and document a SMART_SUSPEND flag to instruct bus types and PM
domains that the system suspend callbacks provided by the driver can
cope with runtime-suspended devices, so from the driver's perspective
it should be safe to leave d
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
The only user of non-empty pcibios_pm_ops is s390 and it only uses
"noirq" callbacks, so drop the invocations of the other pcibios_pm_ops
callbacks from the PCI PM code.
That will allow subsequent changes to be somewhat simp
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Modify i2c-designware-platdrv to set DPM_FLAG_SMART_PREPARE for its
devices and return 0 from the system suspend ->prepare callback
if the device has an ACPI companion object in order to tell the PM
core and middle layers to avoid
Hi All,
Well, this took more time than expected, as I tried to cover everything I had
in mind regarding PM flags for drivers.
This work was triggered by attempts to fix and optimize PM in the
i2c-designware-platdev driver that ended up with adding a couple of
flags to the driver's internal data
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
The motivation for this change is to provide a way to work around
a problem with the direct-complete mechanism used for avoiding
system suspend/resume handling for devices in runtime suspend.
The problem is that some middle layer code (t
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Replace the PCI-specific flag PCI_DEV_FLAGS_NEEDS_RESUME with the
PM core's DPM_FLAG_NEVER_SKIP one everywhere and drop it.
Signed-off-by: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
---
drivers/gpu/drm/i915/i915_drv.c |2
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Make the intel-lpss driver set DPM_FLAG_SMART_SUSPEND for its
devices which will allow them to stay in runtime suspend during
system suspend unless they need to be reconfigured for some reason.
Also make it avoid resuming its child d
On Monday, October 16, 2017 7:34:52 AM CEST Lukas Wunner wrote:
> On Mon, Oct 16, 2017 at 03:29:02AM +0200, Rafael J. Wysocki wrote:
> > + :c:func:`dev_pm_set_driver_flags` helper function.] If the first of
> > + tese flags is set, the PM core will not apply the
On Mon, Oct 16, 2017 at 9:08 AM, Greg Kroah-Hartman
<gre...@linuxfoundation.org> wrote:
> On Mon, Oct 16, 2017 at 03:12:35AM +0200, Rafael J. Wysocki wrote:
>> Hi All,
>>
>> Well, this took more time than expected, as I tried to cover everything I had
>> in mi
On Monday, October 16, 2017 8:28:52 AM CEST Greg Kroah-Hartman wrote:
> On Mon, Oct 16, 2017 at 03:29:02AM +0200, Rafael J. Wysocki wrote:
> > struct dev_pm_info {
> > pm_message_tpower_state;
> > unsigned intcan_wakeup:1;
> > @@ -561,6 +
On Monday, October 16, 2017 8:31:22 AM CEST Greg Kroah-Hartman wrote:
> On Mon, Oct 16, 2017 at 03:29:02AM +0200, Rafael J. Wysocki wrote:
> > +static inline void dev_pm_set_driver_flags(struct device *dev, unsigned
> > int flags)
> > +{
> > + dev->power.driver_fla
On Tuesday, October 17, 2017 10:36:39 AM CEST Ulf Hansson wrote:
> On 16 October 2017 at 03:12, Rafael J. Wysocki <r...@rjwysocki.net> wrote:
> > Hi All,
> >
> > Well, this took more time than expected, as I tried to cover everything I
> > had
> >
On Tuesday, October 17, 2017 9:15:43 AM CEST Greg Kroah-Hartman wrote:
> On Tue, Oct 17, 2017 at 12:05:11AM +0200, Rafael J. Wysocki wrote:
> > On Monday, October 16, 2017 8:28:52 AM CEST Greg Kroah-Hartman wrote:
> > > On Mon, Oct 16, 2017 at 03:29:02AM +0200, Rafae
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Fix the kerneldoc comments of __device_suspend_noirq(),
__device_suspend_late() and __device_suspend() where the function
names in kerneldoc don't match the actual names of the functions.
Also fix the device_resume_noirq() kerneldoc c
e
> +is supported. Refer to Documentation/power/basic-pm-debugging.txt for the
> description of the 'test_resume' option.
>
> To select an option, write the string representing it to /sys/power/disk.
> --
Acked-by: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
--
To
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Fix kerneldoc comments of __device_suspend_noirq(),
__device_suspend_late() and __device_suspend() where the function
names in kerneldoc don't match the actual names of the functions.
Signed-off-by: Rafael J. Wysocki <rafa
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Commit 33fc30b47098 (cpufreq: intel_pstate: Document the current
behavior and user interface) dropped the intel-pstate.txt file
from Documentation/cpu-freq/, but it did not update the index.txt
file in there accordingly, so do that now.
On Mon, Aug 21, 2017 at 11:51 AM, Markus Heiser
<markus.hei...@darmarit.de> wrote:
> Hi Rafael,
>
> great work, helps me and the world saving fossil fuels ;)
Thanks!
>> Am 20.08.2017 um 18:05 schrieb Rafael J. Wysocki <r...@rjwysocki.net>:
>>
>>
On Monday, August 21, 2017 9:39:17 AM CEST Markus Heiser wrote:
>
> > Am 20.08.2017 um 18:06 schrieb Rafael J. Wysocki <r...@rjwysocki.net>:
> >
> > From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
> >
> > The Documentation/power/states.t
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Reorganize the power management part of admin-guide by adding a
description of major power management strategies supported by the
kernel (system-wide and working-state power management) to it and
dividing the rest of the ma
On Monday, August 21, 2017 3:14:56 PM CEST Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
>
> Reorganize the power management part of admin-guide by adding a
> description of major power management strategies supported by the
> kernel (sy
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Commit 7aa7a0360a66 (PM: docs: Delete the obsolete states.txt
document) forgot to update kernel-parameters.txt with a reference
to the new sleep-states.rst document and it still points to
states.txt that was dropped, so fix it now.
On Wednesday, October 18, 2017 2:39:24 AM CEST Rafael J. Wysocki wrote:
> On Tuesday, October 17, 2017 9:41:16 PM CEST Ulf Hansson wrote:
>
> [cut]
>
> > >
> > >> deploying this and from a middle layer point of view, all the trivial
> > >> cas
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
There is one word too many under formatting markup in one place
in device.rst, so fix it.
Signed-off-by: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
---
Documentation/driver-api/pm/devices.rst |2 +-
1 file changed, 1 ins
On Tuesday, October 17, 2017 5:33:17 PM CEST Andy Shevchenko wrote:
> On Mon, 2017-10-16 at 03:32 +0200, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
> >
> > Define and document a new driver flag, DPM_FLAG_AVOID_RPM, to inform
>
On Tuesday, October 17, 2017 10:12:19 PM CEST Alan Stern wrote:
> On Tue, 17 Oct 2017, Ulf Hansson wrote:
>
> > > These functions are wrong, however, because they attempt to reuse the
> > > whole callback *path* instead of just reusing driver callbacks. The
> > > *only* reason why it all "works"
On Tuesday, October 17, 2017 9:41:16 PM CEST Ulf Hansson wrote:
[cut]
> >
> >> deploying this and from a middle layer point of view, all the trivial
> >> cases supports this.
> >
> > These functions are wrong, however, because they attempt to reuse the
> > whole callback *path* instead of just
On Wednesday, October 18, 2017 1:57:52 PM CEST Ulf Hansson wrote:
> On 18 October 2017 at 02:39, Rafael J. Wysocki <r...@rjwysocki.net> wrote:
> > On Tuesday, October 17, 2017 9:41:16 PM CEST Ulf Hansson wrote:
> >
> > [cut]
> >
> >> >
> >> &
On Monday, October 23, 2017 6:37:41 PM CEST Ulf Hansson wrote:
> On 19 October 2017 at 01:17, Rafael J. Wysocki <r...@rjwysocki.net> wrote:
> > From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
> >
> > The motivation for this change is to provide a
On Wednesday, October 18, 2017 9:45:11 PM CEST Grygorii Strashko wrote:
>
> On 10/18/2017 09:11 AM, Ulf Hansson wrote:
[...]
> >>> That's the point. We know pm_runtime_force_* works nicely for the
> >>> trivial middle-layer cases.
> >>
> >> In which cases the middle-layer callbacks don't exist,
On Wednesday, October 18, 2017 4:11:33 PM CEST Ulf Hansson wrote:
> [...]
>
> >>
> >> The reason why pm_runtime_force_* needs to respects the hierarchy of
> >> the RPM callbacks, is because otherwise it can't safely update the
> >> runtime PM status of the device.
> >
> > I'm not sure I follow
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
The motivation for this change is to provide a way to work around
a problem with the direct-complete mechanism used for avoiding
system suspend/resume handling for devices in runtime suspend.
The problem is that some middle layer code (t
On Wednesday, October 18, 2017 2:34:10 PM CEST Ulf Hansson wrote:
> [...]
>
> >> Are there any major reasons why the appended patch (obviously untested)
> >> won't
> >> work, then?
> >
> > OK, there is a reason, which is the optimizations bundled into
> > pm_runtime_force_*, because (a) the
On Tuesday, October 24, 2017 7:22:25 AM CEST Ulf Hansson wrote:
> On 16 October 2017 at 03:29, Rafael J. Wysocki <r...@rjwysocki.net> wrote:
> > From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
> >
> > Define and document a SMART_SUSPEND flag to inst
On Wed, Nov 15, 2017 at 8:43 AM, Ulf Hansson <ulf.hans...@linaro.org> wrote:
> On 12 November 2017 at 01:42, Rafael J. Wysocki <r...@rjwysocki.net> wrote:
>> From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
>>
>> Add helper routines to find and return
On Tuesday, November 14, 2017 5:07:59 PM CET Ulf Hansson wrote:
> On 11 November 2017 at 00:45, Rafael J. Wysocki <raf...@kernel.org> wrote:
> > On Fri, Nov 10, 2017 at 10:09 AM, Ulf Hansson <ulf.hans...@linaro.org>
> > wrote:
> >> On 8 November
On Fri, Nov 17, 2017 at 12:07 AM, Rafael J. Wysocki <r...@rjwysocki.net> wrote:
> On Thursday, November 16, 2017 4:10:16 PM CET Ulf Hansson wrote:
>> On 12 November 2017 at 01:37, Rafael J. Wysocki <r...@rjwysocki.net> wrote:
>> > From: Rafael J. Wysoc
On Fri, Nov 17, 2017 at 2:49 PM, Ulf Hansson wrote:
> [...]
>
>>>
> Second, have you considered setting the default value of
> dev->power.may_skip_resume to true?
Yes.
> That would means the subsystem
> instead need to implement an opt-out
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Define and document a new driver flag, DPM_FLAG_LEAVE_SUSPENDED, to
instruct the PM core and middle-layer (bus type, PM domain, etc.)
code that it is desirable to leave the device in runtime suspend
after system-wide transitions to the w
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Add support for DPM_FLAG_LEAVE_SUSPENDED to the ACPI PM domain by
making it (a) set the power.may_skip_resume status bit for devices
that, from its perspective, may be left in suspend after system
wakeup from sleep and (b) return earl
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Make the PM core handle DPM_FLAG_LEAVE_SUSPENDED directly for
devices whose "noirq", "late" and "early" driver callbacks are
invoked directly by it.
Namely, make it skip all of the system-wi
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Make the PM core avoid invoking the "late" and "noirq" system-wide
suspend (or analogous) callbacks for devices that are in runtime
suspend during the corresponding phases of system-wide suspend
(or analogous) tr
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Add support for DPM_FLAG_LEAVE_SUSPENDED to the PCI bus type by
making it (a) set the power.may_skip_resume status bit for devices
that, from its perspective, may be left in suspend after system
wakeup from sleep and (b) return earl
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Add helper routines to find and return a suitable subsystem callback
during the "noirq" phases of system suspend/resume (or analogous)
transitions as well as during the "late" phase of system suspend and
the &quo
Hi All,
The following still applies:
> On Wednesday, November 8, 2017 1:41:35 AM CET Rafael J. Wysocki wrote:
> >
> > This is a follow-up for the first part of the PM driver flags series
> > sent previously some time ago with an intro as follows:
> >
> > On Sa
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Add helper routines to find and return a suitable subsystem callback
during the "noirq" phases of system suspend/resume (or analogous)
transitions as well as during the "late" phase of system suspend and
the &quo
Hi All,
The following still applies:
On Wednesday, November 8, 2017 1:41:35 AM CET Rafael J. Wysocki wrote:
>
> This is a follow-up for the first part of the PM driver flags series
> sent previously some time ago with an intro as follows:
>
> On Saturday, October 28, 2017 12:11:5
From: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Make the PM core handle DPM_FLAG_LEAVE_SUSPENDED directly for
devices whose "noirq", "late" and "early" driver callbacks are
invoked directly by it.
Namely, make it skip all of the system-wi
1 - 100 of 138 matches
Mail list logo