Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755383Ab3GYIxi (ORCPT ); Thu, 25 Jul 2013 04:53:38 -0400 Received: from co1ehsobe002.messaging.microsoft.com ([216.32.180.185]:20485 "EHLO co1outboundpool.messaging.microsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754779Ab3GYIxe (ORCPT ); Thu, 25 Jul 2013 04:53:34 -0400 X-Forefront-Antispam-Report: CIP:70.37.183.190;KIP:(null);UIP:(null);IPV:NLI;H:mail.freescale.net;RD:none;EFVD:NLI X-SpamScore: 1 X-BigFish: VS1(zz98dI1432Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6h1082kzz1de097hz2dh2a8h668h839h944hd25hd2bhf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h1ad9h1b0ah1d0ch1d2eh1d3fh1dfeh1dffh1155h) Date: Thu, 25 Jul 2013 16:58:10 +0800 From: Robin Gong To: Shawn Guo CC: , , , , , , , , Subject: Re: [PATCH v5] regulator: pfuze100: add pfuze100 regulator driver Message-ID: <20130725085809.GA10765@Robin-OptiPlex-780> References: <1374723198-9716-1-git-send-email-b38343@freescale.com> <20130725084042.GA19368@S2101-09.ap.freescale.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20130725084042.GA19368@S2101-09.ap.freescale.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-OriginatorOrg: freescale.com X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1120 Lines: 26 On Thu, Jul 25, 2013 at 04:40:44PM +0800, Shawn Guo wrote: > On Thu, Jul 25, 2013 at 11:33:18AM +0800, Robin Gong wrote: > > @@ -0,0 +1,113 @@ > > +PFUZE100 family of regulators > > + > > +Required properties: > > +- compatible: "fsl,pfuze100" > > +- reg: I2C slave address > > +- regulators: This is the list of child nodes that specify the regulator > > + initialization data for defined regulators. Please refer to below doc > > + Documentation/devicetree/bindings/regulator/regulator.txt. > > I had the comment on v4 patch. The "regulators" should not be > documented as a property but a sub-node, because it's not a property > but sub-node. > Shawn, I notice there are the same descriptions in the many docs of regulator drivers, can we consider the 'regulators' child node as one of special property ? Sorry for missing the information in the last mail.. > Shawn -- 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/