linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: akpm@linux-foundation.org
Cc: linux-input@vger.kernel.org, eric.miao@marvell.com, david-b@pacbell.net
Subject: Re: [patch 22/22] input: ads7846: introduce platform specific way to synchronize sampling
Date: Thu, 12 Mar 2009 19:34:01 -0700	[thread overview]
Message-ID: <20090313023400.GA16163@dtor-d630.eng.vmware.com> (raw)
In-Reply-To: <200903041959.n24JxDIQ028495@imap1.linux-foundation.org>

Hi,

On Wed, Mar 04, 2009 at 11:59:13AM -0800, akpm@linux-foundation.org wrote:
> From: Eric Miao <eric.miao@marvell.com>
> 
> Noises can be introduced when LCD signals are being driven, some platforms
> provide a signal to assist the synchronization of this sampling procedure.
> 
> Signed-off-by: Eric Miao <eric.miao@marvell.com>
> Cc: David Brownell <david-b@pacbell.net>
> Cc: Dmitry Torokhov <dtor@mail.ru>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
> 
>  drivers/input/touchscreen/ads7846.c |   10 ++++++++++
>  include/linux/spi/ads7846.h         |    2 ++
>  2 files changed, 12 insertions(+)
> 
> diff -puN drivers/input/touchscreen/ads7846.c~input-ads7846-introduce-platform-specific-way-to-synchronize-sampling drivers/input/touchscreen/ads7846.c
> --- a/drivers/input/touchscreen/ads7846.c~input-ads7846-introduce-platform-specific-way-to-synchronize-sampling
> +++ a/drivers/input/touchscreen/ads7846.c
> @@ -127,6 +127,8 @@ struct ads7846 {
>  	void			(*filter_cleanup)(void *data);
>  	int			(*get_pendown_state)(void);
>  	int			gpio_pendown;
> +
> +	void			(*wait_for_sync)(void);
>  };
>  
>  /* leave chip selected when we're done, for quicker re-select? */
> @@ -511,6 +513,10 @@ static int get_pendown_state(struct ads7
>  	return !gpio_get_value(ts->gpio_pendown);
>  }
>  
> +static void null_wait_for_sync(void)
> +{
> +}
> +
>  /*
>   * PENIRQ only kicks the timer.  The timer only reissues the SPI transfer,
>   * to retrieve touchscreen status.
> @@ -686,6 +692,7 @@ static void ads7846_rx_val(void *ads)
>  	default:
>  		BUG();
>  	}
> +	ts->wait_for_sync();
>  	status = spi_async(ts->spi, m);
>  	if (status)
>  		dev_err(&ts->spi->dev, "spi_async --> %d\n",
> @@ -723,6 +730,7 @@ static enum hrtimer_restart ads7846_time
>  	} else {
>  		/* pen is still down, continue with the measurement */
>  		ts->msg_idx = 0;
> +		ts->wait_for_sync();

We are in hard IRQ context here. What is the expectation of
wait_for_sync()? How long are we waiting here?

-- 
Dmitry

  reply	other threads:[~2009-03-13  2:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-04 19:59 [patch 22/22] input: ads7846: introduce platform specific way to synchronize sampling akpm
2009-03-13  2:34 ` Dmitry Torokhov [this message]
2009-03-13  2:42   ` Eric Miao
2009-03-13  2:50     ` Eric Miao
2009-03-14  1:09       ` David Brownell
2009-03-14  3:41         ` Eric Miao
2009-03-14 12:55           ` Mark Brown

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=20090313023400.GA16163@dtor-d630.eng.vmware.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=david-b@pacbell.net \
    --cc=eric.miao@marvell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).