From: linux@prisktech.co.nz (Tony Prisk)
To: linux-arm-kernel@lists.infradead.org
Subject: PWM backlight build warning
Date: Sun, 07 Apr 2013 06:33:35 +1200 [thread overview]
Message-ID: <51606A7F.3050803@prisktech.co.nz> (raw)
Hi Thierry,
Sorry it's taken so long to report this but I've been tied up with other
patches recently. I noticed a build warning on the pwm_bl driver in
3.9-rcX but I'm not sure what the correct resolution would be. This patch:
commit e2c17bc6f717a8847df2a867caec6ba4fe85f3fc
backlight: convert pwm_bl to dev_pm_ops
Should be no functional changes, mainly a reorganisation to support
future work.
[akpm at linux-foundation.org: fix CONFIG_PM=n build]
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Richard Purdie <rpurdie@rpsys.net>
Cc: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
has introduced a two build warnings in my config:
drivers/video/backlight/pwm_bl.c:278:12: warning:
?pwm_backlight_suspend? defined but not used [-Wunused-function]
drivers/video/backlight/pwm_bl.c:292:12: warning: ?pwm_backlight_resume?
defined but not used [-Wunused-function]
Although I noticed it doesn't have your acked-by ;)
Selecting "Run-time PM core functionality" without "Suspend to RAM and
standby" causes the unused function warning.
With CONFIG_PM=n, no warnings. With CONFIG_PM=y and CONFIG_PM_SLEEP=y,
no warnings.
The problem occurs because when CONFIG_PM=y but CONFIG_PM_SLEEP=n:
#define SIMPLE_DEV_PM_OPS(name, suspend_fn, resume_fn) \
const struct dev_pm_ops name = { \
SET_SYSTEM_SLEEP_PM_OPS(syspend_fn, resume_fn) \
}
#ifdef CONFIG_PM_SLEEP
#define SET_SYSTEM_SLEEP_PM_OPS(suspend_fn, resume_fn) \
.suspend = suspend_fn, \
.resume = resume_fn, \
.freeze = suspend_fn, \
.thaw = resume_fn, \
.poweroff = suspend_fn, \
.restore = resume_fn,
#else
#define SET_SYSTEM_SLEEP_PM_OPS(suspend_fn, resume_fn)
#endif
I guess this would be a problem on every driver that has been converted
to SIMPLE_DEV_PM_OPS.
I don't know enough about the PM code to offer a fix, or whethermy
chosen config is just 'invalid'.
Regards
Tony P
next reply other threads:[~2013-04-06 18:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-06 18:33 Tony Prisk [this message]
2013-04-06 20:02 ` PWM backlight build warning Mark Brown
2013-04-06 21:10 ` Thierry Reding
2013-04-06 22:06 ` Tony Prisk
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=51606A7F.3050803@prisktech.co.nz \
--to=linux@prisktech.co.nz \
--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