On Wed, Feb 24, 2016 at 08:46:31AM +0100, Geert Uytterhoeven wrote:
> Hi Simon,
>
> On Wed, Feb 24, 2016 at 3:22 AM, Simon Horman
> <horms+renesas@xxxxxxxxxxxx> wrote:
> > Make use of ARCH_RENESAS in place of ARCH_SHMOBILE.
> >
> > This is part of an ongoing process to migrate from ARCH_SHMOBILE to
> > ARCH_RENESAS the motivation for which being that RENESAS seems to be a more
> > appropriate name than SHMOBILE for the majority of Renesas ARM based SoCs.
> >
> > Signed-off-by: Simon Horman <horms+renesas@xxxxxxxxxxxx>
> > ---
> > drivers/media/platform/Kconfig | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > Based on media_tree/master
> >
> > diff --git a/drivers/media/platform/Kconfig b/drivers/media/platform/Kconfig
> > index 201f5c296a95..662c029400de 100644
> > --- a/drivers/media/platform/Kconfig
> > +++ b/drivers/media/platform/Kconfig
> > @@ -37,7 +37,7 @@ config VIDEO_SH_VOU
> > tristate "SuperH VOU video output driver"
> > depends on MEDIA_CAMERA_SUPPORT
> > depends on VIDEO_DEV && I2C && HAS_DMA
> > - depends on ARCH_SHMOBILE || COMPILE_TEST
> > + depends on ARCH_RENESAS || COMPILE_TEST
>
> This driver is used on sh7722/sh7723/sh7724 only.
> While these are Renesas parts, ARCH_RENESAS isn't set for SuperH SoCs,
> making this driver unavailable where needed.
Thanks for pointing that out, I had missed that detail.
Ideally I would like to stop setting ARCH_SHMOBILE for ARM Based
SoCs. So perhaps the following would be best?
depends on ARCH_SHMOBILE || ARCH_RENESAS || COMPILE_TEST
> > select VIDEOBUF2_DMA_CONTIG
> > help
> > Support for the Video Output Unit (VOU) on SuperH SoCs.
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
