linux-kernel - Re: [PATCH v3 1/1] pinctrl: add Intel BayTrail GPIO/pinctrl 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: <535A8B91.6030903@intel.com>
Date:	Fri, 25 Apr 2014 18:21:37 +0200
From:	"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>
To:	Timur Tabi <timur@...eaurora.org>,
	"Westerberg, Mika" <mika.westerberg@...el.com>
CC:	Mathias Nyman <mathias.nyman@...ux.intel.com>,
	Linus <linus.walleij@...aro.org>,
	Grant Likely <grant.likely@...retlab.ca>,
	lkml <linux-kernel@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...ysocki.net>
Subject: Re: [PATCH v3 1/1] pinctrl: add Intel BayTrail GPIO/pinctrl support

On 4/25/2014 6:13 PM, Timur Tabi wrote:
> Westerberg, Mika wrote:
>> If you happen to have pin controller/mux driver that drives that 
>> hardware,
>> I'm sure your pinmux functions gets called.
>
> Actually, I don't think they do.  On a device-tree system, the 
> functions get called automatically by the pinctrl layer when it parses 
> the device tree.  This happens in response to probe, remove, and 
> various power management changes.
>

I would be interested in understanding what exactly the flow is in that 
situation, so care to educate me?  What does the driver do to trigger 
this and what exactly does happen in response to that?

Rafael

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