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: Sat, 11 Nov 2006 17:27:04 -0800 From: "H. Peter Anvin" <hpa@...or.com> To: David Brownell <david-b@...bell.net> CC: Linux Kernel list <linux-kernel@...r.kernel.org>, Andrew Morton <akpm@...l.org>, Andrew Victor <andrew@...people.com>, Bill Gatliff <bgat@...lgatliff.com>, Haavard Skinnemoen <hskinnemoen@...el.com>, jamey.hicks@...com, Kevin Hilman <khilman@...sta.com>, Nicolas Pitre <nico@....org>, Russell King <rmk@....linux.org.uk>, Tony Lindgren <tony@...mide.com> Subject: Re: [patch/rfc 2.6.19-rc5] arch-neutral GPIO calls David Brownell wrote: > > - Only intended for use with "real" GPIOs that work from IRQ context; > e.g. pins on a SOC that are controlled by chip register access. > > - Doesn't handle I2C or SPI based GPIOs. I think we actually need > a different API for those "message based" GPIOs, where synchronous > get/set requires sleeping (and is thus unusable from IRQ context). > That API could be used for "real" GPIOs; the converse is not true. > > - No IORESOURCE_GPIO resource type (could be added though). > > - Can be trivially implemented today, on many systems (see partial > list above) ... no "provider" or gpiochip API necessary. > > - Provided in the form of a working patch, with sample implementation; > known to be viable on multiple architectures and platforms. > > - Includes Documentation/gpio.txt > > Comments? > If this is done, I think it's essential that a "high-level" API (one that supports message-based GPIO) is provided at the same time. The "high-level" API should be able to address the GPIOs addressed by the low-level API. What we do *not* want is a bunch of stuff using the low-level API when the high-level API would work. -hpa - 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