diff mbox

[PATCH/RFC] dmaengine: sh: Use ARCH_RENESAS

Message ID 1454496934-20672-1-git-send-email-horms+renesas@verge.net.au (mailing list archive)
State Accepted
Headers show

Commit Message

Simon Horman Feb. 3, 2016, 10:55 a.m. UTC
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@verge.net.au>
---
* Based on the next branch of Vinod's slave-dma tree
---
 drivers/dma/sh/Kconfig | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

Comments

Geert Uytterhoeven Feb. 9, 2016, 7:47 p.m. UTC | #1
Hi Simon,

On Wed, Feb 3, 2016 at 11:55 AM, Simon Horman
<horms+renesas@verge.net.au> 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@verge.net.au>

While this patch is correct from a technic point of view...

> ---
> * Based on the next branch of Vinod's slave-dma tree
> ---
>  drivers/dma/sh/Kconfig | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/dma/sh/Kconfig b/drivers/dma/sh/Kconfig
> index f32c430eb16c..6e0685f1a838 100644
> --- a/drivers/dma/sh/Kconfig
> +++ b/drivers/dma/sh/Kconfig
> @@ -12,7 +12,7 @@ config RENESAS_DMA
>
>  config SH_DMAE_BASE
>         bool "Renesas SuperH DMA Engine support"
> -       depends on SUPERH || ARCH_SHMOBILE || COMPILE_TEST
> +       depends on SUPERH || ARCH_RENESAS || COMPILE_TEST

... I'm wondering if we should just drop ARCH_SHMOBILE here.

The only driver for an ARM SoC using this (SH_DMAE_R8A73A4), is not fully
enabled in DT, and probably never will, so I think we can just drop that
driver, too.

Of course all of that can be done later.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

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 dmaengine" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Simon Horman Feb. 10, 2016, 5:11 p.m. UTC | #2
On Tue, Feb 09, 2016 at 08:47:59PM +0100, Geert Uytterhoeven wrote:
> Hi Simon,
> 
> On Wed, Feb 3, 2016 at 11:55 AM, Simon Horman
> <horms+renesas@verge.net.au> 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@verge.net.au>
> 
> While this patch is correct from a technic point of view...
> 
> > ---
> > * Based on the next branch of Vinod's slave-dma tree
> > ---
> >  drivers/dma/sh/Kconfig | 6 +++---
> >  1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/dma/sh/Kconfig b/drivers/dma/sh/Kconfig
> > index f32c430eb16c..6e0685f1a838 100644
> > --- a/drivers/dma/sh/Kconfig
> > +++ b/drivers/dma/sh/Kconfig
> > @@ -12,7 +12,7 @@ config RENESAS_DMA
> >
> >  config SH_DMAE_BASE
> >         bool "Renesas SuperH DMA Engine support"
> > -       depends on SUPERH || ARCH_SHMOBILE || COMPILE_TEST
> > +       depends on SUPERH || ARCH_RENESAS || COMPILE_TEST
> 
> ... I'm wondering if we should just drop ARCH_SHMOBILE here.
> 
> The only driver for an ARM SoC using this (SH_DMAE_R8A73A4), is not fully
> enabled in DT, and probably never will, so I think we can just drop that
> driver, too.
> 
> Of course all of that can be done later.

Sure, given what you have described above dropping ARCH_SHMOBILE is fine by
me. Sorry for not noticing that earlier.
--
To unsubscribe from this list: send the line "unsubscribe dmaengine" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
diff mbox

Patch

diff --git a/drivers/dma/sh/Kconfig b/drivers/dma/sh/Kconfig
index f32c430eb16c..6e0685f1a838 100644
--- a/drivers/dma/sh/Kconfig
+++ b/drivers/dma/sh/Kconfig
@@ -12,7 +12,7 @@  config RENESAS_DMA
 
 config SH_DMAE_BASE
 	bool "Renesas SuperH DMA Engine support"
-	depends on SUPERH || ARCH_SHMOBILE || COMPILE_TEST
+	depends on SUPERH || ARCH_RENESAS || COMPILE_TEST
 	depends on !SUPERH || SH_DMA
 	depends on !SH_DMA_API
 	default y
@@ -41,7 +41,7 @@  endif
 
 config RCAR_DMAC
 	tristate "Renesas R-Car Gen2 DMA Controller"
-	depends on ARCH_SHMOBILE || COMPILE_TEST
+	depends on ARCH_RENESAS || COMPILE_TEST
 	select RENESAS_DMA
 	help
 	  This driver supports the general purpose DMA controller found in the
@@ -49,7 +49,7 @@  config RCAR_DMAC
 
 config RENESAS_USB_DMAC
 	tristate "Renesas USB-DMA Controller"
-	depends on ARCH_SHMOBILE || COMPILE_TEST
+	depends on ARCH_RENESAS || COMPILE_TEST
 	select RENESAS_DMA
 	select DMA_VIRTUAL_CHANNELS
 	help