Re: [PATCH] PM / QoS: Fix default runtime_pm device resume latency

2017-11-01 Thread Rafael J. Wysocki
[cut] >> It seems the default values for pm_qos have changed with the patch, and that >> breaks genpd at least. I only fixed PM runtime initially, but you could try >> this diff to fix the genpd part also: >> >> diff --git a/include/linux/pm_qos.h b/include/linux/pm_qos.h >> index d68b056..7c8f643

Re: [PATCH] PM / QoS: Fix default runtime_pm device resume latency

2017-11-01 Thread Rafael J. Wysocki
On Wed, Nov 1, 2017 at 11:28 AM, Tero Kristo wrote: > On 01/11/17 00:32, Rafael J. Wysocki wrote: >> >> On Tue, Oct 31, 2017 at 7:07 PM, Geert Uytterhoeven >> wrote: >>> >>> Hi Rafael, >>> >>> On Tue, Oct 31, 2017 at 6:22 PM, Rafael J. Wysocki >>> wrote: On Tue, Oct 31, 2017 at 2:55 PM

Re: [PATCH] PM / QoS: Fix default runtime_pm device resume latency

2017-11-01 Thread Tero Kristo
On 01/11/17 00:32, Rafael J. Wysocki wrote: On Tue, Oct 31, 2017 at 7:07 PM, Geert Uytterhoeven wrote: Hi Rafael, On Tue, Oct 31, 2017 at 6:22 PM, Rafael J. Wysocki wrote: On Tue, Oct 31, 2017 at 2:55 PM, Geert Uytterhoeven wrote: Hi Rafael, Tero, CC pinchartl, dri-devel On Tue, Oct 31,

Re: [PATCH] PM / QoS: Fix default runtime_pm device resume latency

2017-10-31 Thread Rafael J. Wysocki
On Tue, Oct 31, 2017 at 7:07 PM, Geert Uytterhoeven wrote: > Hi Rafael, > > On Tue, Oct 31, 2017 at 6:22 PM, Rafael J. Wysocki wrote: >> On Tue, Oct 31, 2017 at 2:55 PM, Geert Uytterhoeven >> wrote: >>> Hi Rafael, Tero, >>> >>> CC pinchartl, dri-devel >>> >>> On Tue, Oct 31, 2017 at 2:10 PM, Gee

Re: [PATCH] PM / QoS: Fix default runtime_pm device resume latency

2017-10-31 Thread Geert Uytterhoeven
Hi Rafael, On Tue, Oct 31, 2017 at 6:22 PM, Rafael J. Wysocki wrote: > On Tue, Oct 31, 2017 at 2:55 PM, Geert Uytterhoeven > wrote: >> Hi Rafael, Tero, >> >> CC pinchartl, dri-devel >> >> On Tue, Oct 31, 2017 at 2:10 PM, Geert Uytterhoeven >> wrote: >>> CC linux-renesas-soc >>> >>> On Tue, Oct

Re: [PATCH] PM / QoS: Fix default runtime_pm device resume latency

2017-10-31 Thread Rafael J. Wysocki
On Tue, Oct 31, 2017 at 2:55 PM, Geert Uytterhoeven wrote: > Hi Rafael, Tero, > > CC pinchartl, dri-devel > > On Tue, Oct 31, 2017 at 2:10 PM, Geert Uytterhoeven > wrote: >> CC linux-renesas-soc >> >> On Tue, Oct 31, 2017 at 2:09 PM, Geert Uytterhoeven >> wrote: >>> On Tue, Oct 31, 2017 at 12:27

Re: [PATCH] PM / QoS: Fix default runtime_pm device resume latency

2017-10-31 Thread Laurent Pinchart
Hi Geert, On Tuesday, 31 October 2017 15:55:02 EET Geert Uytterhoeven wrote: > On Tue, Oct 31, 2017 at 2:10 PM, Geert Uytterhoeven wrote: > > On Tue, Oct 31, 2017 at 2:09 PM, Geert Uytterhoeven wrote: > >> On Tue, Oct 31, 2017 at 12:27 AM, Rafael J. Wysocki wrote: > >>> On Monday, October 30, 2017

Re: [PATCH] PM / QoS: Fix default runtime_pm device resume latency

2017-10-31 Thread Daniel Vetter
On Tue, Oct 31, 2017 at 05:37:50PM +0200, Jani Nikula wrote: > On Tue, 31 Oct 2017, Geert Uytterhoeven wrote: > > Hi Rafael, Tero, > > > > CC pinchartl, dri-devel > > Cc: Marta, Martin > > Our CI is hitting this too. Should be ok again, we've locally reverted this patch. But a big chunk of the

Re: [PATCH] PM / QoS: Fix default runtime_pm device resume latency

2017-10-31 Thread Rafael J. Wysocki
On Tue, Oct 31, 2017 at 3:04 PM, Ulf Hansson wrote: > On 31 October 2017 at 14:55, Geert Uytterhoeven wrote: >> Hi Rafael, Tero, >> >> CC pinchartl, dri-devel >> >> On Tue, Oct 31, 2017 at 2:10 PM, Geert Uytterhoeven >> wrote: >>> CC linux-renesas-soc >>> >>> On Tue, Oct 31, 2017 at 2:09 PM, Gee

Re: [PATCH] PM / QoS: Fix default runtime_pm device resume latency

2017-10-31 Thread Jani Nikula
On Tue, 31 Oct 2017, Geert Uytterhoeven wrote: > Hi Rafael, Tero, > > CC pinchartl, dri-devel Cc: Marta, Martin Our CI is hitting this too. BR, Jani. > > On Tue, Oct 31, 2017 at 2:10 PM, Geert Uytterhoeven > wrote: >> CC linux-renesas-soc >> >> On Tue, Oct 31, 2017 at 2:09 PM, Geert Uytterhoe

Re: [PATCH] PM / QoS: Fix default runtime_pm device resume latency

2017-10-31 Thread Ulf Hansson
On 31 October 2017 at 14:55, Geert Uytterhoeven wrote: > Hi Rafael, Tero, > > CC pinchartl, dri-devel > > On Tue, Oct 31, 2017 at 2:10 PM, Geert Uytterhoeven > wrote: >> CC linux-renesas-soc >> >> On Tue, Oct 31, 2017 at 2:09 PM, Geert Uytterhoeven >> wrote: >>> On Tue, Oct 31, 2017 at 12:27 AM,

Re: [PATCH] PM / QoS: Fix default runtime_pm device resume latency

2017-10-31 Thread Geert Uytterhoeven
Hi Rafael, Tero, CC pinchartl, dri-devel On Tue, Oct 31, 2017 at 2:10 PM, Geert Uytterhoeven wrote: > CC linux-renesas-soc > > On Tue, Oct 31, 2017 at 2:09 PM, Geert Uytterhoeven > wrote: >> On Tue, Oct 31, 2017 at 12:27 AM, Rafael J. Wysocki >> wrote: >>> On Monday, October 30, 2017 11:19:08

Re: [PATCH] PM / QoS: Fix default runtime_pm device resume latency

2017-10-31 Thread Geert Uytterhoeven
CC linux-renesas-soc On Tue, Oct 31, 2017 at 2:09 PM, Geert Uytterhoeven wrote: > Hi Rafael, Tero, > > On Tue, Oct 31, 2017 at 12:27 AM, Rafael J. Wysocki > wrote: >> On Monday, October 30, 2017 11:19:08 AM CET Rafael J. Wysocki wrote: >>> On Mon, Oct 30, 2017 at 8:10 AM, Tero Kristo wrote: >>

Re: [PATCH] PM / QoS: Fix default runtime_pm device resume latency

2017-10-31 Thread Geert Uytterhoeven
Hi Rafael, Tero, On Tue, Oct 31, 2017 at 12:27 AM, Rafael J. Wysocki wrote: > On Monday, October 30, 2017 11:19:08 AM CET Rafael J. Wysocki wrote: >> On Mon, Oct 30, 2017 at 8:10 AM, Tero Kristo wrote: >> > The recent change to the PM QoS framework to introduce a proper >> > no constraint value

Re: [PATCH] PM / QoS: Fix default runtime_pm device resume latency

2017-10-31 Thread Tero Kristo
On 31/10/17 10:40, Rafael J. Wysocki wrote: On Tue, Oct 31, 2017 at 8:13 AM, Tero Kristo wrote: On 31/10/17 01:27, Rafael J. Wysocki wrote: On Monday, October 30, 2017 11:19:08 AM CET Rafael J. Wysocki wrote: On Mon, Oct 30, 2017 at 8:10 AM, Tero Kristo wrote: The recent change to the PM

Re: [PATCH] PM / QoS: Fix default runtime_pm device resume latency

2017-10-31 Thread Rafael J. Wysocki
On Tue, Oct 31, 2017 at 8:13 AM, Tero Kristo wrote: > On 31/10/17 01:27, Rafael J. Wysocki wrote: >> >> On Monday, October 30, 2017 11:19:08 AM CET Rafael J. Wysocki wrote: >>> >>> On Mon, Oct 30, 2017 at 8:10 AM, Tero Kristo wrote: The recent change to the PM QoS framework to introduce

Re: [PATCH] PM / QoS: Fix default runtime_pm device resume latency

2017-10-31 Thread Tero Kristo
On 31/10/17 01:27, Rafael J. Wysocki wrote: On Monday, October 30, 2017 11:19:08 AM CET Rafael J. Wysocki wrote: On Mon, Oct 30, 2017 at 8:10 AM, Tero Kristo wrote: The recent change to the PM QoS framework to introduce a proper no constraint value overlooked to handle the devices which don't

Re: [PATCH] PM / QoS: Fix default runtime_pm device resume latency

2017-10-30 Thread Rafael J. Wysocki
On Monday, October 30, 2017 11:19:08 AM CET Rafael J. Wysocki wrote: > On Mon, Oct 30, 2017 at 8:10 AM, Tero Kristo wrote: > > The recent change to the PM QoS framework to introduce a proper > > no constraint value overlooked to handle the devices which don't > > implement PM QoS OPS. Runtime PM i

Re: [PATCH] PM / QoS: Fix default runtime_pm device resume latency

2017-10-30 Thread Rafael J. Wysocki
On Mon, Oct 30, 2017 at 8:10 AM, Tero Kristo wrote: > The recent change to the PM QoS framework to introduce a proper > no constraint value overlooked to handle the devices which don't > implement PM QoS OPS. Runtime PM is one of the more severely > impacted subsystems, failing every attempt to ru

[PATCH] PM / QoS: Fix default runtime_pm device resume latency

2017-10-30 Thread Tero Kristo
The recent change to the PM QoS framework to introduce a proper no constraint value overlooked to handle the devices which don't implement PM QoS OPS. Runtime PM is one of the more severely impacted subsystems, failing every attempt to runtime suspend a device. This leads into some nasty second lev