> -----Original Message----- > From: Rob Herring [mailto:robh@xxxxxxxxxx] > Sent: Friday, April 27, 2018 10:46 PM > To: Nipun Gupta <nipun.gupta@xxxxxxx> > Cc: robin.murphy@xxxxxxx; will.deacon@xxxxxxx; mark.rutland@xxxxxxx; > catalin.marinas@xxxxxxx; hch@xxxxxx; gregkh@xxxxxxxxxxxxxxxxxxx; > joro@xxxxxxxxxx; m.szyprowski@xxxxxxxxxxx; shawnguo@xxxxxxxxxx; > frowand.list@xxxxxxxxx; bhelgaas@xxxxxxxxxx; iommu@lists.linux- > foundation.org; linux-kernel@xxxxxxxxxxxxxxx; devicetree@xxxxxxxxxxxxxxx; > linux-arm-kernel@xxxxxxxxxxxxxxxxxxx; linuxppc-dev@xxxxxxxxxxxxxxxx; linux- > pci@xxxxxxxxxxxxxxx; Bharat Bhushan <bharat.bhushan@xxxxxxx>; > stuyoder@xxxxxxxxx; Laurentiu Tudor <laurentiu.tudor@xxxxxxx>; Leo Li > <leoyang.li@xxxxxxx> > Subject: Re: [PATCH 2/6 v3] iommu: of: make of_pci_map_rid() available for > other devices too > > On Fri, Apr 27, 2018 at 03:57:02PM +0530, Nipun Gupta wrote: > > iommu-map property is also used by devices with fsl-mc. This > > patch moves the of_pci_map_rid to generic location, so that it > > can be used by other busses too. > > > > 'of_pci_map_rid' is renamed here to 'of_map_rid' and there is no > > functional change done in the API. > > > > Signed-off-by: Nipun Gupta <nipun.gupta@xxxxxxx> > > --- > > drivers/iommu/of_iommu.c | 6 +-- > > drivers/of/address.c | 102 > +++++++++++++++++++++++++++++++++++++++++++++ > > drivers/of/irq.c | 7 ++-- > > drivers/pci/of.c | 101 -------------------------------------------- > > include/linux/of_address.h | 11 +++++ > > include/linux/of_pci.h | 10 ----- > > 6 files changed, 120 insertions(+), 117 deletions(-) > > of/address.c isn't really the best fit either, though I don't have a > better suggestion. > > I'm guessing this breaks on Sparc which doesn't build of/address.c. > I guess move it to base.c and of.h if that is the case. Sure, that makes sense. Thank you for the suggestion !! I'll spin off new version with this change. Regards, Nipun > > Rob -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
