[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20140226132529.GC29779@ulmo.nvidia.com>
Date: Wed, 26 Feb 2014 14:25:30 +0100
From: Thierry Reding <thierry.reding@...il.com>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: Jingoo Han <jg1.han@...sung.com>, Arnd Bergmann <arnd@...db.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-pwm@...r.kernel.org" <linux-pwm@...r.kernel.org>
Subject: Re: [PATCH] backlight: add PWM dependencies
On Mon, Feb 10, 2014 at 12:09:29PM +0100, Linus Walleij wrote:
> On Mon, Feb 10, 2014 at 11:40 AM, Thierry Reding
> <thierry.reding@...il.com> wrote:
>
> > 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 it definately needs that API, not just stubs.
>
> But isn't it proper for Kconfig to allow you to break things
> like that by configuring out stuff and have stubs come in?
>
> I'm a bit torn here.
After thinking about this some more, I've come to the conclusion that
the drivers should have the dependency. Kconfig should make sure that
the resulting drivers work.
If somebody wanted to knowingly build this driver with a configuration
that won't work at runtime, then they should be using COMPILE_TEST
instead.
So I'm leaning towards applying this patch if there are no objections.
Thierry
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists