From: Justin Waters <justin.waters@timesys.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"linux-arm-kernel@lists.arm.linux.org.uk"
<linux-arm-kernel@lists.arm.linux.org.uk>,
"dmitry.torokhov@gmail.com" <dmitry.torokhov@gmail.com>,
"linux@maxim.org.za" <linux@maxim.org.za>
Subject: Re: [PATCH 1/2] atmel_tsadcc: Device driver for AT91SAM9RL Touchscreen
Date: Fri, 25 Apr 2008 17:37:33 -0400 [thread overview]
Message-ID: <1209159453.6990.48.camel@justin-linux> (raw)
In-Reply-To: <20080425211041.GC28497@flint.arm.linux.org.uk>
Thank you for the comments. I've inlined responses below:
On Fri, 2008-04-25 at 17:10 -0400, Russell King - ARM Linux wrote:
> > +config TOUCHSCREEN_ATMEL_TSADCC
> > + tristate "Atmel Touchscreen Interface"
>
> No dependencies. So does this mean this'll build and link on an
> x86 platform?
>
I was actually thinking that this IP will end up on an AVR32 platform as
well, so I intentionally tried to avoid making the driver too ARM
specific. However, I definitely see the point of specifying
ARCH_AT91SAM9RL and worrying about adding additional support for new
platforms later, so I'll add that in.
> > +/* These values are dependent upon the performance of the ADC. Ideally,
> > + * These should be as close to the startup time and debounce time as
> > + * possible (without going over). These assume an optimally setup ADC as
> > + * per the electrical characteristics of the AT91SAM9RL tsadcc module
> > + */
> > +#define TS_POLL_DELAY (1 * 1000000) /* ns delay before the first sample */
> > +#define TS_POLL_PERIOD (5 * 1000000) /* ns delay between samples */
>
> So 1ms and 5ms... Not particularly high resolution...
>
> > +static enum hrtimer_restart atmel_tsadcc_timer(struct hrtimer *handle)
>
> So this uses the highres timer infrastructure. Does this build if
> CONFIG_HIGH_RES_TIMERS is not set?
>
Thank you for catching this. I'll definitely revisit this. Since HRT
support is not mainline for the SAM9 platforms, I'm going to remove all
references to it and worry about high resolution timer support at a
later time.
> > + /* Remap Register Memory */
> > + res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> > + ts->reg_start = res->start;
> > + ts->reg_length = res->end - res->start +1;
>
> So if no memory resources were passed, this oopses.
Ouch, sorry about that. I'll get a check in there.
I'll also take care of the whitespace issues and #defines as well.
-Justin Waters
next prev parent reply other threads:[~2008-04-25 21:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-25 18:56 [PATCH 0/2] Atmel AT91SAM9RL Touchscreen Driver Justin Waters
2008-04-25 18:56 ` [PATCH 1/2] atmel_tsadcc: Device driver for AT91SAM9RL Touchscreen Justin Waters
2008-04-25 18:56 ` [PATCH 2/2] atmel_tsadcc: Add board specific information for touchscreen driver Justin Waters
2008-04-25 22:29 ` Andrew Victor
2008-04-25 20:34 ` [PATCH 1/2] atmel_tsadcc: Device driver for AT91SAM9RL Touchscreen Dmitry Torokhov
2008-04-25 21:10 ` Russell King - ARM Linux
2008-04-25 21:37 ` Justin Waters [this message]
2008-04-25 22:52 ` David Brownell
2008-06-05 13:49 ` Haavard Skinnemoen
2008-04-25 22:16 ` Andrew Victor
2008-04-28 5:55 ` Uwe Kleine-König
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=1209159453.6990.48.camel@justin-linux \
--to=justin.waters@timesys.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-input@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=linux@maxim.org.za \
/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).