linux-kernel - Re: [PATCH V3 2/3] regulator: dt: regulator match by regulator-compatible

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: <20120620231546.GB4037@opensource.wolfsonmicro.com>
Date:	Thu, 21 Jun 2012 00:15:47 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Laxman Dewangan <ldewangan@...dia.com>, lrg@...com,
	rob.herring@...xeda.com, grant.likely@...retlab.ca,
	linus.walleij@...aro.org, lee.jones@...aro.org,
	swarren@...dotorg.org, devicetree-discuss@...ts.ozlabs.org,
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V3 2/3] regulator: dt: regulator match by
 regulator-compatible

On Wed, Jun 20, 2012 at 08:40:52PM +0000, Arnd Bergmann wrote:

> But that sounds more like what the "reg" property does than what
> the "compatible" property does for other devices. In other words, you
> want to know which instance you are describing, not what kind of
> object it is.

No, it's describing the kind of object.  This stuff is for devices which
throw a bunch of irregular regulators down on a chip with no particular
similarity with each other.

> For a "compatible" property, I would expect two objects that have
> the same register-level interface but are responsible for different
> physical objects to have the same "compatible" values, but here
> you specifically need distinct "regulator-compatible" values.

There's nothing stopping a driver drilling down deeper with other data
once it's worked out what it's talking about, if it wants to read an
additional id value or base register that's absolutely fine and probably
even a good idea.  The problem is that for a lot of hardware there's
just a bunch of random irregular devices.

> It makes much more sense now, so please let's make sure that explanation
> ends up in the changelog.

To be honest I just don't care, the old code hasn't been around for long
enough or widely adopted enough for anyone to care and it's just more
brain cycles gone.

> * What is the difference between "regulator-name" and
> "regulator-compatible"? Those are the same most of the time
> in the patches, so can't we just make sure they are always the
> same, and drop the confusingly named "regulator-compatible" one?

As the binding documentation says the former is a display name for use
so people can tell what the software is talking about, for example the
name the supply has in the schematic.  It's completely up to the user
and the regulator driver can't use it for anything except printing so it
needs something else to help it figure out what it's working with.

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