[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130411131134.GC28981@arm.com>
Date: Thu, 11 Apr 2013 14:11:34 +0100
From: Andrew Murray <andrew.murray@....com>
To: Rob Herring <robherring2@...il.com>
Cc: "rob.herring@...xeda.com" <rob.herring@...xeda.com>,
"siva.kallam@...sung.com" <siva.kallam@...sung.com>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
Liviu Dudau <Liviu.Dudau@....com>,
"paulus@...ba.org" <paulus@...ba.org>,
"linux-samsung-soc@...r.kernel.org"
<linux-samsung-soc@...r.kernel.org>,
"linux@....linux.org.uk" <linux@....linux.org.uk>,
"jg1.han@...sung.com" <jg1.han@...sung.com>,
"jgunthorpe@...idianresearch.com" <jgunthorpe@...idianresearch.com>,
"devicetree-discuss@...ts.ozlabs.org"
<devicetree-discuss@...ts.ozlabs.org>,
"kgene.kim@...sung.com" <kgene.kim@...sung.com>,
"bhelgaas@...gle.com" <bhelgaas@...gle.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"suren.reddy@...sung.com" <suren.reddy@...sung.com>
Subject: Re: [PATCH v5 2/3] of/pci: Provide support for parsing PCI DT
ranges property
On Wed, Apr 10, 2013 at 07:26:02PM +0100, Rob Herring wrote:
> On 04/10/2013 02:29 AM, Andrew Murray wrote:
> > This patch factors out common implementation patterns to reduce overall kernel
> > code and provide a means for host bridge drivers to directly obtain struct
> > resources from the DT's ranges property without relying on architecture specific
> > DT handling. This will make it easier to write archiecture independent host bridge
> > drivers and mitigate against further duplication of DT parsing code.
> >
> > This patch can be used in the following way:
> >
> > struct of_pci_range_parser parser;
> > struct of_pci_range range;
> >
> > if (of_pci_range_parser(&parser, np))
> > ; //no ranges property
> >
> > for_each_of_pci_range(&parser, &range) {
> >
> > /*
> > directly access properties of the address range, e.g.:
> > range.pci_space, range.pci_addr, range.cpu_addr,
> > range.size, range.flags
> >
> > alternatively obtain a struct resource, e.g.:
> > struct resource res;
> > of_pci_range_to_resource(&range, np, &res);
> > */
> > }
> >
> > Additionally the implementation takes care of adjacent ranges and merges them
> > into a single range (as was the case with powerpc and microblaze).
> >
> > Signed-off-by: Andrew Murray <Andrew.Murray@....com>
> > Signed-off-by: Liviu Dudau <Liviu.Dudau@....com>
> > Signed-off-by: Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>
> > ---
>
> A few minor things below, otherwise:
>
> Reviewed-by: Rob Herring <rob.herring@...xeda.com>
>
Thanks for the feedback, I've included this in my next spin.
Andrew Murray
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists