From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Walleij Subject: Re: [PATCH V2] i2c: Add generic I2C multiplexer using pinctrl API Date: Wed, 25 Apr 2012 13:09:57 +0200 Message-ID: References: <1335289664-21383-1-git-send-email-swarren@wwwdotorg.org> <20120424200929.GC30172@pengutronix.de> <4F9714F4.2060400@wwwdotorg.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: In-Reply-To: <4F9714F4.2060400-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org> Sender: linux-i2c-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Stephen Warren , Wolfram Sang Cc: Grant Likely , Rob Herring , Jean Delvare , Ben Dooks , linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Stephen Warren List-Id: linux-i2c@vger.kernel.org On Tue, Apr 24, 2012 at 11:02 PM, Stephen Warren wrote: > On 04/24/2012 02:09 PM, Wolfram Sang wrote: >> >> From what I know, compatible-properties should not be linux-specific >> since devicetrees are OS independent. pinctrl-i2cmux sounds >> linux-specific to me. >> >> So, is such a binding acceptable meanwhile? > > To my mind, "pinctrl" has two meanings: (1) is the Linux internal API > (2) is the pinctrl bindings in > Documentation/devicetree/bindings/pinctrl, which were admittedly > developed strongly based on Linux's pinctrl API needs, but I believe > should be completely agnostic to the pinctrl API, SW, OS, etc., and > hence can be considered a pure representation of hardware. > > As such, the "pinctrl" in "pinctrl-i2cmux" above refers to (2) above, > and can be considered a pure HW/binding term. I second Stephens statement. Now every OS in the world must start to think about these things as pin controllers. But tt's not like there is competing terminology anyway, so let's define this before we get into committee meetings... Yours, Linus Walleij