All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Dirk Behme <dirk.behme@de.bosch.com>
Cc: linux-input@vger.kernel.org,
	Oleksij Rempel <external.Oleksij.Rempel@de.bosch.com>
Subject: Re: [PATCH 1/3] Input: zforce - use irq handler instead of gpio polling
Date: Thu, 16 Jul 2015 10:43:41 -0700	[thread overview]
Message-ID: <20150716174341.GC32571@dtor-ws> (raw)
In-Reply-To: <55A4BD48.9000705@de.bosch.com>

On Tue, Jul 14, 2015 at 09:42:00AM +0200, Dirk Behme wrote:
> Hi Dmitry,
> 
> On 13.07.2015 19:04, Dmitry Torokhov wrote:
> >On Mon, Jul 13, 2015 at 02:49:37PM +0200, Dirk Behme wrote:
> >>From: Oleksij Rempel <external.Oleksij.Rempel@de.bosch.com>
> >>
> >>Remove the IRQ GPIO polling and request. Existing DTS should not be affected
> >>since the IRQ registration was and is based on "interrupts" descriptor of DTS.
> >
> >But this means that consecutive touchscreen readings will be delayed by
> >the time it takes to schedule the thread.
> >
> >What is the motivation for this change?
> 
> 
> This is the generic part we've done for a special hardware
> configuration: There is some hardware which uses an I2C Serializer /
> Deserializer (SerDes) to communicate with the zFroce touch driver.
> In this case the SerDes will be configured as an interrupt
> controller and the zForce driver will have no access to poll the
> GPIO line.

In this case can we make gpio optional and use it if it is specified
falling back on one read per ISR invocation in its absence?

Thanks.

-- 
Dmitry

      reply	other threads:[~2015-07-16 17:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13 12:49 [PATCH 1/3] Input: zforce - use irq handler instead of gpio polling Dirk Behme
2015-07-13 12:49 ` [PATCH 2/3] Input: zforce - enable irq only if we are ready to process it Dirk Behme
2015-07-13 17:07   ` Dmitry Torokhov
     [not found]     ` <55A4AEEF.4020300@de.bosch.com>
2015-07-17 21:58       ` Dmitry Torokhov
     [not found]         ` <55AC84D9.2080809@de.bosch.com>
2015-07-20  6:35           ` Dmitry Torokhov
     [not found]             ` <55AC9C57.4070400@de.bosch.com>
2015-07-20 16:54               ` Dmitry Torokhov
2015-07-13 12:49 ` [PATCH 3/3] Input: zforce - remove zforce_irq Dirk Behme
2015-07-13 17:11   ` Dmitry Torokhov
2015-07-13 17:04 ` [PATCH 1/3] Input: zforce - use irq handler instead of gpio polling Dmitry Torokhov
2015-07-14  7:42   ` Dirk Behme
2015-07-16 17:43     ` Dmitry Torokhov [this message]

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=20150716174341.GC32571@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=dirk.behme@de.bosch.com \
    --cc=external.Oleksij.Rempel@de.bosch.com \
    --cc=linux-input@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 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.