[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1936974.loJEzqH07r@aspire.rjw.lan>
Date: Mon, 04 Dec 2017 16:03:41 +0100
From: "Rafael J. Wysocki" <rjw@...ysocki.net>
To: Meelis Roos <mroos@...ux.ee>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>,
Viresh Kumar <viresh.kumar@...aro.org>,
Linux PM <linux-pm@...r.kernel.org>,
Vincent Guittot <vincent.guittot@...aro.org>,
"4 . 14+" <stable@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] cpufreq: longhaul: Set transition_delay_us to 20 ms
On Wednesday, November 29, 2017 7:59:27 AM CET Meelis Roos wrote:
> > > diff --git a/drivers/cpufreq/longhaul.c b/drivers/cpufreq/longhaul.c
> > > index c46a12df40dd..56eafcb07859 100644
> > > --- a/drivers/cpufreq/longhaul.c
> > > +++ b/drivers/cpufreq/longhaul.c
> > > @@ -894,7 +894,7 @@ static int longhaul_cpu_init(struct cpufreq_policy *policy)
> > > if ((longhaul_version != TYPE_LONGHAUL_V1) && (scale_voltage != 0))
> > > longhaul_setup_voltagescaling();
> > >
> > > - policy->cpuinfo.transition_latency = 200000; /* nsec */
> > > + policy->transition_delay_us = 20000; /* usec */
> > >
> > > return cpufreq_table_validate_and_show(policy, longhaul_table);
> > > }
> > > --
> >
> > Meelis, please check if this fixes the shutdown issue you have
> > reported recently.
>
> Yes, but not today - hopefully tomorrow.
Any news?
I'd like to push the fix for 4.15 shortly if it works for you (I don't
see why it wouldn't work, but still I'd prefer it to be actually tested).
Thanks,
Rafael
Powered by blists - more mailing lists