From: valdis.kletnieks@vt.edu
To: Laurence Rochfort <laurence.rochfort@gmail.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Userspace configurable GPIO pinout
Date: Mon, 28 Jan 2019 16:05:36 -0500 [thread overview]
Message-ID: <4162.1548709536@turing-police.cc.vt.edu> (raw)
In-Reply-To: <CAMof6LALHJCuum-FPYArpGoKeSub91_oyPNc9fkpEgXyMJHsTQ@mail.gmail.com>
On Mon, 28 Jan 2019 13:26:55 +0000, Laurence Rochfort said:
> I'm writing a driver for an ePaper display, that will attach via GPIO.
>
> I've read the docs in Documentation/GPIO, and
> Documentation/devicetree/bindings/gpio.
>
> The ePaper itself just has a 34pin flat-flex cable, so people will have to
> use an adapter board to convert to the GPIO headers for a given system.
At that point, you're really stuck with "userspace gets to connect to 34 GPIO
pins and start bit-bashing". I don't think there's any sane way for a single driver
to claim 34 GPIO pins, especially when *which* 34 pins get claimed will depend
on what their system is and how the adapter board is wired.
Having said that, the problem then becomes telling userspace how the 34
pins are wired. About the only way to sort that out is if you're working for
the company that is building this, and you provide adapters for systems, and
a userspace installer program that says "Oh, this is a beaglebone/RPi/whatever,
so write a /etc/Epaper.conf file to match".
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2019-01-28 21:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 13:26 Userspace configurable GPIO pinout Laurence Rochfort
2019-01-28 21:05 ` valdis.kletnieks [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=4162.1548709536@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@kernelnewbies.org \
--cc=laurence.rochfort@gmail.com \
/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).