Russell, Thanks for your comments.
Thank you, Best regards, Hari > -----Original Message----- > From: Russell King - ARM Linux [mailto:li...@arm.linux.org.uk] > Sent: Wednesday, August 05, 2009 3:23 PM > To: Kanigeri, Hari > Cc: Hiroshi DOYU; linux-omap@vger.kernel.org; t...@atomide.com; Shilimkar, > Santosh > Subject: Re: [PATCH v1 3/3] ARM:OMAP4 iommu:provide build support for > omap4 iommu > > On Wed, Aug 05, 2009 at 11:44:53AM -0500, Kanigeri, Hari wrote: > > -- I agree with your comments from OMAP3 point of view. > > For OMAP4, I guess Camera is not going to use IOMMU module. IOMMU > > modules will be used only by the IPC that are communicating with 2 > > remote Cores (Ducati and Tesla). > > In which case what you do is: > > config OMAP_CAMERA > ... > select OMAP_IOMMU if ARCH_OMAP3 > > which means the IOMMU support will only be built if the camera is enabled > and we're building for OMAP3. > > However, if the OMAP3 hardware uses the IOMMU but the OMAP4 hardware > doesn't, I'd hazard a guess (and it's only a guess) that the drivers > will be soo different that squeezing them into one file/config option > would be silly. > > > Having said this, there might not > > be any clients of IOMMU in the Kernel space as we are looking at > > the option of using the IOMMU as a character driver from User-space. > > For this reason, I think we should have the configuration option to > > build iommu. Please let me know your comments. > > In which case, the IOMMU character driver can select the core IOMMU > support. > > Making symbols which are 'selected' visible causes problems - you > can't disable them and you can't work out why they're being > forcefully enabled, which just annoys people who are trying to > configure the kernel. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
