linux-kernel - Re: [PATCH 1/2] gpio: add pin biasing and drive mode to gpiolib

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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 27 Apr 2011 22:58:46 +0100
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Linus Walleij <linus.walleij@...aro.org>,
	Kyungmin Park <kmpark@...radead.org>,
	linux-kernel@...r.kernel.org,
	Haojian Zhuang <haojian.zhuang@...il.com>,
	Grant Likely <grant.likely@...retlab.ca>,
	Ben Nizette <bn@...sdigital.com>,
	Lee Jones <lee.jones@...aro.org>,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 1/2] gpio: add pin biasing and drive mode to gpiolib

On Wed, Apr 20, 2011 at 04:43:15PM +0100, Alan Cox wrote:
> > Then of course the GPIO driver can in turn call the padmux
> > subsystem to request its pins or fail/bail out if they are taken.
> 
> Yes that makes a lot more sense. It preserves the abstraction in the
> simple cases but handles the complex stuff right.

If one GPIO can be routed to multiple pads, it is not possible for
the GPIO driver to request the padmux code to route the GPIO to the
outside world - the GPIO layer doesn't have the information to tell
the padmux code which pad to route the GPIO to.
--
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/