[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150330141815.GG1524@lahna.fi.intel.com>
Date: Mon, 30 Mar 2015 17:18:15 +0300
From: Mika Westerberg <mika.westerberg@...ux.intel.com>
To: Octavian Purdila <octavian.purdila@...el.com>
Cc: Linus Walleij <linus.walleij@...aro.org>,
Lars-Peter Clausen <lars@...afoo.de>,
Robert Dolca <robert.dolca@...il.com>,
Robert Dolca <robert.dolca@...el.com>,
"linux-iio@...r.kernel.org" <linux-iio@...r.kernel.org>,
Jonathan Cameron <jic23@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Hartmut Knaack <knaack.h@....de>,
Peter Meerwald <pmeerw@...erw.net>,
Denis CIOCCA <denis.ciocca@...com>
Subject: Re: [PATCH] IIO: Adds ACPI support for ST gyroscopes
On Mon, Mar 30, 2015 at 04:52:49PM +0300, Octavian Purdila wrote:
> What if we can do the pin configuration in gpiolib right after the
> GPIO controller is initialized. I am thinking of searching the ACPI
> namespace and looking for resources that have GpioInt entries for that
> particular GPIO controller and use them to set the pins to input (and
> ideally also set the other properties like pullups, pulldowns, etc.)
The pinctrl subsystem can do this already but currently there is no ACPI
support. Using information from GpioInt to fill pinctrl pin
configuration sounds good to me.
--
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