[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <E99B44D9-C9E3-4C0B-8B18-450121793EB5@arndb.de>
Date: Fri, 17 Oct 2014 20:09:51 +0200
From: Arnd Bergmann <arnd@...db.de>
To: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
CC: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Grant Likely <grant.likely@...aro.org>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
Aaron Lu <aaron.lu@...el.com>, devicetree@...r.kernel.org,
Linus Walleij <linus.walleij@...aro.org>,
Alexandre Courbot <gnurou@...il.com>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Bryan Wu <cooloney@...il.com>,
Darren Hart <dvhart@...ux.intel.com>,
Mark Rutland <mark.rutland@....com>
Subject: Re: [PATCH v5 10/12] gpio: Support for unified device properties interface
On October 17, 2014 2:16:00 PM CEST, "Rafael J. Wysocki" <rjw@...ysocki.net> wrote:
>From: Mika Westerberg <mika.westerberg@...ux.intel.com>
>
>Some drivers need to deal with only firmware representation of its
>GPIOs. An example would be a GPIO button array driver where each button
>is described as a separate firmware node in device tree. Typically
>these
>child nodes do not have physical representation in the Linux device
>model.
>
>In order to help device drivers to handle such firmware child nodes we
>add dev[m]_get_named_gpiod_from_child() that takes a child firmware
>node pointer as its second argument (the first one is the parent device
>itself), finds the GPIO using whatever is the underlying firmware
>method, and requests the GPIO properly.
Could we also have a wrapper around this function without a "name" argument, using just the index?
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists