Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753415AbaGJMjN (ORCPT ); Thu, 10 Jul 2014 08:39:13 -0400 Received: from mail-wi0-f180.google.com ([209.85.212.180]:39936 "EHLO mail-wi0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753249AbaGJMjK (ORCPT ); Thu, 10 Jul 2014 08:39:10 -0400 MIME-Version: 1.0 In-Reply-To: References: <1ba7771e910084cd0820c19ca5994fe1b3d6451d.1404231535.git.viresh.kumar@linaro.org> <53BD5564.2060704@ti.com> Date: Thu, 10 Jul 2014 07:39:08 -0500 X-Google-Sender-Auth: q-rWjWl6Q12RxPNQZ-OpwK5lCno Message-ID: Subject: Re: [PATCH 07/14] cpufreq: cpu0: OPPs can be populated at runtime From: Nishanth Menon To: Viresh Kumar , Tony Lindgren Cc: Santosh Shilimkar , "Rafael J. Wysocki" , Shawn Guo , 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 , Dave Gerlach , linux-omap 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 Thu, Jul 10, 2014 at 6:19 AM, Viresh Kumar wrote: > 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? Sorry, am away on vacation and slow on emails. The plan was to kill omap cpufreq once all platforms convert to device tree only boot. Only platform left is OMAP3 based platforms - though the date for removing non-dt support has changed a couple of kernel revisions - but we should be able to remove that entire file with this change. We will need this support to go with the solution recommended for opp modifier series[1] - where platform code will populate or add OPPs based on "speed grade" sample detection. [1]http://comments.gmane.org/gmane.linux.ports.arm.kernel/309466 --- Regards, Nishanth Menon -- 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/