Hi Mark,
On Fri, 5 Feb 2010 12:30:11 +, Mark Brown wrote:
Allow I2C drivers to make use of the runtime PM framework by adding
bus implementations of the runtime PM operations. These simply
immediately suspend when the device is idle. The runtime PM framework
provides drivers with off the
On Monday 15 February 2010, Mark Brown wrote:
On Mon, Feb 15, 2010 at 07:14:09PM +0100, Jean Delvare wrote:
Applied, thanks. I am a little surprised to see that these functions
have nothing i2c-specific, so I am wondering why we have to duplicate
them in every bus type... Shouldn't the
On Mon, Feb 15, 2010 at 08:08:24PM +0100, Rafael J. Wysocki wrote:
On Monday 15 February 2010, Mark Brown wrote:
On Mon, Feb 15, 2010 at 07:14:09PM +0100, Jean Delvare wrote:
Applied, thanks. I am a little surprised to see that these functions
have nothing i2c-specific, so I am wondering
On Friday 05 February 2010, you wrote:
On Thu, Feb 04, 2010 at 10:57:27PM +0100, Rafael J. Wysocki wrote:
On Wednesday 03 February 2010, Mark Brown wrote:
Allow I2C drivers to make use of the runtime PM framework by adding
bus implementations of the runtime PM operations. These simply
On Wednesday 03 February 2010, Mark Brown wrote:
Allow I2C drivers to make use of the runtime PM framework by adding
bus implementations of the runtime PM operations. These simply
immediately suspend when the device is idle.
Perhaps it would be a good idea to give the driver a chance to veto
Allow I2C drivers to make use of the runtime PM framework by adding
bus implementations of the runtime PM operations. These simply
immediately suspend when the device is idle. The runtime PM framework
provides drivers with off the shelf refcounts for enables and sysfs
control for managing runtime
