> -----Original Message----- > From: Hiroshi DOYU [mailto:Hiroshi.DOYU@xxxxxxxxx] > Sent: Thursday, September 09, 2010 11:52 AM > To: Balbi, Felipe > Cc: Premi, Sanjeev; linux-omap@xxxxxxxxxxxxxxx > Subject: Re: [PATCH] omap: OMAP_IOMMU not visible in menuconfig > > On Thu, 9 Sep 2010 07:58:55 +0200 > ext Felipe Balbi <balbi@xxxxxx> wrote: > > > On Thu, Sep 09, 2010 at 12:04:45AM -0500, Hiroshi DOYU wrote: > > >Hi Sanjeev, > > > > > >From: ext Sanjeev Premi <premi@xxxxxx> > > >Subject: [PATCH] omap: OMAP_IOMMU not visible in menuconfig > > >Date: Wed, 8 Sep 2010 16:51:21 +0200 > > > > > >> The menu option to select CONFIG_OMAP_IOMMU > > >> was not visible in the menuconfig due to missing > > >> description. > > > > > >There's no point to make OMAP_IOMMU visible since this is a kind of > > >feature used by other device implicitly. OMAP_IOMMU on > menu might confuse > > >users at kernel menuconfig. Instead this should be automatically > > >selected by its clients when it is selected. For exmaple, the case > > >that DSP or Tesla is selected. There was a discussion about this > > >before. > > > > in that case... > > > > >> @@ -98,7 +98,7 @@ config OMAP_MBOX_KFIFO_SIZE > > >> module parameter). > > >> > > >> config OMAP_IOMMU > > >> - tristate > > >> + tristate "OMAP IOMMU support" > > > > it doesn't have to be tristate as select will always mark it 'y' > > Right;p > [sp] So, we will need to "select" this option with ARCH_OMAP3. And maybe for OMAP4... ~sanjeev -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
