Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757312Ab2BCRcU (ORCPT ); Fri, 3 Feb 2012 12:32:20 -0500 Received: from mho-01-ewr.mailhop.org ([204.13.248.71]:56791 "EHLO mho-01-ewr.mailhop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753596Ab2BCRcT (ORCPT ); Fri, 3 Feb 2012 12:32:19 -0500 X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 98.234.237.12 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX18uAcPI9SoH05q0StlliHIi Date: Fri, 3 Feb 2012 09:32:05 -0800 From: Tony Lindgren To: Dong Aisheng Cc: Stephen Warren , Shawn Guo , Dong Aisheng-B29396 , "Linus Walleij (linus.walleij@linaro.org)" , "Sascha Hauer (s.hauer@pengutronix.de)" , "rob.herring@calxeda.com" , "kernel@pengutronix.de" , "cjb@laptop.org" , "Simon Glass (sjg@chromium.org)" , Thomas Abraham , "Grant Likely (grant.likely@secretlab.ca)" , "devicetree-discuss@lists.ozlabs.org" , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: Pinmux bindings proposal V2 Message-ID: <20120203173205.GB1426@atomide.com> References: <74CDBE0F657A3D45AFBB94109FB122FF1780DAB4CE@HQMAIL01.nvidia.com> <20120201143530.GA2203@S2101-09.ap.freescale.net> <74CDBE0F657A3D45AFBB94109FB122FF178E124AC5@HQMAIL01.nvidia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1872 Lines: 49 * Dong Aisheng [120202 11:36]: > > Actually i think i'd rather do not use config property, then i could > be more compact: > (anyway it's another issue and is flexible to be controlled by #pinmux-cells) > pinctrl_usdhc4: pinconfig-usdhc4 { > /* 0: pin 1: group */ > mux-entity = <0>; > func-name = "usdhc4func"; > grp-name = "usdhc4grp"; The func-name and grp-name should be optional here. This mux entry is already the group, and can be used as the group name. And the function name can be generated dynamically in most cases. I'm currently using np->full_name of the driver claiming these pins as the function name. > mux = > > > > > > > > > > ; > }; For listing basic pins this format works fine for me. It seems to have low overhead for parsing. And the width of the array can be driver specific. Looks like it's the binding for altenative states that's still a bit open.. So how about let's first standardize on the mux format above? Then we can enhance it later for describing alternative states? Regards, Tony -- 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/