* Arce, Abraham <[email protected]> [100422 07:39]:
> From: Syed Rafiuddin <[email protected]>
>
> Add OMAP4 data to allow McSPI driver built
>
> Signed-off-by: Syed Rafiuddin <[email protected]>
> Signed-off-by: Shubhro <[email protected]>
> Signed-off-by: Santosh Shilimkar <santosh [email protected]>
> Signed-off-by: Abraham Arce <[email protected]>
> ---
> drivers/spi/Kconfig | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/spi/Kconfig b/drivers/spi/Kconfig
> index a191fa2..5f54235 100644
> --- a/drivers/spi/Kconfig
> +++ b/drivers/spi/Kconfig
> @@ -180,10 +180,10 @@ config SPI_OMAP_UWIRE
> This hooks up to the MicroWire controller on OMAP1 chips.
>
> config SPI_OMAP24XX
> - tristate "McSPI driver for OMAP24xx/OMAP34xx"
> - depends on ARCH_OMAP2 || ARCH_OMAP3
> + tristate "McSPI driver for OMAP24xx/OMAP34xx/OMAP44xx"
> + depends on ARCH_OMAP24XX || ARCH_OMAP34XX || ARCH_OMAP4
> help
> - SPI master controller for OMAP24xx/OMAP34xx Multichannel SPI
> + SPI master controller for OMAP24xx/OMAP34xx/OMAP44xx Multichannel SPI
> (McSPI) modules.
>
> config SPI_OMAP_100K
You can simplify this and make it more future proof with something like:
config SPI_OMAP24XX
tristate "McSPI driver for OMAP"
depends on ARCH_OMAP2PLUS
help
SPI master controller for OMAP24XX and later
Regards,
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
