From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753922Ab2AWTb0 (ORCPT ); Mon, 23 Jan 2012 14:31:26 -0500 Received: from opensource.wolfsonmicro.com ([80.75.67.52]:59409 "EHLO opensource.wolfsonmicro.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753698Ab2AWTbZ (ORCPT ); Mon, 23 Jan 2012 14:31:25 -0500 Date: Mon, 23 Jan 2012 19:31:22 +0000 From: Mark Brown To: Linus Walleij Cc: "Kim, Milo" , "shreshthakumar.sahu@stericsson.com" , "linux-kernel@vger.kernel.org" , "rpurdie@rpsys.net" Subject: Re: [PATCH 3/7] leds-lm3530: add 'is_vin_always_on' in the lm3530_platform_data Message-ID: <20120123193122.GB26409@opensource.wolfsonmicro.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Cookie: You dialed 5483. User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jan 23, 2012 at 08:13:18PM +0100, Linus Walleij wrote: > As far as I know we want to get rid of different design patterns > avoiding the regulator interface. The way forward for this is > either: > (A) Provide a fixed voltage regulator in your platform for this > device (AFAIK the voltage does not even have to be correct) > (B) Enable dummy regulators in your platform > (A) is more elegant. Yeah, regulator usage should essentially never be conditional at a driver level unless there's actual optional supplies in the hardware. The situation has never been any different to that.