All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 24 Apr 2014 06:18:38 -0500	[thread overview]
Message-ID: <5358F30E.9080402@codeaurora.org> (raw)
In-Reply-To: <20140424063546.GA30677@intel.com>

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.  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.

-- 
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.

  reply	other threads:[~2014-04-24 11:18 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 [this message]
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
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=5358F30E.9080402@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 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.