linux-kernel - Re: [PATCH V2] i2c: Add generic I2C multiplexer using pinctrl API

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4F9714F4.2060400@wwwdotorg.org>
Date:	Tue, 24 Apr 2012 15:02:44 -0600
From:	Stephen Warren <swarren@...dotorg.org>
To:	Wolfram Sang <w.sang@...gutronix.de>
CC:	Grant Likely <grant.likely@...retlab.ca>,
	Rob Herring <rob.herring@...xeda.com>,
	Jean Delvare <khali@...ux-fr.org>,
	Ben Dooks <ben-linux@...ff.org>, linux-i2c@...r.kernel.org,
	devicetree-discuss@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
	Stephen Warren <swarren@...dia.com>
Subject: Re: [PATCH V2] i2c: Add generic I2C multiplexer using pinctrl API

On 04/24/2012 02:09 PM, Wolfram Sang wrote:
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/i2c/pinctrl-i2cmux.txt
>> @@ -0,0 +1,79 @@
>> +Pinctrl-based I2C Bus Mux
>> +
>> +This binding describes an I2C bus multiplexer that uses pin multiplexing to
>> +route the I2C signals, and represents the pin multiplexing configuration
>> +using the pinctrl device tree bindings.
>> +
>> +Required properties:
>> +- compatible: pinctrl-i2cmux
> 
> 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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/