From mboxrd@z Thu Jan 1 00:00:00 1970 From: Viresh Kumar Subject: Re: [PATCH 00/14] cpufreq: cpu0: Extend support beyond CPU0, V2 Date: Wed, 16 Jul 2014 21:31:54 +0530 Message-ID: References: <53B4B0B3.9080000@codeaurora.org> <20140703221609.11380.6884@quantum> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from mail-oa0-f41.google.com ([209.85.219.41]:36298 "EHLO mail-oa0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934600AbaGPQBz (ORCPT ); Wed, 16 Jul 2014 12:01:55 -0400 Received: by mail-oa0-f41.google.com with SMTP id j17so1180746oag.14 for ; Wed, 16 Jul 2014 09:01:54 -0700 (PDT) In-Reply-To: Sender: linux-arm-msm-owner@vger.kernel.org List-Id: linux-arm-msm@vger.kernel.org To: Mike Turquette , "Rafael J. Wysocki" , Thomas Petazzoni Cc: 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 Cc'ing Thomas, On 8 July 2014 10:20, Viresh Kumar wrote: > On 4 July 2014 09:51, Viresh Kumar wrote: >> Yeah, having something like what you suggested from DT is the perfect >> solution to get over this. The only reason why I am not touching that here >> is to not delay other patches just because of that. >> >> There are separate threads going on for that and probably somebody >> else was trying to push for that. >> >> That's it, nothing more. I would definitely like to use those bindings instead >> of the crazy routines we are trying here, once that is finalized :) > > Do we have some kind of agreement for this temporary solution? Anyways > I will kick the other thread again to resolve the bindings soon. Hi Mike/Rafael, Thomas has a dependency on the patch adding "find_siblings()": http://www.spinics.net/lists/arm-kernel/msg348080.html Would it be fine to get this temporary solution (Only within cpufreq-cpu0 file, so that it doesn't become an API) for now and updating it later once bindings are closed? I have tried pinging on the other thread as well, but no one replied. And it looks those bindings are going to take some time to settle. -- viresh