From mboxrd@z Thu Jan 1 00:00:00 1970 From: Viresh Kumar Subject: Re: [PATCH 07/14] cpufreq: cpu0: OPPs can be populated at runtime Date: Thu, 10 Jul 2014 16:49:52 +0530 Message-ID: References: <1ba7771e910084cd0820c19ca5994fe1b3d6451d.1404231535.git.viresh.kumar@linaro.org> <53BD5564.2060704@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: <53BD5564.2060704@ti.com> Sender: linux-pm-owner@vger.kernel.org To: Santosh Shilimkar Cc: "Rafael J. Wysocki" , Shawn Guo , Nishanth Menon , Lists linaro-kernel , "linux-pm@vger.kernel.org" , "linux-arm-msm@vger.kernel.org" , Tomasz Figa , Stephen Boyd , Linux Kernel Mailing List , Thomas P Abraham , Arvind Chauhan , Sachin Kamat List-Id: linux-arm-msm@vger.kernel.org On 9 July 2014 20:14, Santosh Shilimkar wrote: > Assuming you are updating bidnings as suggested by Stephen, > patch looks good to me. > Acked-by: Santosh Shilimkar Why do you still have a separate cpufreq driver for omap? Would this patch help getting that out? I see this for omap: static inline void omap_init_cpufreq(void) { struct platform_device_info devinfo = { }; if (!of_have_populated_dt()) devinfo.name = "omap-cpufreq"; else devinfo.name = "cpufreq-generic"; platform_device_register_full(&devinfo); } and it makes me believe that you were just waiting for this patch?