| 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: Wed, 20 Apr 2011 17:17:55 +0200 From: Linus Walleij <linus.walleij@...aro.org> To: Haojian Zhuang <haojian.zhuang@...il.com> Cc: Kyungmin Park <kmpark@...radead.org>, linux-kernel@...r.kernel.org, Grant Likely <grant.likely@...retlab.ca>, linux-arm-kernel@...ts.infradead.org, Ben Nizette <bn@...sdigital.com>, Lee Jones <lee.jones@...aro.org>, Alan Cox <alan@...rguk.ukuu.org.uk> Subject: Re: [PATCH 1/2] gpio: add pin biasing and drive mode to gpiolib 2011/4/20 Haojian Zhuang <haojian.zhuang@...il.com>: > I have an another question on board initialization. The configuration on pins > are including drive strength, pull and multiple function. > > Since this patch can configure drive strength, pull. Will it be preferred to use > in board initialization? I am reusing it (inside the example driver) for drive strength and bias. Multiple function again is pin/padmuxing. Even if some people are only muxing pins that can also be used as GPIO, this is not always the case. We can shunt out the same pins to be used as I2C or SPI for example, that means this cannot be handled in a GPIO driver since it has nothing to do with GPIO pins at all. Thus we need an orthogonal pin/padmux mechanism. 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