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 specifi
...@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
>>
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'
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 'platform_get_res
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 driver
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 t
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 'p
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
>> Vasut
>> Subject: [PATCH v2 03/18] PCI: designware: Configuration space should be
>> specified in 'reg'
>>
>> The configuration address space has so far been specified in *ranges*,
>> however it should be specified in *reg* making it a platform MEM resource.
..@vger.kernel.org; linux-kernel@vger.kernel.org
> Cc: a...@arndb.de; t...@atomide.com; jg1@samsung.com;
> kis...@ti.com; Jason Gunthorpe; Bjorn Helgaas; Mohit KUMAR DCG; Marek
> Vasut
> Subject: [PATCH v2 03/18] PCI: designware: Configuration space should be
> specified in &#x
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 driver.
Cc: Jason Gunthorpe
Cc: Bjorn Helgaas
Cc: Mohit
13 matches
Mail list logo
