From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755245Ab2CUF0e (ORCPT ); Wed, 21 Mar 2012 01:26:34 -0400 Received: from va3ehsobe005.messaging.microsoft.com ([216.32.180.31]:3324 "EHLO va3outboundpool.messaging.microsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754012Ab2CUF0b (ORCPT ); Wed, 21 Mar 2012 01:26:31 -0400 X-SpamScore: -9 X-BigFish: VS-9(zz1432N98dKzz1202hzz8275bh8275dhz2dh2a8h668h839h944hd25h) X-Forefront-Antispam-Report: CIP:70.37.183.190;KIP:(null);UIP:(null);IPV:NLI;H:mail.freescale.net;RD:none;EFVD:NLI Date: Wed, 21 Mar 2012 13:37:39 +0800 From: Dong Aisheng To: Stephen Warren CC: "linus.walleij@linaro.org" , "grant.likely@secretlab.ca" , "rob.herring@calxeda.com" , "linus.walleij@stericsson.com" , Dong Aisheng-B29396 , "s.hauer@pengutronix.de" , "dongas86@gmail.com" , "shawn.guo@linaro.org" , "thomas.abraham@linaro.org" , "tony@atomide.com" , "sjg@chromium.org" , "linux-kernel@vger.kernel.org" , "devicetree-discuss@lists.ozlabs.org" , "linux-tegra@vger.kernel.org" Subject: Re: [PATCH V2 2/6] dt: pinctrl: Document device tree binding Message-ID: <20120321053738.GD3191@shlinux2.ap.freescale.net> References: <1332265479-1260-1-git-send-email-swarren@wwwdotorg.org> <1332265479-1260-2-git-send-email-swarren@wwwdotorg.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <1332265479-1260-2-git-send-email-swarren@wwwdotorg.org> User-Agent: Mutt/1.5.20 (2009-06-14) X-OriginatorOrg: freescale.com Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 21, 2012 at 01:44:35AM +0800, Stephen Warren wrote: > The core pin controller bindings define: > * The fact that pin controllers expose pin configurations as nodes in > device tree. > * That the bindings for those pin configuration nodes is defined by the > individual pin controller drivers. > * A standardized set of properties for client devices to define numbered > or named pin configuration states, each referring to some number of the > afore-mentioned pin configuration nodes. > * That the bindings for the client devices determines the set of numbered > or named states that must exist. > > Signed-off-by: Stephen Warren > Acked-by: Shawn Guo > Acked-by: Tony Lindgren > Acked-by: Linus Walleij > --- > v2: Fix a couple of grammar-os per Randy Dunlap. Add example of a client > device that references no pin configuration nodes per Dong Aisheng. > --- Acked-by: Dong Aisheng Regards Dong Aisheng