Re: [PATCH v2 3/4] watchdog: iTCO_wdt: Fix PMC GCR memory mapping failure

2017-03-19 Thread kbuild test robot
Hi Kuppuswamy, [auto build test ERROR on linus/master] [also build test ERROR on v4.11-rc3 next-20170310] [cannot apply to platform-drivers-x86/for-next tip/x86/core] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v2 3/4] watchdog: iTCO_wdt: Fix PMC GCR memory mapping failure

2017-03-19 Thread kbuild test robot
Hi Kuppuswamy, [auto build test ERROR on linus/master] [also build test ERROR on v4.11-rc3 next-20170310] [cannot apply to platform-drivers-x86/for-next tip/x86/core] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v2 3/4] watchdog: iTCO_wdt: Fix PMC GCR memory mapping failure

2017-03-17 Thread sathyanarayanan kuppuswamy
On 03/17/2017 06:40 AM, Guenter Roeck wrote: On 03/17/2017 04:43 AM, Rajneesh Bhardwaj wrote: On Thu, Mar 16, 2017 at 05:41:35PM -0700, Kuppuswamy Sathyanarayanan wrote: Currently, iTCO watchdog driver uses memory map to access PMC_CFG GCR register. But the entire GCR address space is

Re: [PATCH v2 3/4] watchdog: iTCO_wdt: Fix PMC GCR memory mapping failure

2017-03-17 Thread sathyanarayanan kuppuswamy
On 03/17/2017 06:40 AM, Guenter Roeck wrote: On 03/17/2017 04:43 AM, Rajneesh Bhardwaj wrote: On Thu, Mar 16, 2017 at 05:41:35PM -0700, Kuppuswamy Sathyanarayanan wrote: Currently, iTCO watchdog driver uses memory map to access PMC_CFG GCR register. But the entire GCR address space is

Re: [PATCH v2 3/4] watchdog: iTCO_wdt: Fix PMC GCR memory mapping failure

2017-03-17 Thread sathyanarayanan kuppuswamy
Hi Andy, On 03/17/2017 11:38 AM, Andy Shevchenko wrote: On Fri, Mar 17, 2017 at 7:37 PM, sathyanarayanan kuppuswamy wrote: On 03/17/2017 07:25 AM, Andy Shevchenko wrote: On Fri, Mar 17, 2017 at 3:40 PM, Guenter Roeck wrote:

Re: [PATCH v2 3/4] watchdog: iTCO_wdt: Fix PMC GCR memory mapping failure

2017-03-17 Thread sathyanarayanan kuppuswamy
Hi Andy, On 03/17/2017 11:38 AM, Andy Shevchenko wrote: On Fri, Mar 17, 2017 at 7:37 PM, sathyanarayanan kuppuswamy wrote: On 03/17/2017 07:25 AM, Andy Shevchenko wrote: On Fri, Mar 17, 2017 at 3:40 PM, Guenter Roeck wrote: On 03/17/2017 04:43 AM, Rajneesh Bhardwaj wrote: On Thu, Mar 16,

Re: [PATCH v2 3/4] watchdog: iTCO_wdt: Fix PMC GCR memory mapping failure

2017-03-17 Thread sathyanarayanan kuppuswamy
On 03/17/2017 10:50 AM, Guenter Roeck wrote: On Fri, Mar 17, 2017 at 10:24:35AM -0700, sathyanarayanan kuppuswamy wrote: On 03/17/2017 06:40 AM, Guenter Roeck wrote: On 03/17/2017 04:43 AM, Rajneesh Bhardwaj wrote: On Thu, Mar 16, 2017 at 05:41:35PM -0700, Kuppuswamy Sathyanarayanan wrote:

Re: [PATCH v2 3/4] watchdog: iTCO_wdt: Fix PMC GCR memory mapping failure

2017-03-17 Thread sathyanarayanan kuppuswamy
On 03/17/2017 10:50 AM, Guenter Roeck wrote: On Fri, Mar 17, 2017 at 10:24:35AM -0700, sathyanarayanan kuppuswamy wrote: On 03/17/2017 06:40 AM, Guenter Roeck wrote: On 03/17/2017 04:43 AM, Rajneesh Bhardwaj wrote: On Thu, Mar 16, 2017 at 05:41:35PM -0700, Kuppuswamy Sathyanarayanan wrote:

Re: [PATCH v2 3/4] watchdog: iTCO_wdt: Fix PMC GCR memory mapping failure

2017-03-17 Thread Andy Shevchenko
On Fri, Mar 17, 2017 at 7:37 PM, sathyanarayanan kuppuswamy wrote: > On 03/17/2017 07:25 AM, Andy Shevchenko wrote: >> On Fri, Mar 17, 2017 at 3:40 PM, Guenter Roeck wrote: >>> On 03/17/2017 04:43 AM, Rajneesh Bhardwaj wrote:

Re: [PATCH v2 3/4] watchdog: iTCO_wdt: Fix PMC GCR memory mapping failure

2017-03-17 Thread Andy Shevchenko
On Fri, Mar 17, 2017 at 7:37 PM, sathyanarayanan kuppuswamy wrote: > On 03/17/2017 07:25 AM, Andy Shevchenko wrote: >> On Fri, Mar 17, 2017 at 3:40 PM, Guenter Roeck wrote: >>> On 03/17/2017 04:43 AM, Rajneesh Bhardwaj wrote: On Thu, Mar 16, 2017 at 05:41:35PM -0700, Kuppuswamy

Re: [PATCH v2 3/4] watchdog: iTCO_wdt: Fix PMC GCR memory mapping failure

2017-03-17 Thread Guenter Roeck
On Fri, Mar 17, 2017 at 10:24:35AM -0700, sathyanarayanan kuppuswamy wrote: > > > On 03/17/2017 06:40 AM, Guenter Roeck wrote: > >On 03/17/2017 04:43 AM, Rajneesh Bhardwaj wrote: > >>On Thu, Mar 16, 2017 at 05:41:35PM -0700, Kuppuswamy Sathyanarayanan > >>wrote: > >>>Currently, iTCO watchdog

Re: [PATCH v2 3/4] watchdog: iTCO_wdt: Fix PMC GCR memory mapping failure

2017-03-17 Thread Guenter Roeck
On Fri, Mar 17, 2017 at 10:24:35AM -0700, sathyanarayanan kuppuswamy wrote: > > > On 03/17/2017 06:40 AM, Guenter Roeck wrote: > >On 03/17/2017 04:43 AM, Rajneesh Bhardwaj wrote: > >>On Thu, Mar 16, 2017 at 05:41:35PM -0700, Kuppuswamy Sathyanarayanan > >>wrote: > >>>Currently, iTCO watchdog

Re: [PATCH v2 3/4] watchdog: iTCO_wdt: Fix PMC GCR memory mapping failure

2017-03-17 Thread sathyanarayanan kuppuswamy
On 03/17/2017 07:25 AM, Andy Shevchenko wrote: On Fri, Mar 17, 2017 at 3:40 PM, Guenter Roeck wrote: On 03/17/2017 04:43 AM, Rajneesh Bhardwaj wrote: On Thu, Mar 16, 2017 at 05:41:35PM -0700, Kuppuswamy Sathyanarayanan wrote: Currently, iTCO watchdog driver uses memory

Re: [PATCH v2 3/4] watchdog: iTCO_wdt: Fix PMC GCR memory mapping failure

2017-03-17 Thread sathyanarayanan kuppuswamy
On 03/17/2017 07:25 AM, Andy Shevchenko wrote: On Fri, Mar 17, 2017 at 3:40 PM, Guenter Roeck wrote: On 03/17/2017 04:43 AM, Rajneesh Bhardwaj wrote: On Thu, Mar 16, 2017 at 05:41:35PM -0700, Kuppuswamy Sathyanarayanan wrote: Currently, iTCO watchdog driver uses memory map to access

Re: [PATCH v2 3/4] watchdog: iTCO_wdt: Fix PMC GCR memory mapping failure

2017-03-17 Thread sathyanarayanan kuppuswamy
Hi Rajneesh, On 03/17/2017 04:43 AM, Rajneesh Bhardwaj wrote: On Thu, Mar 16, 2017 at 05:41:35PM -0700, Kuppuswamy Sathyanarayanan wrote: Currently, iTCO watchdog driver uses memory map to access PMC_CFG GCR register. But the entire GCR address space is already mapped in intel_scu_ipc driver.

Re: [PATCH v2 3/4] watchdog: iTCO_wdt: Fix PMC GCR memory mapping failure

2017-03-17 Thread sathyanarayanan kuppuswamy
Hi Rajneesh, On 03/17/2017 04:43 AM, Rajneesh Bhardwaj wrote: On Thu, Mar 16, 2017 at 05:41:35PM -0700, Kuppuswamy Sathyanarayanan wrote: Currently, iTCO watchdog driver uses memory map to access PMC_CFG GCR register. But the entire GCR address space is already mapped in intel_scu_ipc driver.

Re: [PATCH v2 3/4] watchdog: iTCO_wdt: Fix PMC GCR memory mapping failure

2017-03-17 Thread Andy Shevchenko
On Fri, Mar 17, 2017 at 3:40 PM, Guenter Roeck wrote: > On 03/17/2017 04:43 AM, Rajneesh Bhardwaj wrote: >> On Thu, Mar 16, 2017 at 05:41:35PM -0700, Kuppuswamy Sathyanarayanan >> wrote: >>> >>> Currently, iTCO watchdog driver uses memory map to access >>> PMC_CFG GCR

Re: [PATCH v2 3/4] watchdog: iTCO_wdt: Fix PMC GCR memory mapping failure

2017-03-17 Thread Andy Shevchenko
On Fri, Mar 17, 2017 at 3:40 PM, Guenter Roeck wrote: > On 03/17/2017 04:43 AM, Rajneesh Bhardwaj wrote: >> On Thu, Mar 16, 2017 at 05:41:35PM -0700, Kuppuswamy Sathyanarayanan >> wrote: >>> >>> Currently, iTCO watchdog driver uses memory map to access >>> PMC_CFG GCR register. But the entire GCR

Re: [PATCH v2 3/4] watchdog: iTCO_wdt: Fix PMC GCR memory mapping failure

2017-03-17 Thread Rajneesh Bhardwaj
On Fri, Mar 17, 2017 at 06:40:22AM -0700, Guenter Roeck wrote: > On 03/17/2017 04:43 AM, Rajneesh Bhardwaj wrote: > >On Thu, Mar 16, 2017 at 05:41:35PM -0700, Kuppuswamy Sathyanarayanan wrote: > >>Currently, iTCO watchdog driver uses memory map to access > >>PMC_CFG GCR register. But the entire

Re: [PATCH v2 3/4] watchdog: iTCO_wdt: Fix PMC GCR memory mapping failure

2017-03-17 Thread Rajneesh Bhardwaj
On Fri, Mar 17, 2017 at 06:40:22AM -0700, Guenter Roeck wrote: > On 03/17/2017 04:43 AM, Rajneesh Bhardwaj wrote: > >On Thu, Mar 16, 2017 at 05:41:35PM -0700, Kuppuswamy Sathyanarayanan wrote: > >>Currently, iTCO watchdog driver uses memory map to access > >>PMC_CFG GCR register. But the entire

Re: [PATCH v2 3/4] watchdog: iTCO_wdt: Fix PMC GCR memory mapping failure

2017-03-17 Thread Guenter Roeck
On 03/17/2017 04:43 AM, Rajneesh Bhardwaj wrote: On Thu, Mar 16, 2017 at 05:41:35PM -0700, Kuppuswamy Sathyanarayanan wrote: Currently, iTCO watchdog driver uses memory map to access PMC_CFG GCR register. But the entire GCR address space is already mapped in intel_scu_ipc driver. So remapping

Re: [PATCH v2 3/4] watchdog: iTCO_wdt: Fix PMC GCR memory mapping failure

2017-03-17 Thread Guenter Roeck
On 03/17/2017 04:43 AM, Rajneesh Bhardwaj wrote: On Thu, Mar 16, 2017 at 05:41:35PM -0700, Kuppuswamy Sathyanarayanan wrote: Currently, iTCO watchdog driver uses memory map to access PMC_CFG GCR register. But the entire GCR address space is already mapped in intel_scu_ipc driver. So remapping

Re: [PATCH v2 3/4] watchdog: iTCO_wdt: Fix PMC GCR memory mapping failure

2017-03-17 Thread Rajneesh Bhardwaj
On Thu, Mar 16, 2017 at 05:41:35PM -0700, Kuppuswamy Sathyanarayanan wrote: > Currently, iTCO watchdog driver uses memory map to access > PMC_CFG GCR register. But the entire GCR address space is > already mapped in intel_scu_ipc driver. So remapping the intel_pmc_ipc driver. > GCR register in

Re: [PATCH v2 3/4] watchdog: iTCO_wdt: Fix PMC GCR memory mapping failure

2017-03-17 Thread Rajneesh Bhardwaj
On Thu, Mar 16, 2017 at 05:41:35PM -0700, Kuppuswamy Sathyanarayanan wrote: > Currently, iTCO watchdog driver uses memory map to access > PMC_CFG GCR register. But the entire GCR address space is > already mapped in intel_scu_ipc driver. So remapping the intel_pmc_ipc driver. > GCR register in

[PATCH v2 3/4] watchdog: iTCO_wdt: Fix PMC GCR memory mapping failure

2017-03-16 Thread Kuppuswamy Sathyanarayanan
Currently, iTCO watchdog driver uses memory map to access PMC_CFG GCR register. But the entire GCR address space is already mapped in intel_scu_ipc driver. So remapping the GCR register in this driver causes the mem request failure in iTCO_wdt probe function. This patch fixes this issue by using

[PATCH v2 3/4] watchdog: iTCO_wdt: Fix PMC GCR memory mapping failure

2017-03-16 Thread Kuppuswamy Sathyanarayanan
Currently, iTCO watchdog driver uses memory map to access PMC_CFG GCR register. But the entire GCR address space is already mapped in intel_scu_ipc driver. So remapping the GCR register in this driver causes the mem request failure in iTCO_wdt probe function. This patch fixes this issue by using