On Thu, Sep 12, 2013 at 02:07:48PM -0700, Kevin Hilman wrote: > IMO, this decision belongs to the PM domain, not to the core. We have > an established legacy with the current core default (auto) and changing > that means lots of breakage. Yup. > The "forbid by default" can just as easily be handled in the PM domain > for the group of devices that need it, so why not do it there? Or at the device level - I'd guess most I2C devices won't end up in a domain outside of ACPI. Mika's latest version of the patches address this issue, the default is left alone.
Attachment:
signature.asc
Description: Digital signature
