[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3950519.8yj1SQodNQ@wuerfel>
Date: Tue, 28 May 2013 16:52:55 +0200
From: Arnd Bergmann <arnd@...db.de>
To: linux-arm-kernel@...ts.infradead.org
Cc: Pawel Moll <pawel.moll@....com>,
Linus Walleij <linus.walleij@...aro.org>,
"linux@....linux.org.uk ARM Linux" <linux@....linux.org.uk>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"fabian@...ter-vogt.de Vogt" <fabian@...ter-vogt.de>,
Daniel Tang <dt.tangr@...il.com>,
Lionel Debroux <lionel_debroux@...oo.fr>
Subject: Re: [RFC PATCHv4 0/6] arm: Initial TI-Nspire support
On Tuesday 28 May 2013 15:21:04 Pawel Moll wrote:
> On Tue, 2013-05-28 at 15:16 +0100, Linus Walleij wrote:
> > On Tue, May 28, 2013 at 12:54 PM, Pawel Moll <pawel.moll@....com> wrote:
> > > On Mon, 2013-05-27 at 11:32 +0100, Arnd Bergmann wrote:
> > >> b) add a new KMS driver for this hardware that can be used as an
> > >> alternative to the existing one and that works with DT.
> > >
> > > There are people working on this, just trying to jump through some legal
> > > hoops to post a RFC. Once this is done we'll be in an interesting
> > > position of two amba_bus drivers "competing" for the same amba_bus
> > > device, which I'm not sure how to deal with right now...
> >
> > Make them mutually exclusive in Kconfig?
>
> Certainly an option.
>
> I wouldn't mind having both compiled as modules and loading one or the
> other, but it wouldn't fly with "=y"...
It's a bit ugly but I think you can express that in Kconfig like this:
config FB_ARMCLCD
tristate "ARM PrimeCell PL110 support"
depends on FB && ARM && ARM_AMBA
depends on KMS_ARMCLCD != 'y'
depends on 'm' if KMS_ARMCLCD
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists