From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Dave Jones <davej@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-omap <linux-omap@vger.kernel.org>,
linux-fbdev <linux-fbdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Florian Tobias Schandinat <FlorianSchandinat@gmx.de>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Felipe Balbi <balbi@ti.com>, Evgeniy Polyakov <zbr@ioremap.net>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [GIT PULL] fbdev changes for 3.8
Date: Mon, 17 Dec 2012 09:03:39 +0000 [thread overview]
Message-ID: <50CEDFEB.2030600@ti.com> (raw)
In-Reply-To: <20121216203536.GR4989@atomide.com>
[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]
On 2012-12-16 22:35, Tony Lindgren wrote:
>> Those are all omap internal devices and should be all marked with
>> depends on ARCH_OMAP2PLUS.
>>
>> It's a different story for external devices that may be used on other
>> architectures.
>>
>> I only came up with one reason to compile internal devices for other
>> architectures: In some cases the driver subsystem maintainer may want to
>> be able to compile test subsystem wide changes without having to compile
>> for each target separately. But for those cases it's trivial to carry a
>> compile test patch that just drops the depends Kconfig entries.
>
> And here's a patch to limit the omap drivers above to omap only.
The patch looks good to me.
The reason I removed the OMAP dependency from OMAP DSS was not (only)
because of the compile testing, but also because I thought it was right:
a driver for an IP block shouldn't presume that the IP is used only on
particular SoC.
But perhaps that's a bit too academic approach for an IP that's in real
world only used for OMAP.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Dave Jones <davej@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-omap <linux-omap@vger.kernel.org>,
linux-fbdev <linux-fbdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Florian Tobias Schandinat <FlorianSchandinat@gmx.de>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Felipe Balbi <balbi@ti.com>, Evgeniy Polyakov <zbr@ioremap.net>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [GIT PULL] fbdev changes for 3.8
Date: Mon, 17 Dec 2012 11:03:39 +0200 [thread overview]
Message-ID: <50CEDFEB.2030600@ti.com> (raw)
In-Reply-To: <20121216203536.GR4989@atomide.com>
[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]
On 2012-12-16 22:35, Tony Lindgren wrote:
>> Those are all omap internal devices and should be all marked with
>> depends on ARCH_OMAP2PLUS.
>>
>> It's a different story for external devices that may be used on other
>> architectures.
>>
>> I only came up with one reason to compile internal devices for other
>> architectures: In some cases the driver subsystem maintainer may want to
>> be able to compile test subsystem wide changes without having to compile
>> for each target separately. But for those cases it's trivial to carry a
>> compile test patch that just drops the depends Kconfig entries.
>
> And here's a patch to limit the omap drivers above to omap only.
The patch looks good to me.
The reason I removed the OMAP dependency from OMAP DSS was not (only)
because of the compile testing, but also because I thought it was right:
a driver for an IP block shouldn't presume that the IP is used only on
particular SoC.
But perhaps that's a bit too academic approach for an IP that's in real
world only used for OMAP.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]
next prev parent reply other threads:[~2012-12-17 9:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 10:22 [GIT PULL] fbdev changes for 3.8 Tomi Valkeinen
2012-12-14 10:22 ` Tomi Valkeinen
2012-12-15 21:11 ` Linus Torvalds
2012-12-15 21:11 ` Linus Torvalds
2012-12-15 22:24 ` Dave Jones
2012-12-15 22:24 ` Dave Jones
2012-12-16 17:46 ` Tony Lindgren
2012-12-16 17:46 ` Tony Lindgren
2012-12-16 20:35 ` Tony Lindgren
2012-12-16 20:35 ` Tony Lindgren
2012-12-17 6:00 ` Dmitry Torokhov
2012-12-17 6:00 ` Dmitry Torokhov
2012-12-17 18:29 ` Tony Lindgren
2012-12-17 18:29 ` Tony Lindgren
2012-12-17 9:03 ` Tomi Valkeinen [this message]
2012-12-17 9:03 ` Tomi Valkeinen
2012-12-17 10:05 ` Felipe Balbi
2012-12-17 10:05 ` Felipe Balbi
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=50CEDFEB.2030600@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=FlorianSchandinat@gmx.de \
--cc=arnd@arndb.de \
--cc=balbi@ti.com \
--cc=davej@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
--cc=torvalds@linux-foundation.org \
--cc=zbr@ioremap.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.