From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] backlight: add PWM dependencies
Date: Mon, 10 Feb 2014 11:40:34 +0100 [thread overview]
Message-ID: <20140210104032.GB20143@ulmo.nvidia.com> (raw)
In-Reply-To: <1391518634-6472-1-git-send-email-linus.walleij@linaro.org>
On Tue, Feb 04, 2014 at 01:57:14PM +0100, Linus Walleij wrote:
> In some compilations the LM3630A and LP855X backlight drivers
> fail like this:
>
> drivers/built-in.o: In function `lm3630a_pwm_ctrl':
> drivers/video/backlight/lm3630a_bl.c:168: undefined reference to `pwm_config'
> drivers/video/backlight/lm3630a_bl.c:172: undefined reference to `pwm_disable'
> drivers/video/backlight/lm3630a_bl.c:170: undefined reference to `pwm_enable'
> drivers/built-in.o: In function `lp855x_pwm_ctrl':
> drivers/video/backlight/lp855x_bl.c:249: undefined reference to `pwm_config'
> drivers/video/backlight/lp855x_bl.c:253: undefined reference to `pwm_disable'
> drivers/video/backlight/lp855x_bl.c:251: undefined reference to `pwm_enable'
>
> This is because both drivers depend on the PWM framework, so
> add this dependency to their Kconfig entries.
>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> drivers/video/backlight/Kconfig | 2 ++
> 1 file changed, 2 insertions(+)
Hi Linus,
it seems like at least BACKLIGHT_LP8788 is missing a corresponding
dependency as well.
I have applied Sascha's patch to remove the obsolete HAVE_PWM symbol,
and this will fix at least the build issues. However it will also cause
the driver to fail at runtime because the pwm_*() functions won't work.
So I wonder if we should still apply this patch to make it clear that
PWM support is necessary to make the driver work. I guess the point is
somewhat moot because even if we had PWM enabled it could still happen
that no PWM driver is enabled to provide a PWM device... I guess it's
equally justifiable to leave that up to the defconfig.
Should we just drop this patch? Cc'ing Arnd who's commented on Jingoo's
alternate proposal.
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140210/1b95b04c/attachment.sig>
next prev parent reply other threads:[~2014-02-10 10:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 12:57 [PATCH] backlight: add PWM dependencies Linus Walleij
2014-02-05 5:01 ` Jingoo Han
2014-02-05 8:57 ` Linus Walleij
2014-02-06 6:49 ` Jingoo Han
2014-02-06 7:23 ` Jingoo Han
2014-02-06 8:32 ` Linus Walleij
2014-02-06 16:08 ` Arnd Bergmann
2014-02-06 16:35 ` Arnd Bergmann
2014-02-07 3:05 ` Jingoo Han
2014-02-07 9:40 ` Arnd Bergmann
2014-02-10 10:40 ` Thierry Reding [this message]
2014-02-10 11:09 ` Linus Walleij
2014-02-26 13:25 ` Thierry Reding
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=20140210104032.GB20143@ulmo.nvidia.com \
--to=thierry.reding@gmail.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).