All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Linus Walleij <linus.walleij@linaro.org>,
	Alexandre Courbot <gnurou@gmail.com>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/5] ACPI / gpio: Updates to properties
Date: Thu, 29 Sep 2016 10:00:15 +0300	[thread overview]
Message-ID: <20160929070015.GH1218@lahna.fi.intel.com> (raw)
In-Reply-To: <CAJZ5v0gkdZDnRjy_=tDys8LoKD2g5OZzOfNW6t+q8N3bw2ufUA@mail.gmail.com>

On Wed, Sep 28, 2016 at 11:32:46PM +0200, Rafael J. Wysocki wrote:
> Hi,
> 
> On Fri, Sep 23, 2016 at 4:57 PM, Mika Westerberg
> <mika.westerberg@linux.intel.com> wrote:
> > Hi,
> >
> > This series brings couple of useful GPIO related properties from Device
> > Tree to ACPI _DSD device properties:
> >
> >   - Names for GPIO lines
> >   - GPIO hogging
> >   - Holes in GPIO property lists
> >
> > We are using these to get Intel Galileo better supported in the mainline
> > kernel (but these may be useful for other boards as well). For example SPI
> > chip select on Galileo is connected to a GPIO line so we need to be able to
> > describe it in ACPI, and at the same time allow native chip selects.
> >
> > GPIO hogging can be used to set initial state of certain GPIOs available on
> > the headers regardless of the BIOS settings (which may be wrong as it knows
> > nothing about which devices have been connected).
> >
> > Mika Westerberg (5):
> >   ACPI / documentation: Use recommended name in GPIO property names
> >   ACPI / gpio: Add support for naming GPIOs
> >   ACPI / gpio: Add hogging support
> >   ACPI / property: Allow holes in reference properties
> >   ACPI / gpio: Allow holes in list of GPIOs for a device
> >
> >  Documentation/acpi/gpio-properties.txt |  72 ++++++++++++++--
> >  drivers/acpi/property.c                | 116 +++++++++++++++++++-------
> >  drivers/gpio/gpiolib-acpi.c            | 147 ++++++++++++++++++++++++++++++---
> >  include/linux/acpi.h                   |   3 +
> >  4 files changed, 292 insertions(+), 46 deletions(-)
> 
> I would like to tackle patches [1/5] and [4/5] first, as they are core
> patches and the rest is against gpiolib-acpi.

Works for me.

I can re-arrange the series so that the two core patches (1,4/5) are
first and then the GPIO parts.

> Moreover, the documentation patch [1/5] looks like immediately applicable to me.

Yes, it just fixes the names to match what is preferred.

  reply	other threads:[~2016-09-29  7:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-23 14:57 [PATCH 0/5] ACPI / gpio: Updates to properties Mika Westerberg
2016-09-23 14:57 ` [PATCH 1/5] ACPI / documentation: Use recommended name in GPIO property names Mika Westerberg
2016-09-23 14:57 ` [PATCH 2/5] ACPI / gpio: Add support for naming GPIOs Mika Westerberg
2016-09-23 14:57 ` [PATCH 3/5] ACPI / gpio: Add hogging support Mika Westerberg
2016-09-23 14:57 ` [PATCH 4/5] ACPI / property: Allow holes in reference properties Mika Westerberg
2016-09-28 21:36   ` Rafael J. Wysocki
2016-09-29  6:48     ` Mika Westerberg
2016-09-29 11:53       ` Rafael J. Wysocki
2016-09-29 11:56         ` Mika Westerberg
2016-09-29 12:33           ` Rafael J. Wysocki
2016-09-23 14:57 ` [PATCH 5/5] ACPI / gpio: Allow holes in list of GPIOs for a device Mika Westerberg
2016-09-28 21:32 ` [PATCH 0/5] ACPI / gpio: Updates to properties Rafael J. Wysocki
2016-09-29  7:00   ` Mika Westerberg [this message]
2016-09-29 12:26     ` Rafael J. Wysocki
2016-10-19 12:41 ` Mika Westerberg
2016-10-19 21:22   ` Rafael J. Wysocki
2016-10-20  7:46     ` Mika Westerberg
2016-10-20 12:17     ` Linus Walleij
2016-10-20 12:35       ` 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=20160929070015.GH1218@lahna.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=gnurou@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --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.