On Friday 16 February 2007 9:37 am, Nicolas Ferre wrote:
> David Brownell :
> [..]
> > Thanks! I'll be glad to see fewer versions of this driver floating around.
> > And to see the next version of the ads7843 patches ... :)
>
> Hi,
>
> Here is the ads7843 support for the ads7846 touchscreen driver. It is
> very little and takes great advantage of the previous rework.
Good! But see below for one fix ... after that, please split out the
ads7846 update by itself, and submit that patch to the input subsystem
maintainer with your signed-off-by.
Did you find out what was causing the jerky behavior (draw a circle,
it looks like a square) before?
> Tested on Atmel at91sam926[13]ek board with atmel_spi underlying driver.
Which has now been merged; minor fixes needed, including a build
fix for AT91. I expect those will merge by the time 2.6.21 is done.
Looks like that driver is going to get a fair amount of use. :)
> I also put a use case based on the at91sam9263ek init code. This code is
> just sent as an example, I will send those init patches trough AT91
> maintainer.
Yeah, support for that board hasn't made it to kernel.org yet.
I hope you'll also update Atmel's other EK boards using this chip.
> Index: linux-2.6.20-at91/drivers/input/touchscreen/ads7846.c
> ===================================================================
> --- linux-2.6.20-at91.orig/drivers/input/touchscreen/ads7846.c
> +++ linux-2.6.20-at91/drivers/input/touchscreen/ads7846.c
> @@ -39,7 +39,8 @@
> /*
> * This code has been heavily tested on a Nokia 770, and lightly
> * tested on other ads7846 devices (OSK/Mistral, Lubbock).
> - * Support for ads7843 and ads7845 has only been stubbed in.
> + * Support for ads7843 tested on Atmel at91sam926x-EK.
> + * Support for ads7845 has only been stubbed in.
> *
> * IRQ handling needs a workaround because of a shortcoming in handling
> * edge triggered IRQs on some platforms like the OMAP1/2. These
> @@ -246,18 +247,15 @@ static int ads7846_read12_ser(struct dev
>
> /* REVISIT: take a few more samples, and compare ... */
>
> - /* maybe off internal vREF */
> - if (use_internal) {
This part doesn't make sense. Could you say what you're trying
to do? The ads7846 requres an external vREF. Is the issue that
maybe the REF_OFF command isn't just turning off the (non-existent)
internal voltage reference? If so the comments need updating, and
maybe the name REF_OFF needs to change too...
> - req->ref_off = REF_OFF;
> - req->xfer[4].tx_buf = &req->ref_off;
> - req->xfer[4].len = 1;
> - spi_message_add_tail(&req->xfer[4], &req->msg);
> -
> - req->xfer[5].rx_buf = &req->scratch;
> - req->xfer[5].len = 2;
> - CS_CHANGE(req->xfer[5]);
> - spi_message_add_tail(&req->xfer[5], &req->msg);
> - }
> + req->ref_off = REF_OFF;
> + req->xfer[4].tx_buf = &req->ref_off;
> + req->xfer[4].len = 1;
> + spi_message_add_tail(&req->xfer[4], &req->msg);
> +
> + req->xfer[5].rx_buf = &req->scratch;
> + req->xfer[5].len = 2;
> + CS_CHANGE(req->xfer[5]);
> + spi_message_add_tail(&req->xfer[5], &req->msg);
>
> ts->irq_disabled = 1;
> disable_irq(spi->irq);
> @@ -536,6 +534,10 @@ static void ads7846_rx(void *ads)
> } else
> Rt = 0;
>
> + if (ts->model == 7843)
> + Rt = ts->pressure_max / 2;
> +
> +
Heh. Other than turning whatever-that-is off, this looks like the only
substantive change needed. You're right, this isn't much at all ... the
ads7843 support has now become almost trivial!
> /* Sample found inconsistent by debouncing or pressure is beyond
> * the maximum. Don't report it to user space, repeat at least
> * once more the measurement
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]