From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751474AbbCKLqr (ORCPT ); Wed, 11 Mar 2015 07:46:47 -0400 Received: from mail-oi0-f52.google.com ([209.85.218.52]:35709 "EHLO mail-oi0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751158AbbCKLqm (ORCPT ); Wed, 11 Mar 2015 07:46:42 -0400 MIME-Version: 1.0 In-Reply-To: <1426074142.30734.7.camel@pengutronix.de> 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> <1426074142.30734.7.camel@pengutronix.de> Date: Wed, 11 Mar 2015 17:16:42 +0530 Message-ID: Subject: Re: [PATCH v2 3/4] cpufreq: mediatek: add Mediatek cpufreq driver From: Viresh Kumar To: Lucas Stach Cc: Mark Brown , 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 17:12, Lucas Stach wrote: > Instead of creating virtual regulators I would be strongly in favor of > reviving the voltage-domain work. That would allow us to push all those > voltage dependencies we have seen on various SoCs into the domain > handling code and don't care about it in the drivers. > > In that case cpufreq-dt wouldn't control a regulator directly, but > request a specific voltage from the domain the CPUs are located in and > those in turn would control the regulators supplying them. I agree that it would be the right approach but who is going to do that stuff ? I think until the time we revive the voltage-domain stuff we need to support mediatek's driver. And probably a virtual regulator is the best approach unless someone else comes up with another idea.