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: <20120424200929.GC30172@pengutronix.de>
Date:	Tue, 24 Apr 2012 22:09:29 +0200
From:	Wolfram Sang <w.sang@...gutronix.de>
To:	Stephen Warren <swarren@...dotorg.org>
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

> --- /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?

Regards,

   Wolfram

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

Download attachment "signature.asc" of type "application/pgp-signature" (199 bytes)