On Wednesday, June 18, 2014 6:15 PM, Kishon Vijay Abraham I wrote:
> On Friday 30 May 2014 07:45 PM, Karicheri, Muralidharan wrote:
> >> On 5/29/2014 2:38 AM, ABRAHAM, KISHON VIJAY wrote:
> >>> The configuration address space has so far been specified in *ranges*,
> >>> however it should be
...@vger.kernel.org; linux-arm-
>> ker...@lists.infradead.org; linux-o...@vger.kernel.org;
>> linux-...@vger.kernel.org; linux-
>> ker...@vger.kernel.org; a...@arndb.de; t...@atomide.com; jg1@samsung.com;
>> Jason Gunthorpe; Bjorn Helgaas; Mohit Kumar; Marek Vasut
>>
...@lists.infradead.org; linux-o...@vger.kernel.org;
linux-...@vger.kernel.org; linux-
ker...@vger.kernel.org; a...@arndb.de; t...@atomide.com; jg1@samsung.com;
Jason Gunthorpe; Bjorn Helgaas; Mohit Kumar; Marek Vasut
Subject: Re: [PATCH v2 03/18] PCI: designware: Configuration space should
On Wednesday, June 18, 2014 6:15 PM, Kishon Vijay Abraham I wrote:
On Friday 30 May 2014 07:45 PM, Karicheri, Muralidharan wrote:
On 5/29/2014 2:38 AM, ABRAHAM, KISHON VIJAY wrote:
The configuration address space has so far been specified in *ranges*,
however it should be specified in *reg*
ernel.org;
>linux-...@vger.kernel.org; linux-
>ker...@vger.kernel.org; a...@arndb.de; t...@atomide.com; jg1@samsung.com;
>Jason Gunthorpe; Bjorn Helgaas; Mohit Kumar; Marek Vasut
>Subject: Re: [PATCH v2 03/18] PCI: designware: Configuration space should be
>specified
>in 'reg'
>
>O
; linux-
ker...@vger.kernel.org; a...@arndb.de; t...@atomide.com; jg1@samsung.com;
Jason Gunthorpe; Bjorn Helgaas; Mohit Kumar; Marek Vasut
Subject: Re: [PATCH v2 03/18] PCI: designware: Configuration space should be
specified
in 'reg'
On 5/29/2014 2:38 AM, ABRAHAM, KISHON VIJAY wrote
Hi,
On Thursday 29 May 2014 10:02 PM, Murali Karicheri wrote:
> On 5/29/2014 2:38 AM, ABRAHAM, KISHON VIJAY wrote:
>> The configuration address space has so far been specified in *ranges*,
>> however it should be specified in *reg* making it a platform MEM resource.
>> Hence used
On May 29, 2014, at 11:30 AM, Jason Gunthorpe
wrote:
> On Thu, May 29, 2014 at 11:03:36AM -0500, Kumar Gala wrote:
>
>> Just because the kernel doesn’t handle this is NO reason to change
>> the way the DT works.
>
> The OF specs do not specify how to process a config type ranges entry,
> and
On 5/29/2014 2:38 AM, ABRAHAM, KISHON VIJAY wrote:
The configuration address space has so far been specified in *ranges*,
however it should be specified in *reg* making it a platform MEM resource.
Hence used 'platform_get_resource_*' API to get configuration address
space in the designware
On Thu, May 29, 2014 at 11:03:36AM -0500, Kumar Gala wrote:
> Just because the kernel doesn’t handle this is NO reason to change
> the way the DT works.
The OF specs do not specify how to process a config type ranges entry,
and we all mutually agreed that the only sane interpretation for such
a
On May 29, 2014, at 10:18 AM, Liviu Dudau wrote:
> On Thu, May 29, 2014 at 10:03:54AM -0500, Kumar Gala wrote:
>>
>> On May 29, 2014, at 1:38 AM, Kishon Vijay Abraham I wrote:
>>
>>> The configuration address space has so far been specified in *ranges*,
>>> however it should be specified in
On Thu, May 29, 2014 at 10:03:54AM -0500, Kumar Gala wrote:
>
> On May 29, 2014, at 1:38 AM, Kishon Vijay Abraham I wrote:
>
> > The configuration address space has so far been specified in *ranges*,
> > however it should be specified in *reg* making it a platform MEM resource.
> > Hence used
On May 29, 2014, at 1:38 AM, Kishon Vijay Abraham I wrote:
> The configuration address space has so far been specified in *ranges*,
> however it should be specified in *reg* making it a platform MEM resource.
> Hence used 'platform_get_resource_*' API to get configuration address
> space in the
Hi,
On Thursday 29 May 2014 12:41 PM, Mohit KUMAR DCG wrote:
> Hello Kishon,
>
>> -Original Message-
>> From: Kishon Vijay Abraham I [mailto:kis...@ti.com]
>> Sent: Thursday, May 29, 2014 12:08 PM
>> To: devicet...@vger.kernel.org; linux-...@vger.kernel.org; linux-arm-
>>
Hello Kishon,
> -Original Message-
> From: Kishon Vijay Abraham I [mailto:kis...@ti.com]
> Sent: Thursday, May 29, 2014 12:08 PM
> To: devicet...@vger.kernel.org; linux-...@vger.kernel.org; linux-arm-
> ker...@lists.infradead.org; linux-o...@vger.kernel.org; linux-
> p...@vger.kernel.org;
Hello Kishon,
-Original Message-
From: Kishon Vijay Abraham I [mailto:kis...@ti.com]
Sent: Thursday, May 29, 2014 12:08 PM
To: devicet...@vger.kernel.org; linux-...@vger.kernel.org; linux-arm-
ker...@lists.infradead.org; linux-o...@vger.kernel.org; linux-
p...@vger.kernel.org;
Hi,
On Thursday 29 May 2014 12:41 PM, Mohit KUMAR DCG wrote:
Hello Kishon,
-Original Message-
From: Kishon Vijay Abraham I [mailto:kis...@ti.com]
Sent: Thursday, May 29, 2014 12:08 PM
To: devicet...@vger.kernel.org; linux-...@vger.kernel.org; linux-arm-
ker...@lists.infradead.org;
On May 29, 2014, at 1:38 AM, Kishon Vijay Abraham I kis...@ti.com wrote:
The configuration address space has so far been specified in *ranges*,
however it should be specified in *reg* making it a platform MEM resource.
Hence used 'platform_get_resource_*' API to get configuration address
On Thu, May 29, 2014 at 10:03:54AM -0500, Kumar Gala wrote:
On May 29, 2014, at 1:38 AM, Kishon Vijay Abraham I kis...@ti.com wrote:
The configuration address space has so far been specified in *ranges*,
however it should be specified in *reg* making it a platform MEM resource.
Hence
On May 29, 2014, at 10:18 AM, Liviu Dudau li...@dudau.co.uk wrote:
On Thu, May 29, 2014 at 10:03:54AM -0500, Kumar Gala wrote:
On May 29, 2014, at 1:38 AM, Kishon Vijay Abraham I kis...@ti.com wrote:
The configuration address space has so far been specified in *ranges*,
however it should
On Thu, May 29, 2014 at 11:03:36AM -0500, Kumar Gala wrote:
Just because the kernel doesn’t handle this is NO reason to change
the way the DT works.
The OF specs do not specify how to process a config type ranges entry,
and we all mutually agreed that the only sane interpretation for such
a
On 5/29/2014 2:38 AM, ABRAHAM, KISHON VIJAY wrote:
The configuration address space has so far been specified in *ranges*,
however it should be specified in *reg* making it a platform MEM resource.
Hence used 'platform_get_resource_*' API to get configuration address
space in the designware
On May 29, 2014, at 11:30 AM, Jason Gunthorpe jguntho...@obsidianresearch.com
wrote:
On Thu, May 29, 2014 at 11:03:36AM -0500, Kumar Gala wrote:
Just because the kernel doesn’t handle this is NO reason to change
the way the DT works.
The OF specs do not specify how to process a config
Hi,
On Thursday 29 May 2014 10:02 PM, Murali Karicheri wrote:
On 5/29/2014 2:38 AM, ABRAHAM, KISHON VIJAY wrote:
The configuration address space has so far been specified in *ranges*,
however it should be specified in *reg* making it a platform MEM resource.
Hence used
24 matches
Mail list logo
