From: Markus Niebel <list-09_linux_input@tqsc.de>
To: linux-input@vger.kernel.org
Subject: [RFC] edt-ft5x06 - cannot see IRQ Qfrom device after DT probe
Date: Tue, 15 Jul 2014 19:43:57 +0200 [thread overview]
Message-ID: <53C5685D.1090008@tqsc.de> (raw)
Hallo,
working with said tochcontroller we found that the IRQ is not seen in the following scenario:
- bootloader uses pin as an output for some reason
- pin is configured as GPIO and as INT source via device tree
- driver loads correctly and communicates over I2C
- IRQs not seen by CPU becaus pin is still configured as output
- 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
Regards
Markus Niebel
next reply other threads:[~2014-07-15 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 17:43 Markus Niebel [this message]
2014-07-16 10:01 ` [RFC] edt-ft5x06 - cannot see IRQ Qfrom device after DT probe Simon Budig
2014-07-22 10:40 ` Markus Niebel
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=53C5685D.1090008@tqsc.de \
--to=list-09_linux_input@tqsc.de \
--cc=linux-input@vger.kernel.org \
/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).