On Sat, Oct 05, 2013 at 11:09:01AM +0300, Mika Westerberg wrote:
> It looks like Windows actually powers the I2C controller off independently
> of the I2C client power state. We should probably do the same in Linux even
> though it is not following what the ACPI spec says (but makes sense with
>
On Tue, Oct 01, 2013 at 04:09:42PM +0300, Mika Westerberg wrote:
> The ACPI specification requires the parent device to be powered on before
> any of its children. It can be only powered off when all the children are
> already off.
>
> Currently whenever there is no I2C traffic going on, the I2C
On Tue, Oct 01, 2013 at 04:09:42PM +0300, Mika Westerberg wrote:
The ACPI specification requires the parent device to be powered on before
any of its children. It can be only powered off when all the children are
already off.
Currently whenever there is no I2C traffic going on, the I2C
On Sat, Oct 05, 2013 at 11:09:01AM +0300, Mika Westerberg wrote:
It looks like Windows actually powers the I2C controller off independently
of the I2C client power state. We should probably do the same in Linux even
though it is not following what the ACPI spec says (but makes sense with
On Tuesday, October 01, 2013 04:09:42 PM Mika Westerberg wrote:
> The ACPI specification requires the parent device to be powered on before
> any of its children. It can be only powered off when all the children are
> already off.
>
> Currently whenever there is no I2C traffic going on, the I2C
The ACPI specification requires the parent device to be powered on before
any of its children. It can be only powered off when all the children are
already off.
Currently whenever there is no I2C traffic going on, the I2C controller
driver can put the device into low power state transparently to
The ACPI specification requires the parent device to be powered on before
any of its children. It can be only powered off when all the children are
already off.
Currently whenever there is no I2C traffic going on, the I2C controller
driver can put the device into low power state transparently to
On Tuesday, October 01, 2013 04:09:42 PM Mika Westerberg wrote:
The ACPI specification requires the parent device to be powered on before
any of its children. It can be only powered off when all the children are
already off.
Currently whenever there is no I2C traffic going on, the I2C
8 matches
Mail list logo