From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752071AbdF3D6u (ORCPT ); Thu, 29 Jun 2017 23:58:50 -0400 Received: from mail-pf0-f171.google.com ([209.85.192.171]:34954 "EHLO mail-pf0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751776AbdF3D6s (ORCPT ); Thu, 29 Jun 2017 23:58:48 -0400 Date: Fri, 30 Jun 2017 09:28:44 +0530 From: Viresh Kumar To: "Rafael J. Wysocki" Cc: Rafael Wysocki , Lists linaro-kernel , Linux PM , Linux Kernel Mailing List , Vincent Guittot Subject: Re: [PATCH] cpufreq: Find transition latency dynamically Message-ID: <20170630035844.GW29665@vireshk-i7> References: <8041a965fcca71231576ae77a141b1e4333a81cc.1496402967.git.viresh.kumar@linaro.org> <20170629042836.GI29665@vireshk-i7> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 29-06-17, 22:34, Rafael J. Wysocki wrote: > Shouldn't drivers do that really? Well they can, but the we will have some sort of code duplication then. Or else we can provide a helper for them to find this value dynamically and that would be fine too. And maybe we can add a callback for the cpufreq-driver, which can be filled by the generic helper and core can call it once at policy initialization time. -- viresh