linux-kernel - Re: [PATCH v2 3/3] Documentation: mfd: Add binding document for S2MPA01

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]

Date:	Wed, 12 Feb 2014 18:21:48 +0000
From:	Mark Brown <broonie@...nel.org>
To:	Mark Rutland <mark.rutland@....com>
Cc:	Sachin Kamat <sachin.kamat@...aro.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"sbkim73@...sung.com" <sbkim73@...sung.com>,
	"lee.jones@...aro.org" <lee.jones@...aro.org>,
	"lgirdwood@...il.com" <lgirdwood@...il.com>,
	"patches@...aro.org" <patches@...aro.org>
Subject: Re: [PATCH v2 3/3] Documentation: mfd: Add binding document for
 S2MPA01

On Wed, Feb 12, 2014 at 06:10:43PM +0000, Mark Rutland wrote:
> On Thu, Jan 09, 2014 at 11:22:34AM +0000, Sachin Kamat wrote:

> > +Required properties:
> > +- compatible: Should be "samsung,s2mpa01-pmic".
> > +- reg: Specifies the I2C slave address of the PMIC block. It should be 0x66.

> Is the slave address not per-instance in I2C? If not why must is be 0x66?

I2C devices tend to have a very limited selection of addresses they can
support, a small number selected by pin strapping is common but a single
fixed address is also common.  Each device on the bus will have a unique
address but there may not be any selectability.

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