linux-kernel - Re: [RFC PATCH] GPIO: add control of powerdown modes and pull-up/down configurations.

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, 30 Aug 2010 10:35:02 -0700 (PDT)
From:	David Brownell <david-b@...bell.net>
To:	linux-kernel@...r.kernel.org,
	MyungJoo Ham <myungjoo.ham@...sung.com>
Cc:	Kyungmin Park <kyungmin.park@...sung.com>,
	David Brownell <dbrownell@...rs.sourceforge.net>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Grant Likely <grant.likely@...retlab.ca>,
	Jani Nikula <ext-jani.1.nikula@...ia.com>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	MyungJoo Ham <myungjoo.ham@...il.com>
Subject: Re: [RFC PATCH] GPIO: add control of powerdown modes and pull-up/down configurations.

--- On Mon, 8/30/10, MyungJoo Ham <myungjoo.ham@...sung.com> wrote:

> From: MyungJoo Ham <myungjoo.ham@...sung.com>
> Subject: [RFC PATCH] GPIO: add control of powerdown modes and pull-up/down configurations.

NAK.

Note that Documentation/gpio.txt specifies such
pinmux/configuration as out of scope.  There isn't
even uniformity of models about such things between
SOCs (and ASICs etc).

Put these kinds of things in arch-specific code,
which has good reason to know about all the ways
each platform differs from others, and to cope.

Look at OMAP and AT91 for some examples of SOCs
which have addressed these issues cleanly, and
without committing mayhem on the GPIO framework.

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