From mboxrd@z Thu Jan 1 00:00:00 1970 From: yingjoe.chen@mediatek.com (Yingjoe Chen) Date: Fri, 16 Jan 2015 18:23:25 +0800 Subject: [PATCH v3 2/3] dt-bindings: Add pinctrl bindings for mt65xx/mt81xx. In-Reply-To: References: <1415709535-31515-1-git-send-email-hongzhou.yang@mediatek.com> <1415709535-31515-3-git-send-email-hongzhou.yang@mediatek.com> <20141127101830.GP30369@pengutronix.de> <20141202135527.GM30369@pengutronix.de> <20150112122200.GC18908@pengutronix.de> <20150113161614.GF23940@pengutronix.de> Message-ID: <1421403805.11671.58.camel@mtksdaap41> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Fri, 2015-01-16 at 10:53 +0100, Linus Walleij wrote: > On Tue, Jan 13, 2015 at 5:16 PM, Sascha Hauer wrote: > > On Tue, Jan 13, 2015 at 11:05:22AM +0100, Linus Walleij wrote: > > >> > You often talk about ambiguities. Could you give an example what > >> > ambiguities you mean? > >> > >> What happened was this pins = ; arguments were sometimes > >> strings and sometimes integers, that becomes strange to handle > >> in code, ambiguous. > > > > I see. I like naming it 'pinmux' because that's what it is: pins and > > mux settings. A plain 'pinno' suggests that it contains only pin mubers, > > without mux setting. How about 'pin-no-mux'? We also could add an > > explicit "pins-are-numbered" property instead of distinguishing this > > by property names. > > I kind of like this "pins-are-numbered" thing. > > The other property for the pin, whether pinmux or pin-no-mux or > pin-num-and-mux etc is no such big deal, as long as it's > consistent and documented with the generic bindings. Hi Linus, To make sure I understand it correct, you think something like this is OK? pinctrl at 01c20800 { compatible = "mediatek,mt8135-pinctrl"; [...] pins-are-numbered; i2c0_pins_a: i2c0 at 0 { pins1 { pins = , ; bias-disable; }; }; [....] } Joe.C