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: <1632312.tiWezf5I7W@vostro.rjw.lan>
Date:	Wed, 05 Nov 2014 23:15:26 +0100
From:	"Rafael J. Wysocki" <rjw@...ysocki.net>
To:	Grant Likely <grant.likely@...retlab.ca>
Cc:	Timur Tabi <timur@...eaurora.org>,
	Mika Westerberg <mika.westerberg@...ux.intel.com>,
	Linus Walleij <linus.walleij@...aro.org>,
	Alexandre Courbot <gnurou@...il.com>,
	Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
	Mathias Nyman <mathias.nyman@...ux.intel.com>,
	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 Wednesday, November 05, 2014 09:46:14 PM Grant Likely wrote:
> On Tue, Nov 4, 2014 at 5:54 PM, Timur Tabi <timur@...eaurora.org> wrote:
> > On 11/04/2014 02:20 AM, Mika Westerberg wrote:
> >>
> >> There is nothing like that yet in ACPI world but with the ACPI _DSD
> >> patches we are getting properties similar to DT which means that we can
> >> provide pinctrl bindings from ACPI systems as well.
> >
> >
> > Do you know if anyone has signed up to actually do the work of defining how
> > pinctrl will look in ACPI?  I'm guessing the simplest approach would be to:
> 
> Actually, for the most part we /don't/ want to try and put pinctrl
> into an ACPI binding. The assumption is that on an ACPI platform it
> would be the combination of ACPI and firmware responsible for the pin
> mappings, not the operating system.
> 
> Before even attempting to put pinctrl mappings into your driver, there
> should instead be a conversation at the ACPI spec level about whether
> or not it makes sense and what such a binding should look like.

We may need to support pinctrl on ACPI platforms in the meantime, though,
for reasons that Mika mentioned at one point (there are systems where the
firmware mangles things etc., which quite frankly is to be expected).

So while I'm all for discussing this in the ASWG, what's the interim approach
we should be using, in your opinion?

-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
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/