From: Alexander Stein <alexanders83@web.de>
To: linux-input@vger.kernel.org
Subject: GPIO-muxed inputs
Date: Fri, 01 Aug 2014 13:49:44 +0200 [thread overview]
Message-ID: <2820612.QBnQEjqS39@kongar> (raw)
Hi,
I have a custom board which has 2 DIP switches connected to some GPIOs. I think I could use gpio_tilt_polled to generate proper input events. But the twist here is, that those switches uses the same GPIOs but are muxed by an additional GPIO. I'm wondering how this can be solved. An idea would be to add i2c-mux like "bus" where each input device is connected to. I think this way you can block "users" of the muxing GPIO before they can switch that.
Is this a proper way to go? How should (optional feature) should be integrated? Any other ideas?
Best regards,
Alexander
reply other threads:[~2014-08-01 11:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2820612.QBnQEjqS39@kongar \
--to=alexanders83@web.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).