From: Timur Tabi <timur@codeaurora.org>
To: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
"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" <rjw@rjwysocki.net>
Subject: Re: [PATCH v3 1/1] pinctrl: add Intel BayTrail GPIO/pinctrl support
Date: Fri, 25 Apr 2014 11:31:49 -0500 [thread overview]
Message-ID: <535A8DF5.4090104@codeaurora.org> (raw)
In-Reply-To: <535A8B91.6030903@intel.com>
Rafael J. Wysocki wrote:
>>
>
> 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?
I only just learned some of this myself, so I'm no expert. My
understanding is that the all of the pinctrl-* properties and nodes are
scanned by the pinctrl layer itself. So you could have a SATA
controller node that points to a pin control node (via phandles). When
the SATA driver is probed, the pinctrl layer notices the phandles and
automatically calls the pinctrl layer to configure the pins and pin muxes.
--
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:31 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
2014-04-25 16:21 ` Rafael J. Wysocki
2014-04-25 16:31 ` Timur Tabi [this message]
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=535A8DF5.4090104@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 \
--cc=rjw@rjwysocki.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.