mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gary Bisson <gary.bisson@boundarydevices.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: egalax_ts - do not release gpio if probe successful
Date: Fri, 13 Jan 2017 00:03:43 +0100	[thread overview]
Message-ID: <20170112230343.rt6e2qrhnvl4cvqq@x240.lan> (raw)
In-Reply-To: <20170112183019.GB7475@dtor-ws>

Hi Dmitri,

On Thu, Jan 12, 2017 at 10:30:19AM -0800, Dmitry Torokhov wrote:
> Hi Gary,
> 
> On Wed, Jan 11, 2017 at 06:28:41PM +0100, Gary Bisson wrote:
> > Thus preventing anyone to later modify the interrupt GPIO direction
> > and/or state without the driver knowing.
> 
> I am afraid not releasing gpio after waking up the controller will cause
> request_irq to fail if we are using the same pin for interrupt and
> wakeup (as majority of current DTSes do: see
> arch/arm/boot/dts/imx53-tx53-x13x.dts for example).

No, keeping the GPIO doesn't prevent from requesting the IRQ.

However it keeps other drivers/users from changing the GPIO as output
later on.

> You'll need to figure out if irq is backed by the same gpio as wakeup
> and act accordingly.
> 
> What setup did you test this on? Was it shared pin or dedicated wakeup?

I've tested on i.MX6Q Nitrogen6x [1] with Hannstar 10" display [2].

Regards,
Gary

[1] https://boundarydevices.com/product/nitrogen6x-board-imx6-arm-cortex-a9-sbc/
[2] https://boundarydevices.com/product/nit6x_10-1hannstar/

  reply	other threads:[~2017-01-12 23:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-11 17:28 Gary Bisson
2017-01-12 18:30 ` Dmitry Torokhov
2017-01-12 23:03   ` Gary Bisson [this message]
2017-01-12 23:40     ` Dmitry Torokhov
2017-01-16 14:43       ` Gary Bisson

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=20170112230343.rt6e2qrhnvl4cvqq@x240.lan \
    --to=gary.bisson@boundarydevices.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®