From: Timur Tabi <timur@codeaurora.org>
To: "Westerberg, Mika" <mika.westerberg@intel.com>
Cc: Mathias Nyman <mathias.nyman@linux.intel.com>,
Linus <linus.walleij@linaro.org>,
Grant Likely <grant.likely@secretlab.ca>,
lkml <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: [PATCH v3 1/1] pinctrl: add Intel BayTrail GPIO/pinctrl support
Date: Fri, 25 Apr 2014 11:13:18 -0500 [thread overview]
Message-ID: <535A899E.5020801@codeaurora.org> (raw)
In-Reply-To: <20140425074156.GI30677@intel.com>
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.
next prev parent reply other threads:[~2014-04-25 16:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 11:33 [PATCH v3 0/1] Pinctrl/gpio driver for Intel Baytrail platforms Mathias Nyman
2013-06-18 11:33 ` [PATCH v3 1/1] pinctrl: add Intel BayTrail GPIO/pinctrl support Mathias Nyman
2013-06-18 15:17 ` Linus Walleij
2013-06-19 10:28 ` Mathias Nyman
2014-04-11 22:54 ` Timur Tabi
2014-04-14 7:52 ` Mathias Nyman
2014-04-14 15:11 ` Timur Tabi
2014-04-15 10:01 ` Mathias Nyman
2014-04-17 16:47 ` Timur Tabi
2014-04-23 11:46 ` Mathias Nyman
2014-04-23 12:07 ` Timur Tabi
2014-04-23 13:59 ` Westerberg, Mika
2014-04-23 15:14 ` Timur Tabi
2014-04-23 22:20 ` Linus Walleij
2014-04-23 22:54 ` Timur Tabi
2014-04-24 6:27 ` Westerberg, Mika
2014-04-24 11:20 ` Timur Tabi
2014-04-24 11:38 ` Westerberg, Mika
2014-04-24 6:35 ` Westerberg, Mika
2014-04-24 11:18 ` Timur Tabi
2014-04-24 11:58 ` Westerberg, Mika
2014-04-24 13:29 ` Linus Walleij
2014-04-24 15:25 ` Timur Tabi
2014-04-25 7:41 ` Westerberg, Mika
2014-04-25 10:36 ` Linus Walleij
2014-04-25 16:13 ` Timur Tabi [this message]
2014-04-25 16:21 ` Rafael J. Wysocki
2014-04-25 16:31 ` Timur Tabi
2014-05-02 22:31 ` Linus Walleij
2014-04-23 22:17 ` Linus Walleij
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=535A899E.5020801@codeaurora.org \
--to=timur@codeaurora.org \
--cc=grant.likely@secretlab.ca \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=mika.westerberg@intel.com \
--cc=rafael.j.wysocki@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).