Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755133AbaGQA2Z (ORCPT ); Wed, 16 Jul 2014 20:28:25 -0400 Received: from mail-oi0-f53.google.com ([209.85.218.53]:52124 "EHLO mail-oi0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754693AbaGQA2X (ORCPT ); Wed, 16 Jul 2014 20:28:23 -0400 X-Greylist: delayed 57813 seconds by postgrey-1.27 at vger.kernel.org; Wed, 16 Jul 2014 20:28:23 EDT MIME-Version: 1.0 In-Reply-To: <1450785.beFNo3ByBF@vostro.rjw.lan> References: <1450785.beFNo3ByBF@vostro.rjw.lan> Date: Thu, 17 Jul 2014 05:58:22 +0530 Message-ID: Subject: Re: [PATCH 00/14] cpufreq: cpu0: Extend support beyond CPU0, V2 From: Viresh Kumar To: "Rafael J. Wysocki" Cc: Mike Turquette , Thomas Petazzoni , Stephen Boyd , Lists linaro-kernel , "linux-pm@vger.kernel.org" , Arvind Chauhan , "linux-arm-msm@vger.kernel.org" , Sachin Kamat , Thomas P Abraham , Shawn Guo , Linux Kernel Mailing List , Nishanth Menon , Tomasz Figa , "devicetree@vger.kernel.org" , Kukjin Kim , Michal Simek , Rob Herring , Santosh Shilimkar , Simon Horman Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 17 July 2014 02:48, Rafael J. Wysocki wrote: > I don't like that idea, but I wonder what other people think. Hmm, the other thread around looking at the bindings is really slow. One common thing around the platforms which want to use cpufreq-cpu0 is they have different clocks for ALL CPUs. I was wondering if instead of a clock-matching routine, we can provide some temporary relief to them via some other means. I meant we can allow cpufreq-cpu0/generic to either set policy->cpus to ALL CPUs or just 1. So that existing and these new platforms can atleast get going.. But don't know how should we do that. Not a binding ofcourse, a Kconfig option could work but multiplatform stuff would break. What else? Maybe platform data as we are handling cpufreq-cpu0 with a platform device? -- viresh -- 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/