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: <1376045411.585130456@f141.i.mail.ru>
Date:	Fri, 09 Aug 2013 14:50:11 +0400
From:	Alexander Shiyan <shc_work@...l.ru>
To:	Mark Brown <broonie@...nel.org>
Cc:	Wei Ni <wni@...dia.com>, swarren@...dotorg.org,
	linux-kernel@...r.kernel.org, lm-sensors@...sensors.org,
	linux-tegra@...r.kernel.org, MLongnecker@...dia.com,
	linux-arm-kernel@...ts.infradead.org, khali@...ux-fr.org,
	Guenter Roeck <linux@...ck-us.net>
Subject: Re: Proposal: I2C device power (Was: hwmon: (lm90) Add power control)

> On Fri, Aug 09, 2013 at 09:57:00AM +0400, Alexander Shiyan wrote:
> 
> > Instead of adding the support of regulators in each device, let's think about
> > whether it is possible to create a global regulator for any device on the I2C bus.
> 
> > I see it like this:
> > We add an extra field in the i2c_board_info structure "power_name" and handle
> > it in the i2c_device_{probe/remove} functions.
> 
> This would need to be an array of supplies, relatively few devices need
> only a single power supply.  This is also not something that should be
> handled in I2C, power is not something that's uniquely needed by devices
> on an I2C bus.

Additional regulators can be handled in the driver, or "parent"-scheme can
be used. Is not it?

---

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ