From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753656AbbCKMqs (ORCPT ); Wed, 11 Mar 2015 08:46:48 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:35992 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753619AbbCKMqo (ORCPT ); Wed, 11 Mar 2015 08:46:44 -0400 Date: Wed, 11 Mar 2015 12:46:20 +0000 From: Mark Brown To: Viresh Kumar Cc: Lucas Stach , 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 Message-ID: <20150311124620.GC28806@sirena.org.uk> References: <1425458956-20665-4-git-send-email-pi-cheng.chen@linaro.org> <20150311105307.GW28806@sirena.org.uk> <1426074142.30734.7.camel@pengutronix.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="3l764Q7zY5HuAgsB" Content-Disposition: inline In-Reply-To: X-Cookie: Editing is a rewording activity. User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: 94.175.94.161 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [PATCH v2 3/4] cpufreq: mediatek: add Mediatek cpufreq driver X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on mezzanine.sirena.org.uk) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --3l764Q7zY5HuAgsB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Mar 11, 2015 at 05:16:42PM +0530, Viresh Kumar wrote: > 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. Why not just write a custom cpufreq driver if it's too hard to abstract? --3l764Q7zY5HuAgsB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJVADkbAAoJECTWi3JdVIfQRnMH/iGMkf3/S0DoSz9venn5GInN QLnusP6YSaztjFkp9a28fKtF3OMNmBFI2h92BweNyQy1SMpaKFVerQTuHajBYK9J g4Xhoe5KjvZoZZD5OmMYpjrakmp4QEkSBvBMRFD/65HL+IHEsSc31vXstg3HZbJ+ akEkvPzni/4C9xY+7Z5NWhleahJ0Wm2VXCOFqRpo/fpjxAkwpQ1PYsnZDfZP5vLj FjNLIc6k6iVxTFWb6eEtn0SJfx+fBwQc4mj34tNzER5yJem7O/NCXMAPmI/dhapn U7k9FqZpCu52MxgDT+8K/F+zdCmq6oAWankEymK8ycQnGA6RwKKBB06UqF/l60E= =H1aC -----END PGP SIGNATURE----- --3l764Q7zY5HuAgsB--