From: Markus Niebel <list-09_linux_input@tqsc.de>
To: Simon Budig <simon.budig@kernelconcepts.de>, linux-input@vger.kernel.org
Subject: Re: [RFC] edt-ft5x06 - cannot see IRQ Qfrom device after DT probe
Date: Tue, 22 Jul 2014 12:40:04 +0200 [thread overview]
Message-ID: <53CE3F84.5030301@tqsc.de> (raw)
In-Reply-To: <53C64D86.1010808@kernelconcepts.de>
Am 16.07.2014 12:01, wrote Simon Budig:
> On 15/07/14 19:43, Markus Niebel wrote:
>> - when adding an int-gpios node to devicetree and parsing this gpio the gpio will be configured as input
>> - IRQ can be seen by CPU
>>
>> Question:
>>
>> - shall we add an int-gpio property to enable gpio pin config as input or
>
> Shouldn't it be possible to configure the pin as input directly from the
> device tree, indepently from the touch driver section?
I don't see, how to do that, maybe I did miss the right point.
I digged through the gpio code. There are drivers (gpio-omap) that make sure, that gpio is configured as
input and others that don't care (gpio-mxc / gpio-mxs).
seeing this I posted "gpio: gpio-mxc: make sure gpio is input when request IRQ" on linux-arm-kernel
Global question is: how can we make sure, that the driver that request the IRQ requests also the GPIO (implicit or like in the old platfrom data days explicit)? But thats beyond input devices and my knowledge.
Regards
Markus
>
> Bye,
> Simon
>
next prev parent reply other threads:[~2014-07-22 10:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 17:43 [RFC] edt-ft5x06 - cannot see IRQ Qfrom device after DT probe Markus Niebel
2014-07-16 10:01 ` Simon Budig
2014-07-22 10:40 ` Markus Niebel [this message]
2014-07-22 13:47 ` Simon Budig
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=53CE3F84.5030301@tqsc.de \
--to=list-09_linux_input@tqsc.de \
--cc=linux-input@vger.kernel.org \
--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).