diff mbox

[07/15] mmc: sdhi: Enable driver compilation with COMPILE_TEST

Message ID 1385515117-23664-8-git-send-email-laurent.pinchart+renesas@ideasonboard.com (mailing list archive)
State New, archived
Headers show

Commit Message

Laurent Pinchart Nov. 27, 2013, 1:18 a.m. UTC 
This helps increasing build testing coverage.

The driver doesn't compile on (at least) x86 due (possibly among others)
to missing readsw/writesw I/O accessors, restrict compilation to SUPERH
or ARM.

Whether the CTL_DMA_ENABLE register is part of the standard TMIO
controller or is Renesas-specific is unknown and impossible to test as
we have no current or planned TMIO DMA users other than SUPERH and
ARCH_SHMOBILE. Writing to the register is thus conditionally compiled
for SUPERH and ARCH_SHMOBILE only. Adding ARCH_SHMOBILE_MULTI to the
list would extend this to multiarch kernels, but would break the driver
for non-shmobile platforms if the register is Renesas-specific. We can
thus get rid of the conditional compilation completely without
introducing any further issue, and let future non-Renesas users deal
with the situation if it turns out to be a the problem.

Cc: Chris Ball <cjb@laptop.org>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Ian Molton <ian@mnementh.co.uk>
Cc: linux-mmc@vger.kernel.org
Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Acked-by: Simon Horman <horms@verge.net.au>
---
 drivers/mmc/host/Kconfig | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

Comments

Laurent Pinchart Dec. 11, 2013, 12:53 p.m. UTC | #1 
Hi Chris,

Could you please pick this patch (and patch 08/15 in the same series) up for 
v3.14 ?

On Wednesday 27 November 2013 02:18:29 Laurent Pinchart wrote:
> This helps increasing build testing coverage.
> 
> The driver doesn't compile on (at least) x86 due (possibly among others)
> to missing readsw/writesw I/O accessors, restrict compilation to SUPERH
> or ARM.
> 
> Whether the CTL_DMA_ENABLE register is part of the standard TMIO
> controller or is Renesas-specific is unknown and impossible to test as
> we have no current or planned TMIO DMA users other than SUPERH and
> ARCH_SHMOBILE. Writing to the register is thus conditionally compiled
> for SUPERH and ARCH_SHMOBILE only. Adding ARCH_SHMOBILE_MULTI to the
> list would extend this to multiarch kernels, but would break the driver
> for non-shmobile platforms if the register is Renesas-specific. We can
> thus get rid of the conditional compilation completely without
> introducing any further issue, and let future non-Renesas users deal
> with the situation if it turns out to be a the problem.
> 
> Cc: Chris Ball <cjb@laptop.org>
> Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
> Cc: Ian Molton <ian@mnementh.co.uk>
> Cc: linux-mmc@vger.kernel.org
> Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
> Acked-by: Simon Horman <horms@verge.net.au>
> ---
>  drivers/mmc/host/Kconfig | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/mmc/host/Kconfig b/drivers/mmc/host/Kconfig
> index 7fc5099..ca1315e 100644
> --- a/drivers/mmc/host/Kconfig
> +++ b/drivers/mmc/host/Kconfig
> @@ -479,7 +479,8 @@ config MMC_TMIO
> 
>  config MMC_SDHI
>  	tristate "SH-Mobile SDHI SD/SDIO controller support"
> -	depends on SUPERH || ARCH_SHMOBILE
> +	depends on SUPERH || ARM
> +	depends on SUPERH || ARCH_SHMOBILE || COMPILE_TEST
>  	select MMC_TMIO_CORE
>  	help
>  	  This provides support for the SDHI SD/SDIO controller found in
Sergei Shtylyov Dec. 11, 2013, 6:01 p.m. UTC | #2 
Hello.

On 27-11-2013 5:18, Laurent Pinchart wrote:

> This helps increasing build testing coverage.

> The driver doesn't compile on (at least) x86 due (possibly among others)
> to missing readsw/writesw I/O accessors, restrict compilation to SUPERH
> or ARM.

> Whether the CTL_DMA_ENABLE register is part of the standard TMIO
> controller or is Renesas-specific is unknown and impossible to test as
> we have no current or planned TMIO DMA users other than SUPERH and
> ARCH_SHMOBILE. Writing to the register is thus conditionally compiled
> for SUPERH and ARCH_SHMOBILE only. Adding ARCH_SHMOBILE_MULTI to the
> list would extend this to multiarch kernels, but would break the driver
> for non-shmobile platforms if the register is Renesas-specific. We can
> thus get rid of the conditional compilation completely without
> introducing any further issue, and let future non-Renesas users deal
> with the situation if it turns out to be a the problem.

> Cc: Chris Ball <cjb@laptop.org>
> Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
> Cc: Ian Molton <ian@mnementh.co.uk>
> Cc: linux-mmc@vger.kernel.org
> Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
> Acked-by: Simon Horman <horms@verge.net.au>
> ---
>   drivers/mmc/host/Kconfig | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)

> diff --git a/drivers/mmc/host/Kconfig b/drivers/mmc/host/Kconfig
> index 7fc5099..ca1315e 100644
> --- a/drivers/mmc/host/Kconfig
> +++ b/drivers/mmc/host/Kconfig
> @@ -479,7 +479,8 @@ config MMC_TMIO
>
>   config MMC_SDHI
>   	tristate "SH-Mobile SDHI SD/SDIO controller support"
> -	depends on SUPERH || ARCH_SHMOBILE
> +	depends on SUPERH || ARM
> +	depends on SUPERH || ARCH_SHMOBILE || COMPILE_TEST

    Hm, why 2 "depends" lines with SUPERH in both?

WBR, Sergei
Laurent Pinchart Dec. 11, 2013, 6:06 p.m. UTC | #3 
On Wednesday 11 December 2013 22:01:53 Sergei Shtylyov wrote:
> Hello.
> 
> On 27-11-2013 5:18, Laurent Pinchart wrote:
> > This helps increasing build testing coverage.
> > 
> > The driver doesn't compile on (at least) x86 due (possibly among others)
> > to missing readsw/writesw I/O accessors, restrict compilation to SUPERH
> > or ARM.
> > 
> > Whether the CTL_DMA_ENABLE register is part of the standard TMIO
> > controller or is Renesas-specific is unknown and impossible to test as
> > we have no current or planned TMIO DMA users other than SUPERH and
> > ARCH_SHMOBILE. Writing to the register is thus conditionally compiled
> > for SUPERH and ARCH_SHMOBILE only. Adding ARCH_SHMOBILE_MULTI to the
> > list would extend this to multiarch kernels, but would break the driver
> > for non-shmobile platforms if the register is Renesas-specific. We can
> > thus get rid of the conditional compilation completely without
> > introducing any further issue, and let future non-Renesas users deal
> > with the situation if it turns out to be a the problem.
> > 
> > Cc: Chris Ball <cjb@laptop.org>
> > Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
> > Cc: Ian Molton <ian@mnementh.co.uk>
> > Cc: linux-mmc@vger.kernel.org
> > Signed-off-by: Laurent Pinchart
> > <laurent.pinchart+renesas@ideasonboard.com>
> > Acked-by: Simon Horman <horms@verge.net.au>
> > ---
> > 
> >   drivers/mmc/host/Kconfig | 3 ++-
> >   1 file changed, 2 insertions(+), 1 deletion(-)
> > 
> > diff --git a/drivers/mmc/host/Kconfig b/drivers/mmc/host/Kconfig
> > index 7fc5099..ca1315e 100644
> > --- a/drivers/mmc/host/Kconfig
> > +++ b/drivers/mmc/host/Kconfig
> > @@ -479,7 +479,8 @@ config MMC_TMIO
> > 
> >   config MMC_SDHI
> >   
> >   	tristate "SH-Mobile SDHI SD/SDIO controller support"
> > 
> > -	depends on SUPERH || ARCH_SHMOBILE
> > +	depends on SUPERH || ARM
> > +	depends on SUPERH || ARCH_SHMOBILE || COMPILE_TEST
> 
>     Hm, why 2 "depends" lines with SUPERH in both?

The first line means "this driver requires SUPERH || ARM to be compiled", 
while the second line means "devices supported by this driver are only found 
on SUPERH || ARCH_SHMOBILE platforms".
Sergei Shtylyov Dec. 11, 2013, 6:22 p.m. UTC | #4 
On 11-12-2013 22:06, Laurent Pinchart wrote:

>>> This helps increasing build testing coverage.

>>> The driver doesn't compile on (at least) x86 due (possibly among others)
>>> to missing readsw/writesw I/O accessors, restrict compilation to SUPERH
>>> or ARM.

>>> Whether the CTL_DMA_ENABLE register is part of the standard TMIO
>>> controller or is Renesas-specific is unknown and impossible to test as
>>> we have no current or planned TMIO DMA users other than SUPERH and
>>> ARCH_SHMOBILE. Writing to the register is thus conditionally compiled
>>> for SUPERH and ARCH_SHMOBILE only. Adding ARCH_SHMOBILE_MULTI to the
>>> list would extend this to multiarch kernels, but would break the driver
>>> for non-shmobile platforms if the register is Renesas-specific. We can
>>> thus get rid of the conditional compilation completely without
>>> introducing any further issue, and let future non-Renesas users deal
>>> with the situation if it turns out to be a the problem.

>>> Cc: Chris Ball <cjb@laptop.org>
>>> Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
>>> Cc: Ian Molton <ian@mnementh.co.uk>
>>> Cc: linux-mmc@vger.kernel.org
>>> Signed-off-by: Laurent Pinchart
>>> <laurent.pinchart+renesas@ideasonboard.com>
>>> Acked-by: Simon Horman <horms@verge.net.au>
[...]

>>> diff --git a/drivers/mmc/host/Kconfig b/drivers/mmc/host/Kconfig
>>> index 7fc5099..ca1315e 100644
>>> --- a/drivers/mmc/host/Kconfig
>>> +++ b/drivers/mmc/host/Kconfig
>>> @@ -479,7 +479,8 @@ config MMC_TMIO
>>>
>>>    config MMC_SDHI
>>>
>>>    	tristate "SH-Mobile SDHI SD/SDIO controller support"
>>>
>>> -	depends on SUPERH || ARCH_SHMOBILE
>>> +	depends on SUPERH || ARM
>>> +	depends on SUPERH || ARCH_SHMOBILE || COMPILE_TEST

>>      Hm, why 2 "depends" lines with SUPERH in both?

> The first line means "this driver requires SUPERH || ARM to be compiled",

    Then COMPILE_TEST should be there, no?

> while the second line means "devices supported by this driver are only found
> on SUPERH || ARCH_SHMOBILE platforms".

WBR, Sergei
Laurent Pinchart Dec. 11, 2013, 11:05 p.m. UTC | #5 
Hi Sergei,

On Wednesday 11 December 2013 22:22:19 Sergei Shtylyov wrote:
> On 11-12-2013 22:06, Laurent Pinchart wrote:
> >>> This helps increasing build testing coverage.
> >>> 
> >>> The driver doesn't compile on (at least) x86 due (possibly among others)
> >>> to missing readsw/writesw I/O accessors, restrict compilation to SUPERH
> >>> or ARM.
> >>> 
> >>> Whether the CTL_DMA_ENABLE register is part of the standard TMIO
> >>> controller or is Renesas-specific is unknown and impossible to test as
> >>> we have no current or planned TMIO DMA users other than SUPERH and
> >>> ARCH_SHMOBILE. Writing to the register is thus conditionally compiled
> >>> for SUPERH and ARCH_SHMOBILE only. Adding ARCH_SHMOBILE_MULTI to the
> >>> list would extend this to multiarch kernels, but would break the driver
> >>> for non-shmobile platforms if the register is Renesas-specific. We can
> >>> thus get rid of the conditional compilation completely without
> >>> introducing any further issue, and let future non-Renesas users deal
> >>> with the situation if it turns out to be a the problem.
> >>> 
> >>> Cc: Chris Ball <cjb@laptop.org>
> >>> Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
> >>> Cc: Ian Molton <ian@mnementh.co.uk>
> >>> Cc: linux-mmc@vger.kernel.org
> >>> Signed-off-by: Laurent Pinchart
> >>> <laurent.pinchart+renesas@ideasonboard.com>
> >>> Acked-by: Simon Horman <horms@verge.net.au>
> 
> [...]
> 
> >>> diff --git a/drivers/mmc/host/Kconfig b/drivers/mmc/host/Kconfig
> >>> index 7fc5099..ca1315e 100644
> >>> --- a/drivers/mmc/host/Kconfig
> >>> +++ b/drivers/mmc/host/Kconfig
> >>> @@ -479,7 +479,8 @@ config MMC_TMIO
> >>> 
> >>>    config MMC_SDHI
> >>>    	tristate "SH-Mobile SDHI SD/SDIO controller support"
> >>> -	depends on SUPERH || ARCH_SHMOBILE
> >>> +	depends on SUPERH || ARM
> >>> +	depends on SUPERH || ARCH_SHMOBILE || COMPILE_TEST
> >>> 
> >>      Hm, why 2 "depends" lines with SUPERH in both?
> > 
> > The first line means "this driver requires SUPERH || ARM to be compiled",
> 
>     Then COMPILE_TEST should be there, no?

No, because the first line says that the driver is known *not* to compile on 
platforms other than ARM and SUPERH. Adding || COMPILE_TEST there would break 
compilation with allyesconfig and randconfig on those other platforms.

Stated differently, the first line restricts the driver from being compiled on 
architectures where it doesn't compile, regardless of COMPILE_TEST, and the 
second line restricts it to platform where hardware is known to exists, with 
COMPILE_TEST to optionally extend build coverage.

> > while the second line means "devices supported by this driver are only
> > found on SUPERH || ARCH_SHMOBILE platforms".
Laurent Pinchart Jan. 7, 2014, 3:10 p.m. UTC | #6 
Hi Chris,

On Wednesday 11 December 2013 13:53:21 Laurent Pinchart wrote:
> Hi Chris,
> 
> Could you please pick this patch (and patch 08/15 in the same series) up for
> v3.14 ?

Ping ?

> On Wednesday 27 November 2013 02:18:29 Laurent Pinchart wrote:
> > This helps increasing build testing coverage.
> > 
> > The driver doesn't compile on (at least) x86 due (possibly among others)
> > to missing readsw/writesw I/O accessors, restrict compilation to SUPERH
> > or ARM.
> > 
> > Whether the CTL_DMA_ENABLE register is part of the standard TMIO
> > controller or is Renesas-specific is unknown and impossible to test as
> > we have no current or planned TMIO DMA users other than SUPERH and
> > ARCH_SHMOBILE. Writing to the register is thus conditionally compiled
> > for SUPERH and ARCH_SHMOBILE only. Adding ARCH_SHMOBILE_MULTI to the
> > list would extend this to multiarch kernels, but would break the driver
> > for non-shmobile platforms if the register is Renesas-specific. We can
> > thus get rid of the conditional compilation completely without
> > introducing any further issue, and let future non-Renesas users deal
> > with the situation if it turns out to be a the problem.
> > 
> > Cc: Chris Ball <cjb@laptop.org>
> > Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
> > Cc: Ian Molton <ian@mnementh.co.uk>
> > Cc: linux-mmc@vger.kernel.org
> > Signed-off-by: Laurent Pinchart
> > <laurent.pinchart+renesas@ideasonboard.com>
> > Acked-by: Simon Horman <horms@verge.net.au>
> > ---
> > 
> >  drivers/mmc/host/Kconfig | 3 ++-
> >  1 file changed, 2 insertions(+), 1 deletion(-)
> > 
> > diff --git a/drivers/mmc/host/Kconfig b/drivers/mmc/host/Kconfig
> > index 7fc5099..ca1315e 100644
> > --- a/drivers/mmc/host/Kconfig
> > +++ b/drivers/mmc/host/Kconfig
> > @@ -479,7 +479,8 @@ config MMC_TMIO
> > 
> >  config MMC_SDHI
> >  
> >  	tristate "SH-Mobile SDHI SD/SDIO controller support"
> > 
> > -	depends on SUPERH || ARCH_SHMOBILE
> > +	depends on SUPERH || ARM
> > +	depends on SUPERH || ARCH_SHMOBILE || COMPILE_TEST
> > 
> >  	select MMC_TMIO_CORE
> >  	help
> >  	
> >  	  This provides support for the SDHI SD/SDIO controller found in
Chris Ball Jan. 7, 2014, 3:50 p.m. UTC | #7 
Hi Laurent,

On Tue, Jan 07 2014, Laurent Pinchart wrote:
> Hi Chris,
>
> On Wednesday 11 December 2013 13:53:21 Laurent Pinchart wrote:
>> Hi Chris,
>> 
>> Could you please pick this patch (and patch 08/15 in the same series) up for
>> v3.14 ?
>
> Ping ?

Thanks, both pushed to mmc-next for 3.14, sorry for the delay.

- Chris.
Laurent Pinchart Jan. 7, 2014, 4:13 p.m. UTC | #8 
On Tuesday 07 January 2014 15:50:45 Chris Ball wrote:
> On Tue, Jan 07 2014, Laurent Pinchart wrote:
> > On Wednesday 11 December 2013 13:53:21 Laurent Pinchart wrote:
> >> Hi Chris,
> >> 
> >> Could you please pick this patch (and patch 08/15 in the same series) up
> >> for v3.14 ?
> > 
> > Ping ?
> 
> Thanks, both pushed to mmc-next for 3.14, sorry for the delay.

No worries, thank you.
diff mbox

Patch

diff --git a/drivers/mmc/host/Kconfig b/drivers/mmc/host/Kconfig
index 7fc5099..ca1315e 100644
--- a/drivers/mmc/host/Kconfig
+++ b/drivers/mmc/host/Kconfig
@@ -479,7 +479,8 @@  config MMC_TMIO
 
 config MMC_SDHI
 	tristate "SH-Mobile SDHI SD/SDIO controller support"
-	depends on SUPERH || ARCH_SHMOBILE
+	depends on SUPERH || ARM
+	depends on SUPERH || ARCH_SHMOBILE || COMPILE_TEST
 	select MMC_TMIO_CORE
 	help
 	  This provides support for the SDHI SD/SDIO controller found in