On 03/16/2017 12:20 PM, Rajneesh Bhardwaj wrote:
On Thu, Mar 16, 2017 at 11:50:16AM -0700, sathyanarayanan kuppuswamy wrote:
Hi,
On 03/16/2017 07:52 AM, Rajneesh Bhardwaj wrote:
On Wed, Mar 15, 2017 at 08:32:53PM -0700, Kuppuswamy Sathyanarayanan wrote:
Mapping entire GCR mem region in
On 03/16/2017 12:20 PM, Rajneesh Bhardwaj wrote:
On Thu, Mar 16, 2017 at 11:50:16AM -0700, sathyanarayanan kuppuswamy wrote:
Hi,
On 03/16/2017 07:52 AM, Rajneesh Bhardwaj wrote:
On Wed, Mar 15, 2017 at 08:32:53PM -0700, Kuppuswamy Sathyanarayanan wrote:
Mapping entire GCR mem region in
Hi Andy,
On 03/16/2017 01:12 PM, Andy Shevchenko wrote:
On Thu, Mar 16, 2017 at 8:13 PM, Rajneesh Bhardwaj
wrote:
On Thu, Mar 16, 2017 at 06:05:39PM +0200, Andy Shevchenko wrote:
On Thu, Mar 16, 2017 at 4:52 PM, Rajneesh Bhardwaj
Hi Andy,
On 03/16/2017 01:12 PM, Andy Shevchenko wrote:
On Thu, Mar 16, 2017 at 8:13 PM, Rajneesh Bhardwaj
wrote:
On Thu, Mar 16, 2017 at 06:05:39PM +0200, Andy Shevchenko wrote:
On Thu, Mar 16, 2017 at 4:52 PM, Rajneesh Bhardwaj
wrote:
On Wed, Mar 15, 2017 at 08:32:53PM -0700, Kuppuswamy
On Thu, Mar 16, 2017 at 8:13 PM, Rajneesh Bhardwaj
wrote:
> On Thu, Mar 16, 2017 at 06:05:39PM +0200, Andy Shevchenko wrote:
>> On Thu, Mar 16, 2017 at 4:52 PM, Rajneesh Bhardwaj
>> wrote:
>> > On Wed, Mar 15, 2017 at 08:32:53PM -0700,
On Thu, Mar 16, 2017 at 8:13 PM, Rajneesh Bhardwaj
wrote:
> On Thu, Mar 16, 2017 at 06:05:39PM +0200, Andy Shevchenko wrote:
>> On Thu, Mar 16, 2017 at 4:52 PM, Rajneesh Bhardwaj
>> wrote:
>> > On Wed, Mar 15, 2017 at 08:32:53PM -0700, Kuppuswamy Sathyanarayanan wrote:
>> >> Mapping entire GCR
On Thu, Mar 16, 2017 at 11:50:16AM -0700, sathyanarayanan kuppuswamy wrote:
> Hi,
>
>
> On 03/16/2017 07:52 AM, Rajneesh Bhardwaj wrote:
> >On Wed, Mar 15, 2017 at 08:32:53PM -0700, Kuppuswamy Sathyanarayanan wrote:
> >>Mapping entire GCR mem region in this driver creates
> >>mem region request
On Thu, Mar 16, 2017 at 11:50:16AM -0700, sathyanarayanan kuppuswamy wrote:
> Hi,
>
>
> On 03/16/2017 07:52 AM, Rajneesh Bhardwaj wrote:
> >On Wed, Mar 15, 2017 at 08:32:53PM -0700, Kuppuswamy Sathyanarayanan wrote:
> >>Mapping entire GCR mem region in this driver creates
> >>mem region request
Hi,
On 03/16/2017 07:52 AM, Rajneesh Bhardwaj wrote:
On Wed, Mar 15, 2017 at 08:32:53PM -0700, Kuppuswamy Sathyanarayanan wrote:
Mapping entire GCR mem region in this driver creates
mem region request conflict in sub devices that depend
on PMC. This creates driver probe failure in devices
Hi,
On 03/16/2017 07:52 AM, Rajneesh Bhardwaj wrote:
On Wed, Mar 15, 2017 at 08:32:53PM -0700, Kuppuswamy Sathyanarayanan wrote:
Mapping entire GCR mem region in this driver creates
mem region request conflict in sub devices that depend
on PMC. This creates driver probe failure in devices
On Thu, Mar 16, 2017 at 06:05:39PM +0200, Andy Shevchenko wrote:
> On Thu, Mar 16, 2017 at 4:52 PM, Rajneesh Bhardwaj
> wrote:
> > On Wed, Mar 15, 2017 at 08:32:53PM -0700, Kuppuswamy Sathyanarayanan wrote:
> >> Mapping entire GCR mem region in this driver creates
>
On Thu, Mar 16, 2017 at 06:05:39PM +0200, Andy Shevchenko wrote:
> On Thu, Mar 16, 2017 at 4:52 PM, Rajneesh Bhardwaj
> wrote:
> > On Wed, Mar 15, 2017 at 08:32:53PM -0700, Kuppuswamy Sathyanarayanan wrote:
> >> Mapping entire GCR mem region in this driver creates
> >> mem region request conflict
On Thu, Mar 16, 2017 at 4:52 PM, Rajneesh Bhardwaj
wrote:
> On Wed, Mar 15, 2017 at 08:32:53PM -0700, Kuppuswamy Sathyanarayanan wrote:
>> Mapping entire GCR mem region in this driver creates
>> mem region request conflict in sub devices that depend
>> on PMC. This
On Thu, Mar 16, 2017 at 4:52 PM, Rajneesh Bhardwaj
wrote:
> On Wed, Mar 15, 2017 at 08:32:53PM -0700, Kuppuswamy Sathyanarayanan wrote:
>> Mapping entire GCR mem region in this driver creates
>> mem region request conflict in sub devices that depend
>> on PMC. This creates driver probe failure in
On Wed, Mar 15, 2017 at 08:32:53PM -0700, Kuppuswamy Sathyanarayanan wrote:
> Mapping entire GCR mem region in this driver creates
> mem region request conflict in sub devices that depend
> on PMC. This creates driver probe failure in devices like
> iTC0_wdt and telemetry device.
While this patch
On Wed, Mar 15, 2017 at 08:32:53PM -0700, Kuppuswamy Sathyanarayanan wrote:
> Mapping entire GCR mem region in this driver creates
> mem region request conflict in sub devices that depend
> on PMC. This creates driver probe failure in devices like
> iTC0_wdt and telemetry device.
While this patch
Mapping entire GCR mem region in this driver creates
mem region request conflict in sub devices that depend
on PMC. This creates driver probe failure in devices like
iTC0_wdt and telemetry device.
Currently this driver only need memory mapping for
s0ix counter registers. So this patch fixes this
Mapping entire GCR mem region in this driver creates
mem region request conflict in sub devices that depend
on PMC. This creates driver probe failure in devices like
iTC0_wdt and telemetry device.
Currently this driver only need memory mapping for
s0ix counter registers. So this patch fixes this
18 matches
Mail list logo