linux-kernel - Re: [PATCH 1/2] gpiolib: introduce gpio_set

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: <20111205155634.GW11150@opensource.wolfsonmicro.com>
Date:	Mon, 5 Dec 2011 15:56:35 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Jean-Christophe PLAGNIOL-VILLARD <plagnioj@...osoft.com>
Cc:	Stephen Warren <swarren@...dia.com>,
	Igor Grinberg <grinberg@...pulab.co.il>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Nicolas Ferre <nicolas.ferre@...el.com>,
	Grant Likely <grant.likely@...retlab.ca>
Subject: Re: [PATCH 1/2] gpiolib: introduce gpio_set_pullup

On Mon, Dec 05, 2011 at 04:40:11PM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 08:51 Tue 29 Nov     , Stephen Warren wrote:

> > I believe the pinctrl subsystem should be applicable to any chip, be it
> > the main SoC/CPU in the system, or any other chip. We don't currently
> > have any non-SoC drivers, but that's just because nobody has written them
> > yet; there's no technical reason they couldn't exist.

> sorry pinmux for gpio specific management i's overkill

If it's a GPIO-only device then probaby but lots of devices have a
fairly large range of signals that can be brought out on the pins (often
even more than a typical SoC actually).
--
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/