From: Simon Budig <simon.budig@kernelconcepts.de>
To: Markus Niebel <list-09_linux_input@tqsc.de>, linux-input@vger.kernel.org
Subject: Re: [RFC] edt-ft5x06 - cannot see IRQ Qfrom device after DT probe
Date: Tue, 22 Jul 2014 15:47:55 +0200 [thread overview]
Message-ID: <53CE6B8B.20008@kernelconcepts.de> (raw)
In-Reply-To: <53CE3F84.5030301@tqsc.de>
[-- Attachment #1: Type: text/plain, Size: 1893 bytes --]
On 22/07/14 12:40, Markus Niebel wrote:
> 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.
Try looking at
Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt
There you have the "input-enable" generic property.
> 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.
The driver does not depend on the IRQ coming from a "real" CPU gpio. It
*could* be an external gpio expander or whatever (whether that is a good
idea is debatable of course). When I submitted the first version of the
driver it had bits in it to configure the pin properly. The feedback
basically was to remove that, because it made some assumptions that you
can map the IRQ to the relevant GPIO, which is not always possible.
I hope that helps.
(But really, your bootloader really should have a *very* good reason to
configure the touch irq pin as output - I have the impression that right
now there are two outputs driving against each other in your setup - not
healthy for the hardware).
Bye,
Simon
--
Simon Budig kernel concepts GmbH
simon.budig@kernelconcepts.de Sieghuetter Hauptweg 48
+49-271-771091-17 D-57072 Siegen
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2014-07-22 13:48 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
2014-07-22 13:47 ` Simon Budig [this message]
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=53CE6B8B.20008@kernelconcepts.de \
--to=simon.budig@kernelconcepts.de \
--cc=linux-input@vger.kernel.org \
--cc=list-09_linux_input@tqsc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.