linux-kernel - Re: [PATCH v2 0/2] pinctrl: Intel Cherryview/Braswell support

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]

Message-ID: <CACRpkdZOhcUsxC+VTBbpGSKfR7bXJ-WS9MxUb948r0Bvzyz2Mw@mail.gmail.com>
Date:	Thu, 6 Nov 2014 20:30:23 +0100
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Mika Westerberg <mika.westerberg@...ux.intel.com>
Cc:	Timur Tabi <timur@...eaurora.org>,
	Alexandre Courbot <gnurou@...il.com>,
	Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
	Mathias Nyman <mathias.nyman@...ux.intel.com>,
	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	Ning Li <ning.li@...el.com>, Alan Cox <alan@...ux.intel.com>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 0/2] pinctrl: Intel Cherryview/Braswell support

On Tue, Nov 4, 2014 at 8:04 PM, Mika Westerberg
<mika.westerberg@...ux.intel.com> wrote:

> We still need to account the fact that BIOS is supposed to configure the
> pins in advance. The pinctrl mappings are just for refining that, like
> muxing out the SPI pins instead of GPIOs and so on.

Pinctrl currently has no real way of reading out the state from the
hardware and presenting it as a selected group+function combination,
it only knows what has been selected intrinsically with the system,
so some enhancements may be needed to make pinctrl reflect
the state when booting.

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/