ARM config options needing review

[Eric Miao]

On Thu, May 31, 2012 at 9:04 PM, Andy Whitcroft <apw at canonical.com> wrote:
> I have been reviewing and updating the Quantal master configuration and
> noted a few options which are out of sync for ARM (for omap) and am
> wanting to understand if they should become common in value with the
> other options or have annotations.  I am happy to annotate them if you
> can indicate reasons for their delta.  They fall into two sets, the
> first set seem to be 'y' when 'm' is more the norm which may indicate
> they are boot essential, the second set are 'n' when 'm' is more the
> norm and I would like to understand why.
>
>  - CONFIG_NOP_USB_XCEIV
>   CONFIG_TWL4030_USB
>   CONFIG_USB_GPIO_VBUS
>   CONFIG_USB_MUSB_HDRC
>  - is this boot essential on arm?

I think these are for booting from USB, and if they could be compiled as
modules, theoretically it should be OK to put them into initramfs. The
problem is really some of the ARM drivers which claim to be buildable
as module, but not necessarily function correctly. So it needs a bit
verification.

>  - CONFIG_SCSI_OSD_INITIATOR

This doesn't seem to be ARM specific, and checking the source code,
it's a char dev driver, and should be harmless to be made as a module.

>   CONFIG_TIDSPBRIDGE

This is OMAP specific, although it's in staging, checking the source
shows it should be harmless to make as a module.

>   CONFIG_TI_DAVINCI_EMAC

This is Davinci specific, not in any ARM flavour of ours, though looks to
be very safe to turn on as a module.

>   CONFIG_WIMAX_I2400M_SDIO
>   CONFIG_WIMAX_I2400M_USB
>   CONFIG_WM8350_WATCHDOG

Don't think they are used on OMAP platforms, but still look to be quite
harmless to make as modules.

>   CONFIG_USB_GPIO_VBUS

I see no reason this being off, although I don't think OMAP uses this driver,
but it won't hurt to make it module.

>   CONFIG_USB_MUSB_HDRC

Ain't this option made 'y' previously?

>  - why are these off ?