Re: [PATCH v6 5/6] platform/x86: intel_pmc_ipc: Fix iTCO_wdt GCS memory mapping failure

2017-04-06 Thread Andy Shevchenko
On Thu, Apr 6, 2017 at 1:54 AM, Kuppuswamy Sathyanarayanan wrote: > iTCO_wdt driver need access to PMC_CFG GCR register to modify the > noreboot setting. Currently, this is done by passing PMC_CFG reg > address as memory resource to watchdog driver and

Re: [PATCH v6 5/6] platform/x86: intel_pmc_ipc: Fix iTCO_wdt GCS memory mapping failure

2017-04-06 Thread Andy Shevchenko
On Thu, Apr 6, 2017 at 1:54 AM, Kuppuswamy Sathyanarayanan wrote: > iTCO_wdt driver need access to PMC_CFG GCR register to modify the > noreboot setting. Currently, this is done by passing PMC_CFG reg > address as memory resource to watchdog driver and allowing it directly > modify the PMC_CFG

[PATCH v6 5/6] platform/x86: intel_pmc_ipc: Fix iTCO_wdt GCS memory mapping failure

2017-04-05 Thread Kuppuswamy Sathyanarayanan
iTCO_wdt driver need access to PMC_CFG GCR register to modify the noreboot setting. Currently, this is done by passing PMC_CFG reg address as memory resource to watchdog driver and allowing it directly modify the PMC_CFG register. But currently PMC driver also has requirement to memory map the

[PATCH v6 5/6] platform/x86: intel_pmc_ipc: Fix iTCO_wdt GCS memory mapping failure

2017-04-05 Thread Kuppuswamy Sathyanarayanan
iTCO_wdt driver need access to PMC_CFG GCR register to modify the noreboot setting. Currently, this is done by passing PMC_CFG reg address as memory resource to watchdog driver and allowing it directly modify the PMC_CFG register. But currently PMC driver also has requirement to memory map the