linux-kernel - Re: [RFC] generic GPIO parameter API

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20080610094359.GC6053@rakim.wolfsonmicro.main>
Date:	Tue, 10 Jun 2008 10:43:59 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Guennadi Liakhovetski <g.liakhovetski@....de>
Cc:	David Brownell <david-b@...bell.net>, linux-kernel@...r.kernel.org
Subject: Re: [RFC] generic GPIO parameter API

On Mon, Jun 09, 2008 at 07:09:00PM +0200, Guennadi Liakhovetski wrote:

> The primary purpose of the GPIO-parameter proposal was to allow to 
> configure these parameters from the user-space over sysfs by extending the 
> gpio-sysfs patch. And I2S master / slave operation should not be 
> switchable over sysfs, should it?

Not via that API, anyway (apart from anything else both ends of the link
need to agree) - I was more mentioning it as an example of a non-GPIO
function that could use the GPIO configuration.
--
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/