Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755027AbaJHILY (ORCPT ); Wed, 8 Oct 2014 04:11:24 -0400 Received: from top.free-electrons.com ([176.31.233.9]:39166 "EHLO mail.free-electrons.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1755007AbaJHILU (ORCPT ); Wed, 8 Oct 2014 04:11:20 -0400 Date: Wed, 8 Oct 2014 10:11:15 +0200 From: Thomas Petazzoni To: Viresh Kumar Cc: Mike Turquette , "Rafael J. Wysocki" , Lists linaro-kernel , "linux-pm@vger.kernel.org" , Shawn Guo , Stephen Boyd , "linux-arm-msm@vger.kernel.org" , Sachin Kamat , "pramod.gurav@smartplayin.com" , Rob Herring , Ezequiel Garcia , Tawfik Bayouk , Nadav Haklai , Lior Amsalem , Morten Rasmussen , Dietmar Eggemann , Vincent Guittot , Nicolas Pitre , Linux Kernel Mailing List , Tuukka Tikkanen Subject: Re: [PATCH 0/2] allow cpufreq drivers to export flags Message-ID: <20141008101115.1835927a@free-electrons.com> In-Reply-To: References: <1412754534-14068-1-git-send-email-mturquette@linaro.org> Organization: Free Electrons X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.23; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Dear Viresh Kumar, On Wed, 8 Oct 2014 13:24:30 +0530, Viresh Kumar wrote: > On 8 October 2014 13:18, Mike Turquette wrote: > > This series is partially in response to a discussion around DT bindings > > for CPUfreq drivers [0], but it is also needed for on-going work to > > integrate CPUfreq with the scheduler. In particular a scheduler-driven > > cpu frequency scaling policy would be well served to know if the > > underlying CPUfreq driver .target callback might sleep or block for a > > long time. > > > > [0] http://lkml.kernel.org/r/ > > Firstly this link is broken and then the last comment I gave in Thomas's > thread was that he doesn't need this routine anymore. And so your scheduler > work is the only user of it.. And so probably we should get this included with > the scheduler patches only, isn't it? Just including them without any user > wouldn't benefit.. > > Or am I missing something ? Well, when one has to merge a large number of changes, we often recommend to merge them piece by piece, which is what Mike is trying to do here. So we cannot at the same time ask developers to merge things in small pieces that are easy to review and to merge everything together because the users of a given API are not there yet. Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/