From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752506AbdLGJd6 (ORCPT ); Thu, 7 Dec 2017 04:33:58 -0500 Received: from mail-pf0-f195.google.com ([209.85.192.195]:36217 "EHLO mail-pf0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750869AbdLGJdz (ORCPT ); Thu, 7 Dec 2017 04:33:55 -0500 X-Google-Smtp-Source: AGs4zMYnChVrA2XxBWbB71Wv9Da9HgKBlXqjUgSi4lyfBKNY9HN9srxtiK8aipldo6t9gvFxMDxumg== Date: Thu, 7 Dec 2017 15:03:50 +0530 From: Viresh Kumar To: Meelis Roos Cc: "Rafael J. Wysocki" , Rafael Wysocki , Linux PM , Vincent Guittot , "4 . 14+" , Linux Kernel Mailing List Subject: Re: [PATCH] cpufreq: longhaul: Set transition_delay_us to 20 ms Message-ID: <20171207093349.ct2hkhqj2d2tzvui@vireshk-mac-ubuntu> References: <20171207044019.kxwusyl5qoxq7zta@vireshk-mac-ubuntu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 07-12-17, 09:26, Meelis Roos wrote: > > On 06-12-17, 20:21, Meelis Roos wrote: > > > 30000 was not reliable. > > > > > > I created root cron job > > > @reboot sleep 120; /sbin/reboot > > > > > > and by the evening it was dead again. > > > > > > Will try 50000 tomorrow. > > > > Lets make it similar to what it was before my original patch modified > > it, to avoid all corner cases. > > > > Please test against 200 ms, 200000 value here. > > Sorry, I confused 200000 vs 20000, will test 200000. > > But 200000 was the value before. It was value of a different variable (transition_latency) at that time. Just set transition_delay_us in my recent patch as 200,000 and apply that over mainline. I will resend the patch in the mean time as well. > Shall I test 200000 with or without > the other limiting patch? -- viresh