From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753645AbbCLJ27 (ORCPT ); Thu, 12 Mar 2015 05:28:59 -0400 Received: from mail-oi0-f47.google.com ([209.85.218.47]:47002 "EHLO mail-oi0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753267AbbCLJ24 (ORCPT ); Thu, 12 Mar 2015 05:28:56 -0400 MIME-Version: 1.0 In-Reply-To: <20150311124555.GB28806@sirena.org.uk> References: <1425458956-20665-1-git-send-email-pi-cheng.chen@linaro.org> <1425458956-20665-4-git-send-email-pi-cheng.chen@linaro.org> <20150311105307.GW28806@sirena.org.uk> <20150311124555.GB28806@sirena.org.uk> Date: Thu, 12 Mar 2015 14:58:55 +0530 Message-ID: Subject: Re: [PATCH v2 3/4] cpufreq: mediatek: add Mediatek cpufreq driver From: Viresh Kumar To: Mark Brown Cc: Mark Rutland , Catalin Marinas , Chen Fan , Ian Campbell , Howard Chen , "Joe.C" , "devicetree@vger.kernel.org" , Linaro Kernel Mailman List , Pawel Moll , "linux-pm@vger.kernel.org" , Sascha Hauer , Rob Herring , linux-mediatek@lists.infradead.org, Matthias Brugger , Eddie Huang , "linux-arm-kernel@lists.infradead.org" , Thomas Petazzoni , "Rafael J. Wysocki" , Linux Kernel Mailing List , Kumar Gala 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 11 March 2015 at 18:15, Mark Brown wrote: > Ugh, no - that's a hideous bodge which is only going to create trouble > later. Remember, DT is an ABI and should describe the hardware so if > we're doing bodges that are visible there to shoehorn things onto our > implementation that's bad. The concerns that Pi-Cheng had about what > happens if the PMIC gets changed definitely seem relevant here too. Hmm.. > Why not just write a custom cpufreq driver if it's too hard to abstract? Hmm, probably all that can be solved with the new OPP bindings where we can have support for multiple regulator or clock sources to the CPU. @Pi-cheng: How are you going to pass voltages for both the regulators as OPPs today only support a single regulator, in case you have to write your own driver.