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:
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:
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
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
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:
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,
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:
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:
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 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
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
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
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
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
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.
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.
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
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
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
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
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
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
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
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
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
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
26 matches
Mail list logo