off-by: Vincent Guittot
Acked-by: Rafael J. Wysocki
and I think I've given the tag on this patch already.
> ---
> drivers/cpufreq/cpufreq.c | 36
> include/linux/cpufreq.h | 10 ++
> 2 files changed, 46 insertions(+)
>
> di
On Tue, Nov 21, 2023 at 2:44 PM Russell King wrote:
>
> From: James Morse
>
> Neither arm64 nor riscv support physical hotadd of CPUs that were not
> present at boot. For arm64 much of the platform description is in static
> tables which do not have update methods. arm64 does support HOTPLUG_CPU,
icy before this point anyway.
>
> Signed-off-by: James Morse
> Reviewed-by: Gavin Shan
> Signed-off-by: Russell King (Oracle)
Acked-by: Rafael J. Wysocki
and I'd suggest sending this separately to the x86 list.
> ---
> subsys_initcall_sync() would be an option, but mov
On Tue, Oct 24, 2023 at 5:15 PM Russell King (Oracle)
wrote:
>
> Hi,
>
> I'm posting James' patch set updated with most of the review comments
> from his RFC v2 series back in September. Individual patches have a
> changelog attached at the bottom of the commit message. Those which
> I have finish
On Tue, Oct 24, 2023 at 5:17 PM Russell King wrote:
>
> From: James Morse
>
> Today the ACPI enumeration code 'visits' all devices that are present.
>
> This is a problem for arm64, where CPUs are always present, but not
> always enabled. When a device-check occurs because the firmware-policy
> h
On Mon, Jul 15, 2019 at 4:43 PM Joel Fernandes (Google)
wrote:
>
> list_for_each_entry_rcu has built-in RCU and lock checking. Make use of
> it for acpi_ioremaps list traversal.
>
> Signed-off-by: Joel Fernandes (Google)
Acked-by: Rafael J. Wysocki
> ---
> drivers/acpi/
On Fri, Jul 5, 2019 at 11:04 PM Shreeya Patel
wrote:
>
> Convert core file to ReST format, in order to allow it to
> be parsed by Sphinx. Make a minor change of correcting the wrong
> function name cpufreq_put_cpu to cpufreq_cpu_put.
> Also create an index.rst file in cpu-freq and add it's entry
>
On Friday, June 28, 2019 2:20:37 PM CEST Mauro Carvalho Chehab wrote:
> The intel-int3496.txt file is a documentation for an ACPI driver.
>
> There's no reason to keep it on a separate directory.
>
> So, instead of keeping it on some random location, move it
> to a sub-directory inside the ACPI d
On Wednesday, July 3, 2019 3:53:31 AM CEST Srinivas Pandruvada wrote:
> Added myself as the maintainer.
>
> Signed-off-by: Srinivas Pandruvada
Acked-by: Rafael J. Wysocki
> ---
> MAINTAINERS | 8
> 1 file changed, 8 insertions(+)
>
> diff --git a/MAINTAINE
tel-speed-select perf-profile --help
>
> To get help for a command for a feature for example
> $sudo intel-speed-select perf-profile get-lock-status --help
>
> Signed-off-by: Srinivas Pandruvada
Acked-by: Rafael J. Wysocki
> ---
> Updates:
> - Copied Makefile from tools
On Wed, Jun 19, 2019 at 11:59 AM Rafael J. Wysocki wrote:
>
> On Tuesday, June 18, 2019 11:05:44 PM CEST Mauro Carvalho Chehab wrote:
> > The intel-int3496.txt file is a documentation for an ACPI driver.
> >
> > There's no reason to keep it on a separate directory.
&
ub-directory inside the ACPI documentation dir.
>
> For now, keep it with .txt extension, in order to avoid
> Sphinx build noise. A later patch should change it to .rst
> and movin it to be together with other acpi docs.
>
> Signed-off-by: Mauro Carvalho Chehab
Acked-by: Rafael
ad of "What", they use "Where".
>
> Signed-off-by: Mauro Carvalho Chehab
> Signed-off-by: Mauro Carvalho Chehab
Acked-by: Rafael J. Wysocki
> ---
> Documentation/ABI/testing/pstore | 2 +-
> .../sysfs-bus-event_source-devices-format
On Sun, Jun 9, 2019 at 4:30 AM Mauro Carvalho Chehab
wrote:
>
> The conversion is actually:
> - add blank lines and identation in order to identify paragraphs;
> - fix tables markups;
> - add some lists markups;
> - mark literal blocks;
> - adjust title markups.
>
> At its new index.rst,
gned-off-by: Mauro Carvalho Chehab
Acked-by: Rafael J. Wysocki
> ---
> Documentation/ABI/testing/sysfs-devices-system-cpu | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/ABI/testing/sysfs-devices-system-cpu
> b/Documentation/ABI/test
On Mon, May 20, 2019 at 4:48 PM Mauro Carvalho Chehab
wrote:
>
> Mostly due to x86 and acpi conversion, several documentation
> links are still pointing to the old file. Fix them.
>
> Signed-off-by: Mauro Carvalho Chehab
For the ACPI part:
Acked-by: Rafael J. Wysocki
On Fri, Jan 18, 2019 at 12:11 PM Quentin Perret wrote:
>
> On Friday 18 Jan 2019 at 12:01:35 (+0100), Rafael J. Wysocki wrote:
> > On Fri, Jan 18, 2019 at 11:58 AM Rafael J. Wysocki
> > wrote:
> > >
> > > On Fri, Jan 18, 2019 at 11:34 AM Quentin Perret
&g
On Fri, Jan 18, 2019 at 11:58 AM Rafael J. Wysocki wrote:
>
> On Fri, Jan 18, 2019 at 11:34 AM Quentin Perret
> wrote:
> >
> > Hi Rafael,
> >
> > On Friday 18 Jan 2019 at 10:57:08 (+0100), Rafael J. Wysocki wrote:
> > > On Fri, Jan 18, 201
On Fri, Jan 18, 2019 at 11:34 AM Quentin Perret wrote:
>
> Hi Rafael,
>
> On Friday 18 Jan 2019 at 10:57:08 (+0100), Rafael J. Wysocki wrote:
> > On Fri, Jan 18, 2019 at 10:16 AM Quentin Perret
> > wrote:
> > >
> > > Hi Juri,
> > >
> >
On Fri, Jan 18, 2019 at 10:16 AM Quentin Perret wrote:
>
> Hi Juri,
>
> On Thursday 17 Jan 2019 at 16:51:17 (+0100), Juri Lelli wrote:
> > On 10/01/19 11:05, Quentin Perret wrote:
> [...]
> > > +The idea behind introducing an EM is to allow the scheduler to evaluate
> > > the
> > > +implications
On Thu, Jan 17, 2019 at 11:56 AM Ulf Hansson wrote:
>
> On Wed, 16 Jan 2019 at 23:10, Rafael J. Wysocki wrote:
> >
> > On Wed, Jan 9, 2019 at 11:54 AM Rafael J. Wysocki
> > wrote:
> > >
> > > From: Rafael J. Wysocki
> > >
> > >
On Wed, Jan 9, 2019 at 11:54 AM Rafael J. Wysocki wrote:
>
> From: Rafael J. Wysocki
>
> Replace the remaining documents under Documentation/cpuidle/
> with one more complete governor and driver API document for cpuidle
> under Documentation/driver-api/pm/.
>
> Signed-o
On Mon, Jan 14, 2019 at 11:39 AM Daniel Lezcano
wrote:
>
>
> Hi Rafael,
>
> sorry for the delay.
>
> On 10/01/2019 11:20, Rafael J. Wysocki wrote:
>
> [ ... ]
>
> >>> if (entered_state >= 0) {
> >>> +
On Thu, Jan 10, 2019 at 10:53 AM Daniel Lezcano
wrote:
>
> On 10/12/2018 12:30, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > Add two new metrics for CPU idle states, "above" and "below", to count
> > the number of times the given
From: Rafael J. Wysocki
Replace the remaining documents under Documentation/cpuidle/
with one more complete governor and driver API document for cpuidle
under Documentation/driver-api/pm/.
Signed-off-by: Rafael J. Wysocki
---
On top of https://patchwork.kernel.org/patch/10747185
On Wednesday, January 9, 2019 12:56:51 AM CET Otto Sabart wrote:
>
> --LZvS9be/3tNcYl/X
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> Old cpuidle/sysfs.txt file was replaced in aa5eee355b46. So, refer to
> an updated f
From: Rafael J. Wysocki
Update the MAINTAINERS entry for cpuidle by making it clear that it
is not just drivers and adding a documentation record to it.
Signed-off-by: Rafael J. Wysocki
---
MAINTAINERS |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Index: linux-pm/MAINTAINERS
From: Rafael J. Wysocki
Update the MAINTAINERS entry for cpufreq by making it clear that it
is not just drivers and adding current documentation records to it.
Signed-off-by: Rafael J. Wysocki
---
MAINTAINERS |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
Index: linux-pm
On Wed, Dec 12, 2018 at 10:57 AM Ulf Hansson wrote:
>
> On Wed, 12 Dec 2018 at 10:46, Peter Zijlstra wrote:
> >
> > On Tue, Dec 11, 2018 at 10:51:48AM +0100, Rafael J. Wysocki wrote:
> > > On Mon, Dec 10, 2018 at 11:51 PM Peter Zijlstra
> > > wrote:
On Friday, November 16, 2018 11:24:19 PM CET Srinivas Pandruvada wrote:
> Force HWP Request MAX = HWP Request MIN = HWP Capability MIN and EPP to
> 0xFF. In this way the performance limits on the offlined CPU will not
> influence performance limits on its sibling CPU, which is still online.
>
> If
On Mon, Dec 10, 2018 at 11:51 PM Peter Zijlstra wrote:
>
> On Mon, Dec 10, 2018 at 10:36:40PM +0100, Rafael J. Wysocki wrote:
> > On Mon, Dec 10, 2018 at 1:21 PM Peter Zijlstra wrote:
>
> > > One question on this; why is this tracked unconditionally?
> >
> &g
On Mon, Dec 10, 2018 at 1:21 PM Peter Zijlstra wrote:
>
> On Mon, Dec 10, 2018 at 12:30:23PM +0100, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > Add two new metrics for CPU idle states, "above" and "below", to count
> > the numb
From: Rafael J. Wysocki
Add two new metrics for CPU idle states, "above" and "below", to count
the number of times the given state had been asked for (or entered
from the kernel's perspective), but the observed idle duration turned
out to be too short or too long for
On Fri, Dec 7, 2018 at 1:57 PM Lorenzo Pieralisi
wrote:
>
> On Fri, Dec 07, 2018 at 12:57:00PM +0100, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> > Subject: [PATCH] cpuidle: Add 'above' and 'below' idle state metrics
> >
> > Add two n
On Friday, December 7, 2018 1:02:05 PM CET Quentin Perret wrote:
> Hi Rafael,
>
> On Friday 07 Dec 2018 at 12:57:00 (+0100), Rafael J. Wysocki wrote:
> > --- linux-pm.orig/Documentation/ABI/testing/sysfs-devices-system-cpu
> > +++ linux-pm/Documentation/ABI/testing/sys
From: Rafael J. Wysocki
Subject: [PATCH] cpuidle: Add 'above' and 'below' idle state metrics
Add two new metrics for CPU idle states, "above" and "below", to count
the number of times the given state had been asked for (or entered
from the kernel's
On Thu, Dec 6, 2018 at 12:08 AM Doug Smythies wrote:
>
> Hi Rafael,
>
> On 2018.12.03 04:32 Rafael J. Wysocki wrote:
>
> > Add two new metrics for CPU idle states, "high" and "low", to count
> > the number of times the given state had been asked fo
From: Rafael J. Wysocki
Add cpuidle.governor= command line parameter to allow the default
cpuidle governor to be replaced.
That is useful, for example, if someone running a tickful kernel
wants to use the menu governor on it.
Signed-off-by: Rafael J. Wysocki
---
On top of https
From: Rafael J. Wysocki
Subject: [PATCH] cpuidle: Add 'high' and 'low' idle state metrics
Add two new metrics for CPU idle states, "high" and "low", to count
the number of times the given state had been asked for (or entered
from the kernel's perspe
From: Rafael J. Wysocki
When computing the limit of time to spend in the loop in poll_idle(),
use the target residency of the first enabled idle state deeper than
state 0 instead of always using the target residency of state 1.
This helps when state 1 is disabled for diagnostics, for instance
From: Rafael J. Wysocki
Add two new metrics for CPU idle states, "high" and "low", to count
the number of times the given state had been asked for (or entered
from the kernel's perspective), but the observed idle duration turned
out to be too high or too low for it (resp
On Thu, Nov 29, 2018 at 10:40 PM Jonathan Corbet wrote:
>
> On Thu, 29 Nov 2018 22:22:04 +0100
> "Rafael J. Wysocki" wrote:
>
> > Important information is missing from user/admin cpuidle documentation
> > available today, so add a new user/admin document for
From: Rafael J. Wysocki
Important information is missing from user/admin cpuidle documentation
available today, so add a new user/admin document for cpuidle containing
current and comprehensive information to admin-guide and drop the old
.txt documents it is replacing.
Signed-off-by: Rafael J
On Thu, Nov 29, 2018 at 9:07 AM Ulf Hansson wrote:
>
> On Wed, 28 Nov 2018 at 12:47, Rafael J. Wysocki wrote:
> >
> > From: Rafael J. Wysocki
> >
> > Important information is missing from user/admin cpuidle documentation
> > available today, so add a
From: Rafael J. Wysocki
Important information is missing from user/admin cpuidle documentation
available today, so add a new user/admin document for cpuidle containing
current and comprehensive information to admin-guide and drop the old
.txt documents it is replacing.
Signed-off-by: Rafael J
On Wed, Nov 28, 2018 at 10:31 AM Viresh Kumar wrote:
>
> On 28-11-18, 10:11, Rafael J. Wysocki wrote:
> > On Wed, Nov 28, 2018 at 6:48 AM Viresh Kumar
> > wrote:
> > >
> > > On 26-11-18, 14:11, Rafael J. Wysocki wrote:
> > > > From: Rafael J. W
On Wed, Nov 28, 2018 at 6:48 AM Viresh Kumar wrote:
>
> On 26-11-18, 14:11, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > Important information is missing from user/admin cpuidle documentation
> > available today, so add a new user/admin document for
From: Rafael J. Wysocki
Important information is missing from user/admin cpuidle documentation
available today, so add a new user/admin document for cpuidle containing
current and comprehensive information to admin-guide and drop the old
.txt documents it is replacing.
Signed-off-by: Rafael J
On Monday, November 19, 2018 11:16:15 AM CET David Hildenbrand wrote:
> Let's use pfn_to_online_page() instead of pfn_to_page() when checking
> for saveable pages to not save/restore offline memory sections.
>
> Cc: "Rafael J. Wysocki"
> Cc: Pavel Machek
> C
On Monday, November 19, 2018 11:16:16 AM CET David Hildenbrand wrote:
> The content of pages that are marked PG_offline is not of interest
> (e.g. inflated by a balloon driver), let's skip these pages.
>
> Cc: "Rafael J. Wysocki"
> Cc: Pavel Machek
> Cc: Len
Hi Linus,
Please pull from the tag
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
pm-4.20-rc3
with top-most commit 97dc6c03c1b0a9af7aa26da7b0b266a762451f5f
Merge branch 'pm-cpuidle'
on top of commit 651022382c7f8da46cb4872a545ee1da6d097d2a
Linux 4.20-rc1
to receive p
On Monday, October 15, 2018 7:37:18 PM CEST Srinivas Pandruvada wrote:
> This series presents base frequency to cpufreq sysfs when intel_pstate
> is in use in HWP mode.
>
> Changes:
> v4:
> - Documentation update only as suggested by Rafael
>
> v3:
> - Update documentation
> v2
> - Removed guaran
On Fri, Oct 12, 2018 at 6:44 PM Srinivas Pandruvada
wrote:
>
> Updated documentation to explain base_frequency attribute.
>
> Signed-off-by: Srinivas Pandruvada
> ---
> Documentation/admin-guide/pm/intel_pstate.rst | 4
> 1 file changed, 4 insertions(+)
>
> diff --git a/Documentation/admin-
On Saturday, September 1, 2018 6:51:15 AM CEST Vladimir D. Seleznev wrote:
> This commit updates the default value of /sys/power/image_size in
> the documentation.
>
> Since ac5c24ec1e983313ef0015258fba6f630e54e7cn the `image_size' value is
> set to about 2/5 of RAM, according to kernel/power/snap
On Wed, May 23, 2018 at 3:34 AM, Dou Liyang wrote:
> At 05/22/2018 09:47 AM, Dou Liyang wrote:
>>
>>
>>
>> At 05/19/2018 11:06 PM, Thomas Gleixner wrote:
>>>
>>> On Tue, 20 Mar 2018, Dou Liyang wrote:
>>>
ACPI driver should make sure all the processor IDs in their ACPI
Namespace
are
On Wednesday, April 25, 2018 12:07:03 PM CEST Jonathan Neuschäfer wrote:
> Signed-off-by: Jonathan Neuschäfer
> ---
> Documentation/admin-guide/pm/sleep-states.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/admin-guide/pm/sleep-states.rst
> b/Document
t; > to scaling_cur_freq (as currently stated).
> >
> > Fix it.
> Thanks for the fix.
>
> >
> > Signed-off-by: Juri Lelli
> > Cc: Jonathan Corbet
> > Cc: "Rafael J. Wysocki"
> > Cc: Srinivas Pandruvada
> > Cc: li
bitmap of size 0xFF instead of a u64 for the GPE mask so 256
> GPEs can be masked.
>
> Fixes: 9c4aa1eecb48 ("ACPI / sysfs: Provide quirk mechanism to prevent GPE
> flooding")
> Signed-off-by: Prarit Bharava
> Cc: Lv Zheng
> Cc: Jonathan Corbet
> Cc: &qu
..@vger.kernel.org
> Cc: linux-a...@vger.kernel.org
> Cc: linux-ser...@vger.kernel.org
> Cc: Bhupesh Sharma
> Cc: Lv Zheng
> Cc: Thomas Gleixner
> Cc: Ingo Molnar
> Cc: "H. Peter Anvin"
> Cc: x...@kernel.org
> Cc: Jonathan Corbet
> Cc: Catalin Marinas
&g
On Sunday, December 3, 2017 11:56:40 PM CET Ognjen Galic wrote:
> Add support for the ACPI batteries on newer thinkpad models
> (>Sandy Bridge) that support the setting of start and stop
> thresholds.
>
> The actual interface to the driver is a extension for the
> existing ACPI battery driver. Thi
On Wednesday, November 22, 2017 2:10:51 AM CET Rafael J. Wysocki wrote:
> On Monday, November 20, 2017 2:42:26 PM CET Ulf Hansson wrote:
> > On 18 November 2017 at 15:41, Rafael J. Wysocki wrote:
> > > From: Rafael J. Wysocki
> > >
> > > Make the PM core hand
On Monday, November 20, 2017 2:42:26 PM CET Ulf Hansson wrote:
> On 18 November 2017 at 15:41, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > Make the PM core handle DPM_FLAG_LEAVE_SUSPENDED directly for
> > devices whose "noirq", "late&quo
On Mon, Nov 20, 2017 at 1:25 PM, Ulf Hansson wrote:
> On 18 November 2017 at 15:31, Rafael J. Wysocki wrote:
>> From: Rafael J. Wysocki
>>
>> Define and document a new driver flag, DPM_FLAG_LEAVE_SUSPENDED, to
>> instruct the PM core and middle-layer (bus type, PM do
From: Rafael J. Wysocki
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 early from pci_pm_resume_noirq()
for devices
From: Rafael J. Wysocki
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 "early" phase of system resume (o
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
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 working state (for example,
the
From: Rafael J. Wysocki
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 early from acpi_subsys_resume_noirq()
for
From: Rafael J. Wysocki
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-wide resume callbacks for
such devices with DPM_FL
From: Rafael J. Wysocki
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) transitions.
The underlying observation i
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 method. I am thinking that
On Fri, Nov 17, 2017 at 7:11 AM, Ulf Hansson wrote:
> [...]
>
>>> > +++ linux-pm/include/linux/pm.h
>>> > @@ -559,6 +559,7 @@ struct pm_subsys_data {
>>> > * NEVER_SKIP: Do not skip system suspend/resume callbacks for the
>>> > device.
>>> > * SMART_PREPARE: Check the return value of the driv
On Fri, Nov 17, 2017 at 12:07 AM, Rafael J. Wysocki wrote:
> On Thursday, November 16, 2017 4:10:16 PM CET Ulf Hansson wrote:
>> On 12 November 2017 at 01:37, Rafael J. Wysocki wrote:
>> > From: Rafael J. Wysocki
>> >
>> > Define and document a new drive
On Thursday, November 16, 2017 4:10:16 PM CET Ulf Hansson wrote:
> On 12 November 2017 at 01:37, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > Define and document a new driver flag, DPM_FLAG_LEAVE_SUSPENDED, to
> > instruct the PM core and middle-laye
On Wed, Nov 15, 2017 at 8:43 AM, Ulf Hansson wrote:
> On 12 November 2017 at 01:42, Rafael J. Wysocki wrote:
>> From: Rafael J. Wysocki
>>
>> Add helper routines to find and return a suitable subsystem callback
>> during the "noirq" phases of system suspend
On Tuesday, November 14, 2017 5:07:59 PM CET Ulf Hansson wrote:
> On 11 November 2017 at 00:45, Rafael J. Wysocki wrote:
> > On Fri, Nov 10, 2017 at 10:09 AM, Ulf Hansson
> > wrote:
> >> On 8 November 2017 at 14:25, Rafael J. Wysocki wrote:
> >>> From: Rafae
From: Rafael J. Wysocki
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 "early" phase of system resume (o
From: Rafael J. Wysocki
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 early from acpi_subsys_resume_noirq()
for
From: Rafael J. Wysocki
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) transitions.
The underlying observation i
From: Rafael J. Wysocki
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 working state (for example,
the
From: Rafael J. Wysocki
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 early from pci_pm_resume_noirq()
for devices
From: Rafael J. Wysocki
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-wide resume callbacks for
such devices with DPM_FL
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
On Sat, Nov 11, 2017 at 12:45 AM, Rafael J. Wysocki wrote:
> On Fri, Nov 10, 2017 at 10:09 AM, Ulf Hansson wrote:
>> On 8 November 2017 at 14:25, Rafael J. Wysocki wrote:
[cut]
>> Moreover, you should check the return value from
>> pm_runtime_set_suspended().
>
On Sat, Nov 11, 2017 at 12:45 AM, Rafael J. Wysocki wrote:
> On Fri, Nov 10, 2017 at 10:09 AM, Ulf Hansson wrote:
>> On 8 November 2017 at 14:25, Rafael J. Wysocki wrote:
>>> From: Rafael J. Wysocki
>>>
>>> Define and document a new driver flag, DPM_FLAG_LEA
On Fri, Nov 10, 2017 at 10:09 AM, Ulf Hansson wrote:
> On 8 November 2017 at 14:25, Rafael J. Wysocki wrote:
>> From: Rafael J. Wysocki
>>
>> Define and document a new driver flag, DPM_FLAG_LEAVE_SUSPENDED, to
>> instruct the PM core and middle-layer (bus type, PM do
On Wed, Nov 8, 2017 at 9:38 PM, Bjorn Helgaas wrote:
> On Wed, Nov 08, 2017 at 02:28:18PM +0100, Rafael J. Wysocki wrote:
>> From: Rafael J. Wysocki
>>
>> Add support for DPM_FLAG_LEAVE_SUSPENDED to the PCI bus type by
>> making it (a) set the power.may_skip_resume sta
From: Rafael J. Wysocki
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 early from acpi_subsys_resume_noirq()
for
From: Rafael J. Wysocki
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 early from pci_pm_resume_noirq()
for devices
From: Rafael J. Wysocki
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) transitions.
The underlying observation i
From: Rafael J. Wysocki
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-wide resume callbacks for
such devices with DPM_FL
From: Rafael J. Wysocki
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 working state (for example,
the
Hi All,
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:55 AM CET Rafael J. Wysocki wrote:
> The following part of the original cover letter still applies:
>
> On Monday, O
From: Rafael J. Wysocki
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 "early" phase of system resume (o
On Mon, Nov 6, 2017 at 9:09 AM, Ulf Hansson wrote:
> On 28 October 2017 at 00:22, Rafael J. Wysocki wrote:
>> From: Rafael J. Wysocki
>>
>> Define and document a SMART_SUSPEND flag to instruct bus types and PM
>> domains that the system suspend callbacks provided by
On Wed, Nov 1, 2017 at 10:28 AM, Lee Jones wrote:
> On Tue, 31 Oct 2017, Rafael J. Wysocki wrote:
>
>> On Tue, Oct 31, 2017 at 4:09 PM, Lee Jones wrote:
>> > On Mon, 16 Oct 2017, Rafael J. Wysocki wrote:
>> >
>> >> From: Rafael J. Wysocki
On Tue, Oct 31, 2017 at 4:09 PM, Lee Jones wrote:
> On Mon, 16 Oct 2017, Rafael J. Wysocki wrote:
>
>> From: Rafael J. Wysocki
>>
>> Make the intel-lpss driver set DPM_FLAG_SMART_SUSPEND for its
>> devices which will allow them to stay in runtime suspend during
>
From: Rafael J. Wysocki
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 (the PCI bus type and
the ACPI PM
From: Rafael J. Wysocki
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 devices in runtime suspend d
From: Rafael J. Wysocki
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
Acked-by: Greg Kroah-Hartman
Acked-by: Bjorn Helgaas
Reviewed-by: Ulf Hansson
---
-> v2: No
1 - 100 of 208 matches
Mail list logo
