[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdb0joX35HdcSJ=afchMCNVo7i=an3HE4BnK0xA_Gb5YpA@mail.gmail.com>
Date: Mon, 19 Oct 2015 08:55:09 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Lars-Peter Clausen <lars@...afoo.de>
Cc: Sören Brinkmann <soren.brinkmann@...inx.com>,
Zubair Lutfullah Kakakhel <Zubair.Kakakhel@...tec.com>,
Ralf Baechle <ralf@...ux-mips.org>,
Rob Herring <robh+dt@...nel.org>,
Linux MIPS <linux-mips@...ux-mips.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/5] gpio/xilinx: enable for MIPS
On Wed, Oct 14, 2015 at 5:57 PM, Lars-Peter Clausen <lars@...afoo.de> wrote:
> On 10/14/2015 05:18 PM, Sören Brinkmann wrote:
>> On Wed, 2015-10-14 at 01:51PM +0100, Zubair Lutfullah Kakakhel wrote:
>> Hmm, in general, this driver is hopefully generic enough that it doesn't
>> have any real architecture dependencies. And I suspect, we want to
>> enable this driver for ARM64 for ZynqMP soon too. Should we probably
>> drop these arch dependencies completely? It seems to become quite a long list.
>
> I've been thinking about this a while ago. This is certainly not the only
> driver affected by this problem. But the thing is people always complain if
> new symbols become visable in Kconfig that don't apply to their platform.
I don't think it's that important. If people go do down in the GPIO submenu
they are looking at real weird stuff anyways. Please send a patch enabling
this for all rather than coming up with strange config symbols IMO.
Yours,
Linus Walleij
--
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