From: Javier Martinez Canillas <martinez.javier@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Kevin McNeely <kev@cypress.com>,
Henrik Rydberg <rydberg@euromail.se>,
Srikar <ext-srikar.1.bhavanarayana@nokia.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] Input: cyttsp - Cypress TTSP capacitive multi-touch screen support
Date: Sat, 03 Sep 2011 07:34:15 +0200 [thread overview]
Message-ID: <1315028055.11839.13.camel@sauron> (raw)
In-Reply-To: <20110822043107.GB23010@core.coreip.homeip.net>
Hello Dmitry,
On Sun, 2011-08-21 at 21:31 -0700, Dmitry Torokhov wrote:
> Hi Javier,
>
> Still reading through the patches, but have one question:
>
> > +
> > + ts->irq = gpio_to_irq(ts->platform_data->irq_gpio);
> > + if (ts->irq <= 0) {
> > + dev_dbg(ts->dev, "%s: Error, failed to allocate irq\n",
> > + __func__);
> > + goto error_init;
> > + }
>
> Why do we need to get gpio/irq from platform data instead of having
> board code set up controllers appropriately and use IRQ either from I2C
> client structure or from SPI?
>
> Thanks.
>
Right, next version fix this by extracting the IRQ either from the I2C
or SPI client data structure as you suggest.
Best regards,
Javier Martinez Canillas
next prev parent reply other threads:[~2011-09-03 5:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-20 4:01 Input: Cypress TTSP device driver Javier Martinez Canillas
2011-08-20 4:01 ` [PATCH 1/3] Input: cyttsp - Cypress TTSP capacitive multi-touch screen support Javier Martinez Canillas
2011-08-22 4:31 ` Dmitry Torokhov
2011-08-22 13:06 ` Javier Martinez Canillas
2011-09-03 5:34 ` Javier Martinez Canillas [this message]
2011-08-20 4:01 ` [PATCH 2/3] Input: cyttsp - add support for Cypress TTSP touchscreen I2C bus interface Javier Martinez Canillas
2011-08-20 4:01 ` [PATCH 3/3] Input: cyttsp - add support for Cypress TTSP touchscreen SPI " Javier Martinez Canillas
2011-08-22 2:44 ` Dmitry Torokhov
2011-09-03 5:31 ` Javier Martinez Canillas
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=1315028055.11839.13.camel@sauron \
--to=martinez.javier@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=ext-srikar.1.bhavanarayana@nokia.com \
--cc=gregkh@suse.de \
--cc=kev@cypress.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rydberg@euromail.se \
/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).