Re: [RFC v3 3/7] platform/x86: intel_pmc_ipc: Use regmap calls for GCR updates

2017-10-04 Thread Andy Shevchenko
On Wed, Oct 4, 2017 at 4:16 AM, sathyanarayanan kuppuswamy wrote: > On 10/01/2017 07:48 AM, Andy Shevchenko wrote: >> On Tue, Sep 5, 2017 at 8:37 AM, >> wrote: >> Since it sounds as candidate for stable, > > Yes. >> >> can we have split it to just >> as less as possible intrusive fix + moving to

Re: [RFC v3 3/7] platform/x86: intel_pmc_ipc: Use regmap calls for GCR updates

2017-10-03 Thread sathyanarayanan kuppuswamy
Hi Andy, On 10/01/2017 07:48 AM, Andy Shevchenko wrote: On Tue, Sep 5, 2017 at 8:37 AM, wrote: From: Kuppuswamy Sathyanarayanan Currently, update_no_reboot_bit() function implemented in this driver uses mutex_lock to protect its register updates. But this function is called with in atomic c

Re: [RFC v3 3/7] platform/x86: intel_pmc_ipc: Use regmap calls for GCR updates

2017-10-01 Thread Andy Shevchenko
On Tue, Sep 5, 2017 at 8:37 AM, wrote: > From: Kuppuswamy Sathyanarayanan > > Currently, update_no_reboot_bit() function implemented in this driver > uses mutex_lock to protect its register updates. But this function is > called with in atomic context in iTCO_wdt_start() and iTCO_wdt_stop() > fun

[RFC v3 3/7] platform/x86: intel_pmc_ipc: Use regmap calls for GCR updates

2017-09-04 Thread sathyanarayanan . kuppuswamy
From: Kuppuswamy Sathyanarayanan Currently, update_no_reboot_bit() function implemented in this driver uses mutex_lock to protect its register updates. But this function is called with in atomic context in iTCO_wdt_start() and iTCO_wdt_stop() functions in iTCO_wdt.c driver, which in turn causes "