From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
Cc: linux-fbdev@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/2] OMAPDSS: panel-dvi: Add Kconfig dependency on I2C
Date: Wed, 29 Feb 2012 10:21:42 +0000 [thread overview]
Message-ID: <1330510902.1934.76.camel@deskari> (raw)
In-Reply-To: <4F4DF801.3000905@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 2059 bytes --]
On Wed, 2012-02-29 at 10:03 +0000, Florian Tobias Schandinat wrote:
> On 02/29/2012 08:48 AM, Tomi Valkeinen wrote:
> > panel-dvi uses i2c, but the Kconfig didn't have dependency on I2C. Add
> > it.
> >
> > Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
> > ---
> > drivers/video/omap2/displays/Kconfig | 2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/drivers/video/omap2/displays/Kconfig b/drivers/video/omap2/displays/Kconfig
> > index 74d29b5..408a992 100644
> > --- a/drivers/video/omap2/displays/Kconfig
> > +++ b/drivers/video/omap2/displays/Kconfig
> > @@ -12,7 +12,7 @@ config PANEL_GENERIC_DPI
> >
> > config PANEL_DVI
> > tristate "DVI output"
> > - depends on OMAP2_DSS_DPI
> > + depends on OMAP2_DSS_DPI && I2C
>
> It's just a matter of taste, but are you sure you want to "depend" on it and not
> "select" it? Other drivers tend to use select for I2C, for me it doesn't really
> matter.
Well, I'd like to "select", but I don't think that's correct. From
Documentation/kbuild/kconfig-language.txt:
In general use select only for non-visible symbols
(no prompts anywhere) and for symbols with no dependencies.
But I do see quite many selects for I2C, so I'm not sure if all those
are wrong, or has it just been decided that I2C is a valid target for
select.
Using depend is in line with the other panel drivers in the same
directory. I've been thinking about the same thing from time to time,
and I'd rather select I2C, SPI and BACKLIGHT_CLASS_DEVICE than use
depend.
But, for example, using select to BACKLIGHT_CLASS_DEVICE is broken: if I
change a panel driver to select BACKLIGHT_CLASS_DEVICE, but then I
manually disable CONFIG_BACKLIGHT_LCD_SUPPORT (which the
BACKLIGHT_CLASS_DEVICE depends on) from the kernel config, this leads to
BACKLIGHT_CLASS_DEVICE being enabled, but CONFIG_BACKLIGHT_LCD_SUPPORT
being disabled, which is clearly broken.
So... As I see it, depending is a bit awkward, but it's correct.
Tomi
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-02-29 10:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 8:48 [PATCH 0/2] OMAPDSS: small fixes for 3.3 rc Tomi Valkeinen
2012-02-29 8:48 ` [PATCH 1/2] OMAPDSS: panel-dvi: Add Kconfig dependency on I2C Tomi Valkeinen
2012-02-29 10:03 ` Florian Tobias Schandinat
2012-02-29 10:21 ` Tomi Valkeinen [this message]
2012-02-29 11:10 ` Florian Tobias Schandinat
2012-02-29 8:48 ` [PATCH 2/2] OMAPDSS: APPLY: make ovl_enable/disable synchronous Tomi Valkeinen
2012-02-29 10:13 ` Florian Tobias Schandinat
2012-02-29 10:30 ` Tomi Valkeinen
2012-02-29 10:48 ` Florian Tobias Schandinat
2012-02-29 14:52 ` Rob Clark
2012-02-29 9:56 ` [PATCH 0/2] OMAPDSS: small fixes for 3.3 rc Florian Tobias Schandinat
2012-03-01 5:38 ` Florian Tobias Schandinat
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=1330510902.1934.76.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=FlorianSchandinat@gmx.de \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-omap@vger.kernel.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).