RE: [PATCH] iovmm: IVA2 MMU range is from 0x11000000 to 0xFFFFFFFF

[Guzman Lugo, Fernando]

Hi Hiroshi, 

> -----Original Message-----
> From: Hiroshi DOYU [mailto:Hiroshi.DOYU@xxxxxxxxx] 
> Sent: Thursday, October 07, 2010 2:14 PM
> To: Guzman Lugo, Fernando
> Cc: felipe.contreras@xxxxxxxxx; ameya.palande@xxxxxxxxx; 
> david.cohen@xxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; 
> andy.shevchenko@xxxxxxxxx; linux-omap@xxxxxxxxxxxxxxx
> Subject: Re: [PATCH] iovmm: IVA2 MMU range is from 0x11000000 
> to 0xFFFFFFFF
> 
> From: ext Fernando Guzman Lugo <x0095840@xxxxxx>
> Subject: [PATCH] iovmm: IVA2 MMU range is from 0x11000000 to 
> 0xFFFFFFFF
> Date: Thu, 7 Oct 2010 20:43:41 +0200
> 
> > IV2 MMU capable addresses start from 0x11000000
> 
> Wouldn't it be better to add an general API to configure the 
> valid 'da' range in advance?

Yes I was thinking in passing start and end range in iommu_get
(because don't need to change rage, it is needed only one time)
And create new elements in iommu struct for start and end address
 or maybe defining the range statically when the structures are
Fillup for omapxxx. But I tought I was break other users of iommu
Like omap4 and isp and it would be easier to accept an small patch.

But I am agree with you it would be better to make it configurable.
As tidspbridge iommu migratio seems to be target to 37 I can 
Make a new patch and resend.

Please let me know if you have some suggestions.

Regards,
Fernando.

> 
> I don't think that it's a good idea to introduce the iommu
> instance("iva2:iommu") specific code here.
> --
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/