| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 28 Oct 2014 16:10:26 +0100 From: Linus Walleij <linus.walleij@...aro.org> To: David Cohen <david.a.cohen@...ux.intel.com> Cc: Mika Westerberg <mika.westerberg@...ux.intel.com>, Mathias Nyman <mathias.nyman@...ux.intel.com>, Alexandre Courbot <gnurou@...il.com>, "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [RFC/PATCH] gpio/pinctrl: baytrail: move gpio driver from pinctrl to gpio directory On Fri, Oct 17, 2014 at 3:53 AM, David Cohen <david.a.cohen@...ux.intel.com> wrote: > On Thu, Oct 16, 2014 at 11:01:23AM +0300, Mika Westerberg wrote: >> In an ideal world, yes. However, the reality has shown that BIOS/FW gets >> these wrong and we need to work it around in the OS. > > But we never upstream these workarounds, right? :) Unless you discover it after it hits the market, right? I think this driver is just fine exactly where it is. Besides, the driver is fully aware of all its pins, and just look at all the pull up etc information displayed by byt_gpio_dbg_show(), it doesn't get more pin control than that even if you don't implement the pin control API. 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