From: Stefano Babic <sbabic@denx.de>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Stefano Babic <sbabic@denx.de>,
linux-input@vger.kernel.org,
Simon Budig <simon.budig@kernelconcepts.de>,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH] input: wrong irq requested in edt-ft5x06.c
Date: Thu, 20 Sep 2012 10:18:13 +0200 [thread overview]
Message-ID: <505AD145.8050204@denx.de> (raw)
In-Reply-To: <20120919165815.GB16286@core.coreip.homeip.net>
On 19/09/2012 18:58, Dmitry Torokhov wrote:
> Hi Stefano,
>
Hi Dmitry,
> On Wed, Sep 19, 2012 at 04:53:54PM +0200, Stefano Babic wrote:
>> The probe function checks for integrity the pdata->irq_pin,
>> but then does not request this line for interrupt.
>> For this reason, no interrupts are generated.
>>
>> Tested on a AM3517 board with EP0700M06
>
> Why is your board code does not set client->irq properly?
My concern is related that there are two different setup for the irq.
Near the client structure, the driver uses a an own platform data
structure edt_ft5x06_platform_data, where one filed is irq_pin. In whole
driver the pdata->irq_pin is used, and client->irq is used only for
requesting the irq.
But they contain the same information, as the irq number can be get easy
from irq_pin with gpio_to_irq(). Having both, it is possible to set them
to different values, and this is wrong.
Regards,
Stefano
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic@denx.de
=====================================================================
next prev parent reply other threads:[~2012-09-20 8:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 14:53 [PATCH] input: wrong irq requested in edt-ft5x06.c Stefano Babic
2012-09-19 16:58 ` Dmitry Torokhov
2012-09-20 8:18 ` Stefano Babic [this message]
2012-09-20 8:31 ` Simon Budig
2012-09-20 8:56 ` Stefano Babic
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=505AD145.8050204@denx.de \
--to=sbabic@denx.de \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=simon.budig@kernelconcepts.de \
/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).