On Wed, Oct 14, 2015 at 5:57 PM, Lars-Peter Clausen <lars@xxxxxxxxxx> 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 devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
