linux-kernel - Re: pinctrl_config APIs, and other pinmux questions

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 17 Oct 2011 17:11:36 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Shawn Guo <shawn.guo@...escale.com>
Cc:	Stephen Warren <swarren@...dia.com>,
	Linus Walleij <linus.walleij@...ricsson.com>,
	Lee Jones <lee.jones@...aro.org>,
	Joe Perches <joe@...ches.com>,
	Russell King <linux@....linux.org.uk>,
	Linaro Dev <linaro-dev@...ts.linaro.org>,
	Sascha Hauer <s.hauer@...gutronix.de>,
	David Brown <davidb@...eaurora.org>,
	Stijn Devriendt <highguy@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Grant Likely <grant.likely@...retlab.ca>,
	Barry Song <21cnbao@...il.com>
Subject: Re: pinctrl_config APIs, and other pinmux questions

On Fri, Oct 14, 2011 at 4:59 PM, Shawn Guo <shawn.guo@...escale.com> wrote:
> [Stephen]
>> I've started to look at porting the Tegra pinmux driver to your pinctrl
>> subsystem. In order to replace the existing pinmux driver, I need a way
>> to support configuring options such as tri-state, pull-up/down, drive-
>> strength, etc.
>>
> I'm also concerned about this.  The current pinctrl subsystem only
> implements pinmux.  Before pin/pad configuration (pincfg) support is
> available, I can not really convert imx iomuxc driver (iomux-v3) over
> to use the subsystem.

I have the same problem for drivers/gpio/gpio-nomadik. which
does all weird kind of stuff. So you're not alone.

The reason why this is not in the subsystem as of today is that
we cannot push hundreds of kilobytes of upfront design with no drivers
using it, the current patch set in for-next is big enough as it is right
now.
http://en.wikipedia.org/wiki/Big_Design_Up_Front

But we can start thinking about the next step, so lets design the
generic pin control stuff we need and merge it to -next early so
we can work on it next kernel cycle.

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/