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] [day] [month] [year] [list]
Message-ID: <20120806214724.GC26698@opensource.wolfsonmicro.com>
Date:	Mon, 6 Aug 2012 22:47:24 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Stephen Warren <swarren@...dotorg.org>
Cc:	Liam Girdwood <lrg@...com>, linux-kernel@...r.kernel.org,
	Laxman Dewangan <ldewangan@...dia.com>,
	Gyungoh Yoo <jack.yoo@...im-ic.com>,
	Stephen Warren <swarren@...dia.com>
Subject: Re: [PATCH] regulator: add MAX8907 driver

On Mon, Aug 06, 2012 at 03:22:17PM -0600, Stephen Warren wrote:
> On 08/04/2012 04:19 AM, Mark Brown wrote:

> > I'm really not convinced it makes much sense to represent the backlight
> > driver current regulators as regulators, they only get used as part of
> > the backlight and are usually tightly coupled to their boosts.

> So you mean just completely remove any reference to WLED from the
> driver? There is a register to configure the current limit - do you not
> expect anything to ever need to set that in the kernel; do you expect
> the HW default to be correct, or the bootloader to set the desired value?

I'd expect it to be configured as part of configuring the overall
backlight, for an actual current regulator you're not setting a current
limit but rather a current which usually translates directly into a
brightness.  As I say this will usually be done in conjunction with a
boost regulator.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ