public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Nizette <ben@niasdigital.com>
To: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Cc: kernel <kernel@avr32linux.org>,
	"Egtvedt, Hans-Christian" <Hans-Christian.Egtvedt@atmel.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] favr32: improve touchscreen response
Date: Thu, 30 Jul 2009 07:39:21 +1000	[thread overview]
Message-ID: <1248903561.13515.178.camel@ben-desktop> (raw)
In-Reply-To: <20090727131758.050ca571@hskinnemoen-d830>

On Mon, 2009-07-27 at 13:17 +0200, Haavard Skinnemoen wrote:
> Ben Nizette wrote:
> > Hi Haavard,
> > 
> > This has hce's ack, any chance of getting it in .31?
> 
> Yeah, should be a good chance :-) Sorry for taking so long.
> 
> It doesn't apply, however. I ended up doing this:
> 
> diff --git a/arch/avr32/boards/favr-32/setup.c b/arch/avr32/boards/favr-32/setup.c
> index 46c9b0a..75f19f4 100644
> --- a/arch/avr32/boards/favr-32/setup.c
> +++ b/arch/avr32/boards/favr-32/setup.c
> @@ -72,6 +72,10 @@ static struct ads7846_platform_data ads7843_data = {
>  	.debounce_max		= 20,
>  	.debounce_rep		= 4,
>  	.debounce_tol		= 5,
> +
> +	.keep_vref_on		= true,
> +	.settle_delay_usecs	= 500,
> +	.penirq_recheck_delay_usecs = 100,
>  };
>  
>  static struct spi_board_info __initdata spi1_board_info[] = {
> 
> It appears to compile, but please verify that it's still correct.

Looks good, thanks!

Tested-by: Ben Nizette <bn@niasdigital.com>

> 
> Haavard


      reply	other threads:[~2009-07-29 21:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-20  2:36 [PATCH] favr32: improve touchscreen response Ben Nizette
2009-04-20  3:13 ` Ben Nizette
2009-04-20  5:54 ` Hans-Christian Egtvedt
2009-06-26  7:49 ` Ben Nizette
2009-07-27 11:17   ` Haavard Skinnemoen
2009-07-29 21:39     ` Ben Nizette [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=1248903561.13515.178.camel@ben-desktop \
    --to=ben@niasdigital.com \
    --cc=Hans-Christian.Egtvedt@atmel.com \
    --cc=haavard.skinnemoen@atmel.com \
    --cc=kernel@avr32linux.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