[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100624130942.GG26189@bnru02.bnr.st.com>
Date: Thu, 24 Jun 2010 18:39:43 +0530
From: Rabin VINCENT <rabin.vincent@...ricsson.com>
To: Luotao Fu <l.fu@...gutronix.de>
Cc: Samuel Ortiz <sameo@...ux.intel.com>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Linus WALLEIJ <linus.walleij@...ricsson.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-input@...r.kernel.org" <linux-input@...r.kernel.org>,
STEricsson_nomadik_linux <STEricsson_nomadik_linux@...t.st.com>
Subject: Re: [PATCH 4/6] mfd/stmpexxx: change touchscreen irq
On Thu, Jun 24, 2010 at 13:13:39 +0200, Luotao Fu wrote:
> the stmpe touchscreen driver uses fifo threshold irq to trigger data fetching.
> The touch_det irq bit is only used while polling for release. Change the
> platform resource and the irq definition in the variant block.
> ---
> drivers/mfd/stmpe-devices.c | 12 +++---------
> 1 files changed, 3 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/mfd/stmpe-devices.c b/drivers/mfd/stmpe-devices.c
> index fa6934d..3e21c26 100644
> --- a/drivers/mfd/stmpe-devices.c
> +++ b/drivers/mfd/stmpe-devices.c
> @@ -59,17 +59,11 @@ static struct mfd_cell stmpe_keypad_cell = {
>
> static struct resource stmpe_ts_resources[] = {
> {
> - .name = "TOUCH_DET",
> + .name = "FIFO_TH",
> .start = 0,
> .end = 0,
> .flags = IORESOURCE_IRQ,
> - },
> - {
> - .name = "FIFO_TH",
> - .start = 1,
> - .end = 1,
> - .flags = IORESOURCE_IRQ,
> - },
> + }
> };
>
> static struct mfd_cell stmpe_ts_cell = {
> @@ -107,7 +101,7 @@ static struct stmpe_variant_block stmpe811_blocks[] = {
> },
> {
> .cell = &stmpe_ts_cell,
> - .irq = STMPE811_IRQ_TOUCH_DET,
> + .irq = STMPE811_IRQ_FIFO_TH,
> .block = STMPE_BLOCK_TOUCHSCREEN,
> },
> };
Would it be clearer if you leave this as-is, and instead use
platform_get_irq_byname("FIFO_TH") in the stmpe-ts driver, since I think
the TSC block has a whole bunch of irqs?
Rabin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists