From: Liam Girdwood <liam.girdwood@wolfsonmicro.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH 2.4] Wolfson AC97 touch screen driver - Input Event interface
Date: Wed, 17 Dec 2003 15:56:24 +0000 [thread overview]
Message-ID: <1071676584.23686.2731.camel@cearnarfon> (raw)
In-Reply-To: <3FE076A2.9050406@pobox.com>
On Wed, 2003-12-17 at 15:30, Jeff Garzik wrote:
> > +/*
> > + * Pen down detection
> > + *
> > + * Pen down detection can either be via an interrupt (preferred) or
> > + * by polling the PDEN bit. This is an option because some systems may
> > + * not support the pen down interrupt.
> > + *
> > + * Set pen_int to 1 to enable interrupt driven pen down detection.
> > + */
> > +MODULE_PARM(pen_int,"i");
> > +MODULE_PARM_DESC(pen_int, "Set pen down interrupt");
> > +static int pen_int = 0;
>
> I wouldn't call this "detection" ;-)
>
> This module option is awful for users. How do users know what to do?
> (rhetorical question...) IMO this should be selected automatically on
> a per-chipset basis. I'm sure there is _some_ way to notice
> programmatically, for instance selected by chipset or selecting by
> sending a test interrupt.
>
> XScale PDA users just aren't going to know this kind of information off
> the top of their heads...
>
>
Yeah, your right. I was aiming this configuration option at developers.
Currently the driver can either poll the pen down status (expensive, but
platform agnostic) or it could be interrupted (if supported on the
platform) when the pen up / down status changed.
I'll make this automatically be determined at build time.
> > /*
> > * ADC sample delay times in uS
> > */
> > static const int delay_table[16] = {
> > - 21, // 1 AC97 Link frames
> > - 42, // 2
> > - 84, // 4
> > - 167, // 8
> > - 333, // 16
> > - 667, // 32
> > - 1000, // 48
> > - 1333, // 64
> > - 2000, // 96
> > - 2667, // 128
> > - 3333, // 160
> > - 4000, // 192
> > - 4667, // 224
> > - 5333, // 256
> > - 6000, // 288
> > - 0 // No delay, switch matrix always on
> > + 21,// 1 AC97 Link frames
> > + 42,// 2
> > + 84,// 4
> > + 167,// 8
> > + 333,// 16
> > + 667,// 32
> > + 1000,// 48
> > + 1333,// 64
> > + 2000,// 96
> > + 2667,// 128
> > + 3333,// 160
> > + 4000,// 192
> > + 4667,// 224
> > + 5333,// 256
> > + 6000,// 288
> > + 0 // No delay, switch matrix always on
> > };
>
> is this a mistake? You just made the code more difficult to read.
Yep, I seem to have some unintentional whitespace/tab changes.
> > +// Todo
> > +static void wm97xx_interrupt(int irq, void *dev_id, struct pt_regs *regs)
> > +{
> > + info("int recv");
> > +}
>
> hmmmm.
>
> This change doesn't seem terribly appropriate for the 2.4.x stable series...
>
>
Work in progress. Will remove for 2.4.x
I'll address the remaining issues create another patch.
Liam
prev parent reply other threads:[~2003-12-17 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-17 14:44 [PATCH 2.4] Wolfson AC97 touch screen driver - Input Event interface Liam Girdwood
2003-12-17 15:30 ` Jeff Garzik
2003-12-17 15:56 ` Liam Girdwood [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=1071676584.23686.2731.camel@cearnarfon \
--to=liam.girdwood@wolfsonmicro.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
/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.