From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gpio / ACPI: ignore GpioInt() GPIOs when requesting GPIO_OUT_*
Date: Thu, 24 Mar 2016 16:01:33 +0200 [thread overview]
Message-ID: <20160324140133.GT2099@lahna.fi.intel.com> (raw)
In-Reply-To: <20160323225831.GA28309@dtor-ws>
On Wed, Mar 23, 2016 at 03:58:31PM -0700, Dmitry Torokhov wrote:
> From: Dmitry Torokhov <dtor@chromium.org>
>
> When firmware does not use _DSD properties that allow properly name GPIO
> resources, the kernel falls back on parsing _CRS resources, and will
> return entries described as GpioInt() as general purpose GPIOs even
> though they are meant to be used simply as interrupt sources for the
> device:
>
> Device (ETSA)
> {
> Name (_HID, "ELAN0001")
> ...
>
> Method(_CRS, 0x0, NotSerialized)
> {
> Name(BUF0,ResourceTemplate ()
> {
> I2CSerialBus(
> 0x10, /* SlaveAddress */
> ControllerInitiated, /* SlaveMode */
> 400000, /* ConnectionSpeed */
> AddressingMode7Bit, /* AddressingMode */
> "\\_SB.I2C1", /* ResourceSource */
> )
> GpioInt (Edge, ActiveLow, ExclusiveAndWake, PullNone,,
> "\\_SB.GPSW") { BOARD_TOUCH_GPIO_INDEX }
> } )
> Return (BUF0)
> }
> ...
> }
>
> This gives troubles with drivers such as Elan Touchscreen driver
> (elants_i2c) that uses devm_gpio_get to look up "reset" GPIO line and
> decide whether the driver is responsible for powering up and resetting
> the device or firmware is. In the above case the lookup succeeds, we map
> GPIO as output and later fail to request client->irq interrupt that is
> mapped to the same GPIO.
>
> Let's ignore resources described as GpioInt() when requesting output
> GPIO (but allow them when requesting GPIOD_ASIS or GPIOD_IN as some
> drivers - i2c-hid - do request GPIO as input and then map it to
> interrupt with gpiod_to_irq).
You could mention here that we only ignore GpioInt() resources in
fallback case.
> BUG=chrome-os-partner:51154
> TEST=Boot Cyan, verify touchscreen work
>
> Change-Id: Id20c730b937dce8a4135d2b64c8d798372d20e82
This is not needed for mainline patches :)
> Signed-off-by: Dmitry Torokhov <dtor@chromium.org>
Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>
next prev parent reply other threads:[~2016-03-24 14:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 22:58 [PATCH] gpio / ACPI: ignore GpioInt() GPIOs when requesting GPIO_OUT_* Dmitry Torokhov
2016-03-24 14:01 ` Mika Westerberg [this message]
2016-03-24 17:41 ` Dmitry Torokhov
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=20160324140133.GT2099@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
/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