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]

Date:	Thu, 24 Apr 2014 14:58:48 +0300
From:	"Westerberg, Mika" <mika.westerberg@...el.com>
To:	Timur Tabi <timur@...eaurora.org>
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" <rafael.j.wysocki@...el.com>
Subject: Re: [PATCH v3 1/1] pinctrl: add Intel BayTrail GPIO/pinctrl support

On Thu, Apr 24, 2014 at 06:18:38AM -0500, Timur Tabi wrote:
> Westerberg, Mika wrote:
> >>>That is, when the kernel parses the ASL, and it seems a command to
> >>>configure pin #3 to function #4, it calls the local pinctrl driver to do
> >>>that?
> 
> >I'm not aware of ASL code that allows you to do that. Do you have examples?
> 
> No, that's my point.  I was expecting the pinmux functions of the
> pinctrl driver are used by ACPI, but apparently they aren't, and
> that's why I'm asking.

Which functions?

> I'm wondering why a pinctrl driver for an
> ACPI platform should be defining pinmux function groups.  I haven't
> gotten a straight answer to that question.

Are you asking why pinctrl-baytrail.c uses pinctrl_gpio_ranges even if it
is a pretty much standard GPIO driver? Mathias probably can answer that
question better than me.
--
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/