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:	Mon, 18 Jun 2012 18:28:09 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Guennadi Liakhovetski <g.liakhovetski@....de>
Cc:	linux-kernel@...r.kernel.org, Liam Girdwood <lrg@...com>
Subject: Re: [PATCH 1/2 v2] regulator: support multiple dummy fixed regulators

On Mon, Jun 18, 2012 at 07:13:06PM +0200, Guennadi Liakhovetski wrote:
> On Mon, 18 Jun 2012, Mark Brown wrote:

> > It's for cases where people can't be bothered to specify the supply
> > properly but want to just put something in there to satisfy the sofware
> > without providing any useful information.  There will be one or more
> > physical supplies but the software is being non-committal about them.

> Ok, but for that purpose I thought we already have the dummy regulator... 

The dummy regulator isn't supposed to be used in production whereas this
is - dummy will get substituted in for *any* missing supply as a crutch
to get things working while this is added where needed.  Having dummy on
can break things.

> So, what's the proper way to describe board common voltage rails? 

Fixed voltage regulators should be described with the fixed voltage
regulator driver.

> Obviously you don't want to disable and enable them. Of course, there are 
> real physical regulators, that provide that voltage, but what does it 
> change, whether we specify the real name of that device or just say - yes, 
> we have 3.3V on this board? So, it IS just a fixed regulator with a fixed 
> voltage with no way to control it. The only action you can perform with it 
> is query the voltage.

The name is mainly useful for allowing people to associate the code with
the schematic, by putting the name used in the schematic into the code
we make things much easier when people want to map between the two.

> > Meh, yes.  I did try to make them readable.  But then making up the
> > names in this fashion does rather defeat the point there...

> Ok, what shall we do with this? You want the user to supply a name for 
> these fixed voltage always-on regulators? Or you're against these changes 

Supply a name I think, the use case is totally sensible so it's
definitely totally reasonable to do something.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ