linux-kernel - Re: [PATCH] pinctrl: establish pull-up/pull-down terminology

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:	Mon, 24 Jun 2013 14:39:05 +0200
From:	Heiko Stübner <heiko@...ech.de>
To:	Linus Walleij <linus.walleij@...aro.org>
Cc:	Laurent Pinchart <laurent.pinchart@...asonboard.com>,
	Stephen Warren <swarren@...dotorg.org>,
	James Hogan <james.hogan@...tec.com>,
	Linus Walleij <linus.walleij@...ricsson.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Stephen Warren <swarren@...dia.com>,
	Anmar Oueja <anmar.oueja@...aro.org>
Subject: Re: [PATCH] pinctrl: establish pull-up/pull-down terminology

Am Montag, 24. Juni 2013, 14:24:12 schrieb Linus Walleij:
> On Sat, Jun 22, 2013 at 1:39 AM, Heiko Stübner <heiko@...ech.de> wrote:
> > Am Samstag, 22. Juni 2013, 01:30:18 schrieb Laurent Pinchart:
> >> [Stephen]
> >> 
> >> > IIRC the idea of the PULL_PIN_DEFAULT was to avoid having to specify
> >> > UP/DOWN for each pin/group, but could just say "default", which would
> >> > then reduce the number of pinctrl mapping table entries or pinctrl DT
> >> > property entries.
> >> 
> >> I may be mistaken, but I've understood the PULL_PIN_DEFAULT option as a
> >> way to select the default bias configuration when the default value is
> >> hardware- controlled, not as a pure software option.
> > 
> > Yep that was the original intent ... to handle hardware that hides the
> > complete logic from the software and you only get to turn it on or off,
> > while the direction and other params are determined internally for
> > example by the pin function.
> 
> Heiko, can you send a documentation patch to clarify this so we
> don't get any misunderstandings?
> 
> Maybe it'd be useful for software purposes as well, but let's save
> that for when it gets used like that.

will try to get this (and the changes from the other mail) done today

Heiko
--
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/