From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755764Ab2DTONa (ORCPT ); Fri, 20 Apr 2012 10:13:30 -0400 Received: from mail-lpp01m010-f46.google.com ([209.85.215.46]:36881 "EHLO mail-lpp01m010-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753032Ab2DTON2 convert rfc822-to-8bit (ORCPT ); Fri, 20 Apr 2012 10:13:28 -0400 MIME-Version: 1.0 In-Reply-To: References: <1334829097-32084-1-git-send-email-jaswinder.singh@linaro.org> <20120419124204.GE3046@opensource.wolfsonmicro.com> <20120419162905.GA3084@opensource.wolfsonmicro.com> <20120420114602.GB3259@opensource.wolfsonmicro.com> <20120420130134.GA5957@opensource.wolfsonmicro.com> Date: Fri, 20 Apr 2012 19:43:27 +0530 Message-ID: Subject: Re: [PATCH] regulator: Provide a check for dummy regulator From: Jassi Brar To: Mark Brown Cc: linux-kernel@vger.kernel.org, lrg@ti.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 20 April 2012 19:18, Jassi Brar wrote: > >>  To repeat yet again you're not supposed to actually use dummy regulators, >> you're supposed to fully specify the regulators on your platform. >> > I use dummy regulators for what they are meant for - until every platform > completely define supplies for every consumer. > We are not there yet, yet one 'ideal' consumer suffers because of that. > > If you ask me to go away and disable dummy and update all consumers > and their platforms, then I say why not remove the concept of dummy > altogether which only delays full compliance to the regulator api ? > Btw, by 'all platforms' I meant those based on my SoC. Popular term - machines.