From: Linus Walleij <linus.walleij@linaro.org>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Alexandre Courbot <gnurou@gmail.com>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 3/4] ACPI / gpio: Add hogging support
Date: Thu, 20 Oct 2016 14:09:30 +0200 [thread overview]
Message-ID: <CACRpkdYTUy9u0_VWQ6CuriD+__H8EkR_MyarXMFdJ9hbZwYUgw@mail.gmail.com> (raw)
In-Reply-To: <20160929133944.158596-4-mika.westerberg@linux.intel.com>
On Thu, Sep 29, 2016 at 3:39 PM, Mika Westerberg
<mika.westerberg@linux.intel.com> wrote:
> GPIO hogging means that the GPIO controller can "hog" and configure certain
> GPIOs without need for a driver or userspace to do that. This is useful in
> open-connected boards where BIOS cannot possibly know beforehand which
> devices will be connected to the board.
>
> This adds GPIO hogging mechanism to ACPI analogous to Device Tree.
>
> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Overall nice to have the hogs in ACPI too!
Again here my comment is to break out device_property() and fwnode_*
accessing code to a file shared between ACPI and OF.
If it makes sense.
Because the idea was not to invent those abstractions in order to
just use them with ACPI I hope.
The problem is that some of the code seems to be ACPI-specific,
so if it doesn't work out, I'm also OK to keep it like this.
Yours,
Linus Walleij
next prev parent reply other threads:[~2016-10-20 12:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 13:39 [PATCH v2 0/4] ACPI / gpio: Updates to properties Mika Westerberg
2016-09-29 13:39 ` [PATCH v2 1/4] ACPI / property: Allow holes in reference properties Mika Westerberg
2016-10-11 20:46 ` Rafael J. Wysocki
2016-10-20 12:00 ` Linus Walleij
2016-09-29 13:39 ` [PATCH v2 2/4] ACPI / gpio: Add support for naming GPIOs Mika Westerberg
2016-10-07 17:05 ` Andy Shevchenko
2016-10-09 15:01 ` Mika Westerberg
2016-10-09 17:08 ` Andy Shevchenko
2016-10-20 12:02 ` Linus Walleij
2016-10-20 12:08 ` Mika Westerberg
2016-10-20 12:06 ` Linus Walleij
2016-10-20 12:14 ` Mika Westerberg
2016-09-29 13:39 ` [PATCH v2 3/4] ACPI / gpio: Add hogging support Mika Westerberg
2016-10-20 12:09 ` Linus Walleij [this message]
2016-10-20 12:29 ` Mika Westerberg
2016-09-29 13:39 ` [PATCH v2 4/4] ACPI / gpio: Allow holes in list of GPIOs for a device Mika Westerberg
2016-10-20 12:10 ` Linus Walleij
2016-10-07 17:10 ` [PATCH v2 0/4] ACPI / gpio: Updates to properties Andy Shevchenko
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=CACRpkdYTUy9u0_VWQ6CuriD+__H8EkR_MyarXMFdJ9hbZwYUgw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=gnurou@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.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.