On Wed, Jun 21, 2017 at 3:27 PM, Hans de Goede <hdegoede@xxxxxxxxxx> wrote: > Hi, > > On 14-05-17 23:35, Hans de Goede wrote: >> >> Some Bay Trail devices use a GPI1 regulator field (address 0x4c) in >> their 0x8d power OpRegion, add support for this. >> >> This fixes AE_BAD_PARAMETER errors getting thrown on these devices and >> fixes these errors causing these devices to not suspend. >> >> Signed-off-by: Hans de Goede <hdegoede@xxxxxxxxxx> >> Reviewed-by: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx> >> --- >> Changes in v2: >> -Simplify reg == 0x92 handling (suggested by Andy Shevchenko) >> -Add special handling for reg == 0x92 to intel_xpower_pmic_get_power() too >> Changes in v3: >> -Use defines for GPI1 reg and bits, rather then hardcoded hex values > > > What is the status of this patch ? AFAICT this patch has not been > merged yet, even though it has a Reviewe-by. > > Note this patch is necessary to fix suspend/resume on some devices, > as such it would be nic if we can get this merged soon. It will go into 4.13, sorry for the delay. Thanks, Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
