mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Timur Tabi <timur@codeaurora.org>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Alexandre Courbot <gnurou@gmail.com>,
	Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	Mathias Nyman <mathias.nyman@linux.intel.com>,
	Ning Li <ning.li@intel.com>, Alan Cox <alan@linux.intel.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] pinctrl: Intel Cherryview/Braswell support
Date: Wed, 05 Nov 2014 22:19:09 +0100	[thread overview]
Message-ID: <3242341.BG0xCMgUSF@vostro.rjw.lan> (raw)
In-Reply-To: <545959A8.7010305@codeaurora.org>

On Tuesday, November 04, 2014 04:56:40 PM Timur Tabi wrote:
> On 11/04/2014 05:13 PM, Rafael J. Wysocki wrote:
> > Well, first of all, you won't use phandles with ACPI.:-)
> 
> Yes, which makes things complicated for me.  The pinctrl binding makes 
> heavy use of phandles, so it will be a challenge to come up with a 
> substitue.
> 
> > That seems to be the case in which some ACPI-specific code would need to be
> > written.  In ACPI, instead of the list of phandles you'll have a list of
> > references to device objects that you can walk in an analogous way.
> 
> Can you point me to an example Linux driver that parses references?

The GPIO subsystem does that, but it probably is too complicated for your case,
because ACPI has its own native way of representing GPIOs and what we do there
is to translate the ACPI way into what the GPIO core expects.  Not exactly
straightforward, that.

Anyway, if you want me to describe it to you, please let me know.

For pinctrl we don't have any "native ACPI way" of representing things, so
we'll need to start with the DT binding directly.  That's why I asked about it.

[cut]

> > And it looks like we'll need a device_property_read_string_index().:-)
> 
> Multi-string properties are also very popular in device tree.

Those we do handle already.

> >
> > BTW, where's the pinctrl binding documented?
> 
> Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt

Thanks!

Rafael


  parent reply	other threads:[~2014-11-05 20:58 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03 11:01 Mika Westerberg
2014-11-03 11:01 ` [PATCH v2 1/2] gpio / ACPI: Add knowledge about pin controllers to acpi_get_gpiod() Mika Westerberg
2014-11-04 10:18   ` Linus Walleij
2014-11-03 11:01 ` [PATCH v2 2/2] pinctrl: Add Intel Cherryview/Braswell pin controller support Mika Westerberg
2014-11-04 10:23   ` Linus Walleij
2014-11-03 23:24 ` [PATCH v2 0/2] pinctrl: Intel Cherryview/Braswell support Timur Tabi
2014-11-04  8:20   ` Mika Westerberg
2014-11-04  9:39     ` Mika Westerberg
2014-11-04 13:31       ` Rafael J. Wysocki
2014-11-04 13:48         ` Linus Walleij
2014-11-04 14:16           ` Rafael J. Wysocki
2014-11-04 14:12             ` Mika Westerberg
2014-11-04 16:37           ` Timur Tabi
2014-11-04 21:51         ` Timur Tabi
2014-11-04 22:47           ` Rafael J. Wysocki
2014-11-04 22:32             ` Timur Tabi
2014-11-04 22:39               ` Timur Tabi
2014-11-04 23:13                 ` Rafael J. Wysocki
2014-11-04 22:56                   ` Timur Tabi
2014-11-04 23:18                     ` Timur Tabi
2014-11-05 21:04                       ` Rafael J. Wysocki
2014-11-05 21:19                     ` Rafael J. Wysocki [this message]
2014-11-04 23:00               ` Rafael J. Wysocki
2014-11-04 17:54     ` Timur Tabi
2014-11-04 19:04       ` Mika Westerberg
2014-11-06 19:30         ` Linus Walleij
2014-11-05 21:46       ` Grant Likely
2014-11-05 21:59         ` Timur Tabi
2014-11-05 22:15         ` Rafael J. Wysocki
2014-11-06 17:37           ` Grant Likely
2014-11-06 18:01             ` Timur Tabi
2014-11-07 23:12             ` Timur Tabi
2014-11-06 19:28       ` Linus Walleij
2014-11-05 21:44 ` Olof Johansson
2014-11-06  6:07   ` Mika Westerberg

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=3242341.BG0xCMgUSF@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=alan@linux.intel.com \
    --cc=gnurou@gmail.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathias.nyman@linux.intel.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=ning.li@intel.com \
    --cc=timur@codeaurora.org \
    /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

all inboxes | Powered by JetHome®