From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 19/19] fbdev: sh-mobile-lcdcfb: Enable the driver on all ARM platforms
Date: Wed, 06 Nov 2013 00:27:30 +0000 [thread overview]
Message-ID: <1671829.6znfm3IPYO@avalon> (raw)
In-Reply-To: <alpine.DEB.2.02.1310312039330.13521@ayla.of.borg>
Hi Geert,
Thank you for the patch.
On Thursday 31 October 2013 20:42:52 Geert Uytterhoeven wrote:
> On Tue, 29 Oct 2013, Laurent Pinchart wrote:
> > Renesas ARM platforms are transitioning from single-platform to
> > multi-platform kernels using the new ARCH_SHMOBILE_MULTI. Make the
> > driver available on all ARM platforms to enable it on both ARCH_SHMOBILE
> > and ARCH_SHMOBILE_MULTI, and increase build testing coverage with
> > COMPILE_TEST.
> >
> > diff --git a/drivers/video/Kconfig b/drivers/video/Kconfig
> > index 84b685f..32b5c86 100644
> > --- a/drivers/video/Kconfig
> > +++ b/drivers/video/Kconfig
> > @@ -2482,7 +2482,7 @@ endif
> >
> > config FB_SH_MOBILE_MERAM
> >
> > tristate "SuperH Mobile MERAM read ahead support"
> >
> > - depends on (SUPERH || ARCH_SHMOBILE)
> > + depends on (SUPERH || ARM || COMPILE_TEST)
> >
> > select GENERIC_ALLOCATOR
> > ---help---
> >
> > Enable MERAM support for the SuperH controller.
>
> While the below compiler warnings have been seen with sh-randconfig
> before, they're more likely to happen with COMPILE_TEST=y.
> I now see them with e.g. m68k-allmodconfig, so I created a patch.
>
> From 15eb69172457c675cde177a6f742b6f1dabdeb18 Mon Sep 17 00:00:00 2001
> From: Geert Uytterhoeven <geert@linux-m68k.org>
> Date: Thu, 31 Oct 2013 20:35:14 +0100
> Subject: [PATCH] fbdev: sh_mobile_meram: Fix defined but not used compiler
> warnings
> MIME-Version: 1.0
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 8bit
>
> If CONFIG_PM_SLEEP resp. CONFIG_PM_RUNTIME are not set:
>
> drivers/video/sh_mobile_meram.c:573: warning: ‘sh_mobile_meram_suspend’
> defined but not used drivers/video/sh_mobile_meram.c:597: warning:
> ‘sh_mobile_meram_resume’ defined but not used
>
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
> ---
> drivers/video/sh_mobile_meram.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/video/sh_mobile_meram.c
> b/drivers/video/sh_mobile_meram.c index e0f098562a74..56a8e47ffceb 100644
> --- a/drivers/video/sh_mobile_meram.c
> +++ b/drivers/video/sh_mobile_meram.c
> @@ -569,6 +569,7 @@ EXPORT_SYMBOL_GPL(sh_mobile_meram_cache_update);
> * Power management
> */
>
> +#ifdef CONFIG_PM_SLEEP
> static int sh_mobile_meram_suspend(struct device *dev)
> {
> struct platform_device *pdev = to_platform_device(dev);
> @@ -592,7 +593,9 @@ static int sh_mobile_meram_suspend(struct device *dev)
> }
> return 0;
> }
> +#endif
>
> +#ifdef CONFIG_PM_RUNTIME
> static int sh_mobile_meram_resume(struct device *dev)
> {
> struct platform_device *pdev = to_platform_device(dev);
> @@ -611,6 +614,7 @@ static int sh_mobile_meram_resume(struct device *dev)
> meram_write_reg(priv->base, common_regs[i], priv->regs[i]);
> return 0;
> }
> +#endif
>
> static UNIVERSAL_DEV_PM_OPS(sh_mobile_meram_dev_pm_ops,
> sh_mobile_meram_suspend,
I'm a bit surprised, looking at the definition of UNIVERSAL_DEV_PM_OPS, I
would have thought that both functions would be used when either
CONFIG_PM_SLEEP or CONFIG_PM_RUNTIME is defined. I would thus have guarded
both functions with #if defined(CONFIG_PM_SLEEP) ||
defined(CONFIG_PM_RUNTIME).
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-11-06 0:27 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1383086274-11049-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
2013-10-29 22:37 ` [PATCH v2 01/19] serial: sh-sci: Enable the driver on all ARM platforms Laurent Pinchart
2014-02-19 20:54 ` Uwe Kleine-König
2014-02-19 22:24 ` Laurent Pinchart
2014-02-20 0:00 ` Uwe Kleine-König
2013-10-29 22:37 ` [PATCH v2 02/19] DMA: shdma: " Laurent Pinchart
2013-10-29 22:37 ` [PATCH v2 03/19] i2c: sh_mobile: " Laurent Pinchart
2013-10-31 11:50 ` Wolfram Sang
2013-10-29 22:37 ` [PATCH v2 04/19] input: sh_keysc: " Laurent Pinchart
2013-10-31 7:54 ` Dmitry Torokhov
2013-10-29 22:37 ` [PATCH v2 05/19] iommu: shmobile: " Laurent Pinchart
2013-11-01 13:43 ` Joerg Roedel
2013-10-29 22:37 ` [PATCH v2 06/19] i2c: rcar: " Laurent Pinchart
2013-10-29 22:37 ` [PATCH v2 07/19] v4l: sh_vou: " Laurent Pinchart
2013-10-29 22:37 ` [PATCH v2 08/19] mmc: sdhi: " Laurent Pinchart
2013-10-30 11:23 ` [PATCH] " Laurent Pinchart
2013-10-30 11:23 ` Laurent Pinchart
2013-10-31 8:26 ` Magnus Damm
2013-10-31 11:59 ` Laurent Pinchart
2013-10-29 22:37 ` [PATCH v2 09/19] mmc: sh_mmcif: " Laurent Pinchart
2013-10-30 11:34 ` [PATCH v3 1/3] mmc: sh_mmcif: Factorize DMA channel request and configuration code Laurent Pinchart
2013-10-30 11:34 ` [PATCH v3 2/3] mmc: sh_mmcif: Fix compilation warning on 64-bit platforms Laurent Pinchart
2013-10-30 11:34 ` [PATCH v3 3/3] mmc: sh_mmcif: Enable the driver on all ARM platforms Laurent Pinchart
2013-10-29 22:37 ` [PATCH v2 10/19] mtd: sh_flctl: " Laurent Pinchart
2013-11-12 23:10 ` Brian Norris
2013-11-12 23:14 ` Laurent Pinchart
2013-11-12 23:17 ` Brian Norris
2013-11-12 23:20 ` Laurent Pinchart
2013-10-29 22:37 ` [PATCH v2 11/19] net: sh_eth: Set receive alignment correctly " Laurent Pinchart
2013-10-29 22:37 ` [PATCH v2 12/19] irda: sh_irda: Enable the driver " Laurent Pinchart
2013-10-29 22:37 ` [PATCH v2 13/19] pinctrl: sh-pfc: " Laurent Pinchart
2013-10-29 22:37 ` [PATCH v2 14/19] pwm: pwm-renesas-tpu: " Laurent Pinchart
2013-10-29 22:37 ` [PATCH v2 15/19] sh: intc: " Laurent Pinchart
2013-10-29 22:37 ` [PATCH v2 16/19] spi: sh_msiof: " Laurent Pinchart
2013-10-29 22:37 ` [PATCH v2 17/19] spi: sh_hspi: " Laurent Pinchart
2013-10-29 22:37 ` [PATCH v2 18/19] thermal: rcar-thermal: " Laurent Pinchart
2013-10-29 22:37 ` [PATCH v2 19/19] fbdev: sh-mobile-lcdcfb: " Laurent Pinchart
2013-10-31 19:42 ` Geert Uytterhoeven
2013-11-06 0:27 ` Laurent Pinchart [this message]
2013-11-06 8:46 ` Geert Uytterhoeven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1671829.6znfm3IPYO@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).