From: Hiroshi DOYU <Hiroshi.DOYU@xxxxxxxxx> Subject: Re: [RFC/PATCH 3/3] omap3-iommu: remote registration Date: Mon, 18 May 2009 16:35:33 +0300 (EEST) > From: ext Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx> > Subject: Re: [RFC/PATCH 3/3] omap3-iommu: remote registration > Date: Mon, 18 May 2009 14:11:13 +0200 > > > On Sat, May 16, 2009 at 01:05:50PM +0300, Felipe Contreras wrote: > > > This allows devices to be registered only when they are used. The > > > current dsp-bridge driver for example is not using iommu so registering > > > the iommu iva2 device would conflict. By allowing remote registration > > > the dsp-bridge can decide when the iommu iva2 device is registered. > > > > I don't think that this is a good idea - what happens if two people > > call omap_iommu_add() for the same IOMMU device independently? > > > > The real problem here seems to be the TI DSP bridge code, and if that's > > the case why can't we just avoid registering IVA2 if the TI DSP bridge > > code is enabled. That solves your stated problem without creating > > additional management issues. > > How about the attached patch? I think this is enough. Oops, CONFIG_NAME was wrong. Attached new one.
Attachment:
0001-omap-iommu-disable-iva2-iommu-device-registration-i.patch
Description: Binary data
