[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <535A899E.5020801@codeaurora.org>
Date: Fri, 25 Apr 2014 11:13:18 -0500
From: Timur Tabi <timur@...eaurora.org>
To: "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" <rafael.j.wysocki@...el.com>
Subject: Re: [PATCH v3 1/1] pinctrl: add Intel BayTrail GPIO/pinctrl support
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.
AFAIK, there is nothing at all like that for ACPI systems. Do you have
an example of a driver making pinmux calls directly?
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the
Code Aurora Forum, hosted by The Linux Foundation.
--
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/
Powered by blists - more mailing lists