On Thu, Jan 10, 2019 at 08:50:14AM +0100, Vincent Guittot wrote:
> On Thu, 10 Jan 2019 at 08:46, Ladislav Michl wrote:
> >
> > On Wed, Jan 09, 2019 at 11:06:34PM +0100, Rafael J. Wysocki wrote:
> > > On Wed, Jan 9, 2019 at 7:05 PM Vincent Guittot
> > > wrote:
> > > >
> > > > On Wed, 9 Jan 2019
On Thu, 10 Jan 2019 at 08:46, Ladislav Michl wrote:
>
> On Wed, Jan 09, 2019 at 11:06:34PM +0100, Rafael J. Wysocki wrote:
> > On Wed, Jan 9, 2019 at 7:05 PM Vincent Guittot
> > wrote:
> > >
> > > On Wed, 9 Jan 2019 at 18:26, Ladislav Michl wrote:
> > > >
> > > > On Wed, Jan 09, 2019 at
On Wed, Jan 09, 2019 at 11:06:34PM +0100, Rafael J. Wysocki wrote:
> On Wed, Jan 9, 2019 at 7:05 PM Vincent Guittot
> wrote:
> >
> > On Wed, 9 Jan 2019 at 18:26, Ladislav Michl wrote:
> > >
> > > On Wed, Jan 09, 2019 at 05:32:31PM +0100, Vincent Guittot wrote:
> > > > On Wed, 9 Jan 2019 at
On Wed, Jan 9, 2019 at 7:05 PM Vincent Guittot
wrote:
>
> On Wed, 9 Jan 2019 at 18:26, Ladislav Michl wrote:
> >
> > On Wed, Jan 09, 2019 at 05:32:31PM +0100, Vincent Guittot wrote:
> > > On Wed, 9 Jan 2019 at 17:07, Ladislav Michl wrote:
> > > >
> > > > On Wed, Jan 09, 2019 at 03:12:25PM
On Wed, 9 Jan 2019 at 18:26, Ladislav Michl wrote:
>
> On Wed, Jan 09, 2019 at 05:32:31PM +0100, Vincent Guittot wrote:
> > On Wed, 9 Jan 2019 at 17:07, Ladislav Michl wrote:
> > >
> > > On Wed, Jan 09, 2019 at 03:12:25PM +0100, Vincent Guittot wrote:
> > > > Please keep all thread list when
On Wed, Jan 09, 2019 at 05:32:31PM +0100, Vincent Guittot wrote:
> On Wed, 9 Jan 2019 at 17:07, Ladislav Michl wrote:
> >
> > On Wed, Jan 09, 2019 at 03:12:25PM +0100, Vincent Guittot wrote:
> > > Please keep all thread list when replying :-)
> >
> > Ahh, sorry for that...
> > [snip]
> > > On
* Vincent Guittot [190109 16:56]:
> On Wed, 9 Jan 2019 at 17:50, Tony Lindgren wrote:
> >
> > * Vincent Guittot [190109 16:48]:
> > > On Wed, 9 Jan 2019 at 17:28, Tony Lindgren wrote:
> > > >
> > > > * Rafael J. Wysocki [190109 09:44]:
> > > > > On Wed, Jan 9, 2019 at 2:51 AM Tony Lindgren
On Wed, 9 Jan 2019 at 17:50, Tony Lindgren wrote:
>
> * Vincent Guittot [190109 16:48]:
> > On Wed, 9 Jan 2019 at 17:28, Tony Lindgren wrote:
> > >
> > > * Rafael J. Wysocki [190109 09:44]:
> > > > On Wed, Jan 9, 2019 at 2:51 AM Tony Lindgren wrote:
> > > > >
> > > > > * Vincent Guittot
* Vincent Guittot [190109 16:48]:
> On Wed, 9 Jan 2019 at 17:28, Tony Lindgren wrote:
> >
> > * Rafael J. Wysocki [190109 09:44]:
> > > On Wed, Jan 9, 2019 at 2:51 AM Tony Lindgren wrote:
> > > >
> > > > * Vincent Guittot [190109 01:42]:
> > > > > Le Tuesday 08 Jan 2019 à 13:37:43 (-0800),
On Wed, 9 Jan 2019 at 17:28, Tony Lindgren wrote:
>
> * Rafael J. Wysocki [190109 09:44]:
> > On Wed, Jan 9, 2019 at 2:51 AM Tony Lindgren wrote:
> > >
> > > * Vincent Guittot [190109 01:42]:
> > > > Le Tuesday 08 Jan 2019 à 13:37:43 (-0800), Tony Lindgren a écrit :
> > > > > Lowering the
On Wed, 9 Jan 2019 at 17:07, Ladislav Michl wrote:
>
> On Wed, Jan 09, 2019 at 03:12:25PM +0100, Vincent Guittot wrote:
> > Please keep all thread list when replying :-)
>
> Ahh, sorry for that...
> [snip]
> > On Wed, 9 Jan 2019 at 14:33, Ladislav Michl wrote:
> > > I agree, but it doea all the
* Rafael J. Wysocki [190109 09:44]:
> On Wed, Jan 9, 2019 at 2:51 AM Tony Lindgren wrote:
> >
> > * Vincent Guittot [190109 01:42]:
> > > Le Tuesday 08 Jan 2019 à 13:37:43 (-0800), Tony Lindgren a écrit :
> > > > Lowering the autosuspend_delay_ms to 2100 ms makes things work again.
> > > >
On Wed, Jan 09, 2019 at 03:12:25PM +0100, Vincent Guittot wrote:
> Please keep all thread list when replying :-)
Ahh, sorry for that...
[snip]
> On Wed, 9 Jan 2019 at 14:33, Ladislav Michl wrote:
> > I agree, but it doea all the magic correctly, so you won't need
> > to touch that code is
Please keep all thread list when replying :-)
On Wed, 9 Jan 2019 at 14:33, Ladislav Michl wrote:
>
> On Wed, Jan 09, 2019 at 02:24:37PM +0100, Vincent Guittot wrote:
> > On Wed, 9 Jan 2019 at 12:58, Ladislav Michl wrote:
> > >
> > > On Wed, Jan 09, 2019 at 12:27:57PM +0100, Vincent Guittot
On Wed, 9 Jan 2019 at 12:58, Ladislav Michl wrote:
>
> On Wed, Jan 09, 2019 at 12:27:57PM +0100, Vincent Guittot wrote:
> > On Wed, 9 Jan 2019 at 12:17, Ladislav Michl wrote:
> > >
> > > On Wed, Jan 09, 2019 at 02:42:18AM +0100, Vincent Guittot wrote:
> > > > Le Tuesday 08 Jan 2019 à 13:37:43
On Wed, 9 Jan 2019 at 12:17, Ladislav Michl wrote:
>
> On Wed, Jan 09, 2019 at 02:42:18AM +0100, Vincent Guittot wrote:
> > Le Tuesday 08 Jan 2019 à 13:37:43 (-0800), Tony Lindgren a écrit :
> > > * Vincent Guittot [190108 16:42]:
> > > > On Tue, 8 Jan 2019 at 16:53, Tony Lindgren wrote:
> > >
On Wed, Jan 09, 2019 at 02:42:18AM +0100, Vincent Guittot wrote:
> Le Tuesday 08 Jan 2019 à 13:37:43 (-0800), Tony Lindgren a écrit :
> > * Vincent Guittot [190108 16:42]:
> > > On Tue, 8 Jan 2019 at 16:53, Tony Lindgren wrote:
> > > > Hmm so could it be that we now rely on timers that that may
On Wed, Jan 9, 2019 at 2:51 AM Tony Lindgren wrote:
>
> * Vincent Guittot [190109 01:42]:
> > Le Tuesday 08 Jan 2019 à 13:37:43 (-0800), Tony Lindgren a écrit :
> > > Lowering the autosuspend_delay_ms to 2100 ms makes things work again.
> > > Anything higher than 2200 ms seems to somehow time
* Vincent Guittot [190109 01:42]:
> Le Tuesday 08 Jan 2019 à 13:37:43 (-0800), Tony Lindgren a écrit :
> > Lowering the autosuspend_delay_ms to 2100 ms makes things work again.
> > Anything higher than 2200 ms seems to somehow time out immediately
> > now :)
>
> This is quite close to the max ns
Le Tuesday 08 Jan 2019 à 13:37:43 (-0800), Tony Lindgren a écrit :
> * Vincent Guittot [190108 16:42]:
> > On Tue, 8 Jan 2019 at 16:53, Tony Lindgren wrote:
> > > Hmm so could it be that we now rely on timers that that may
> > > not be capable of waking up the system from idle states with
> > >
* Vincent Guittot [190108 16:42]:
> On Tue, 8 Jan 2019 at 16:53, Tony Lindgren wrote:
> > Hmm so could it be that we now rely on timers that that may
> > not be capable of waking up the system from idle states with
> > hrtimer?
>
> With nohz and hrtimer enabled, timer relies on hrtimer to
On Tue, 8 Jan 2019 at 16:53, Tony Lindgren wrote:
>
> * Vincent Guittot [190108 08:00]:
> > Hi Tony,
> >
> > On Tue, 8 Jan 2019 at 00:38, Tony Lindgren wrote:
> > >
> > > Hi all,
> > >
> > > Looks like commit 8234f6734c5d ("PM-runtime: Switch autosuspend
> > > over to using hrtimers") caused a
* Vincent Guittot [190108 08:00]:
> Hi Tony,
>
> On Tue, 8 Jan 2019 at 00:38, Tony Lindgren wrote:
> >
> > Hi all,
> >
> > Looks like commit 8234f6734c5d ("PM-runtime: Switch autosuspend
> > over to using hrtimers") caused a regression on at least
> > omap5-uevm where 8250 UART rx wake no
Hi Tony,
On Tue, 8 Jan 2019 at 00:38, Tony Lindgren wrote:
>
> Hi all,
>
> Looks like commit 8234f6734c5d ("PM-runtime: Switch autosuspend
> over to using hrtimers") caused a regression on at least
> omap5-uevm where 8250 UART rx wake no longer works. I have not
> noticed this happening on
Hi all,
Looks like commit 8234f6734c5d ("PM-runtime: Switch autosuspend
over to using hrtimers") caused a regression on at least
omap5-uevm where 8250 UART rx wake no longer works. I have not
noticed this happening on others so far.
The devices I've tested all are using 8250 with dedicated
25 matches
Mail list logo