Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S966711Ab3HHVaI (ORCPT ); Thu, 8 Aug 2013 17:30:08 -0400 Received: from mail.active-venture.com ([67.228.131.205]:57553 "EHLO mail.active-venture.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S966606Ab3HHVaG (ORCPT ); Thu, 8 Aug 2013 17:30:06 -0400 X-Originating-IP: 108.223.40.66 Message-ID: <52040DE2.50201@roeck-us.net> Date: Thu, 08 Aug 2013 14:30:10 -0700 From: Guenter Roeck User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8 MIME-Version: 1.0 To: Mark Brown CC: Wei Ni , swarren@wwwdotorg.org, linux-kernel@vger.kernel.org, lm-sensors@lm-sensors.org, linux-tegra@vger.kernel.org, MLongnecker@nvidia.com, khali@linux-fr.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v2 1/3] hwmon: (lm90) Add power control References: <1375944991-29182-1-git-send-email-wni@nvidia.com> <1375944991-29182-2-git-send-email-wni@nvidia.com> <20130808110136.GA6427@sirena.org.uk> <52038035.7030803@roeck-us.net> <20130808130840.GC6427@sirena.org.uk> <5203B78C.7010101@roeck-us.net> <20130808171554.GI6427@sirena.org.uk> <20130808200026.GA18226@roeck-us.net> <20130808211825.GN6427@sirena.org.uk> In-Reply-To: <20130808211825.GN6427@sirena.org.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1957 Lines: 44 On 08/08/2013 02:18 PM, Mark Brown wrote: > On Thu, Aug 08, 2013 at 01:00:26PM -0700, Guenter Roeck wrote: >> On Thu, Aug 08, 2013 at 06:15:54PM +0100, Mark Brown wrote: > >>> Sure, that's the transition issues I mentioned - the regulator API does >>> have stubbing facilities which should cover things and it's very easy to >>> define stub regulators if you need to. Like I say I expect this to be a >>> lot easier after the next merge window as another way of doing stubs is >>> being added which should make this even easier by avoiding disrupting >>> drivers that do genuinely want to check for absent supplies and handle >>> that better. > >> We will need to make sure that all dts files using any of the compatible chips >> are updated accordingly. There are several entries in various dts files for >> adm1032, adt7461, lm90, and nct1008. > > Yes, and probably also board files as well. Or either just accept > bisection trouble for now or wait till the better stubbing is in there - Ah, that is exactly the trouble I wanted to avoid. > that will mean that for DT systems the core will just assume the supply > is really there and not fail requests if it's not in the DT. > >>> The names requested by a driver are defined with regard to the device >>> and should be the names used by the chip itself as defined in the > >> 9 votes for vdd, 11 votes for vcc, one undecided (no datasheet available). >> Guess one is as good as the other ;-). > > What I've suggested before is to use the name from the part for which > the driver is named. Assuming the vendor doesn't randomly change their > datasheet (but that causes problems for hardware engineers so tends to > be avoided). > Makes sense. Guenter -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/