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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACRpkdbk8okbzaZgD=BqeMSOvbEvYNViqamd9i=NAaAWW=T9sQ@mail.gmail.com>
Date:	Thu, 24 Apr 2014 00:20:12 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Timur Tabi <timur@...eaurora.org>
Cc:	"Westerberg, Mika" <mika.westerberg@...el.com>,
	Mathias Nyman <mathias.nyman@...ux.intel.com>,
	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 Wed, Apr 23, 2014 at 5:14 PM, Timur Tabi <timur@...eaurora.org> wrote:

> How are the pin muxes normally configured in ACPI?

VERY good question.

>  All of our GPIOs have a
> pinmux on them, and so if you want to use the pin for the non-default
> functionality, you need to configure the mux.  Isn't that supposed to happen
> with the through the pinctrl driver?  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?

Let's suspect this is true. That is how GPIO work after all is it not?

I guess the other option would be that all systems must come with a
tailored set-up written in ASL, specific for each board configuration.

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/