From: Asier Llano Palacios <a.llano@usyscom.com>
To: Jamey Hicks <jamey.hicks@hp.com>
Subject: Re: gpio api
Date: Mon, 21 Feb 2005 11:02:24 +0100 [thread overview]
Message-ID: <1108980144.15299.16.camel@localhost.localdomain> (raw)
In-Reply-To: <4215F1A0.1030805@hp.com>
I think that implementing a GPIO interface is a must-have. And I also
think that your proposal is awesome. I work with GPIOs a lot, and I hate
not doing it in a cross-platform way.
I generally agree with your proposal but I see some missing behaviours.
Configuration that should be done on GPIOs.
- GPIO direction (input/output)
- GPIO modes (standard CMOS / open drain).
- GPIO interruption generation (by level or edge, high, low, raising,
falling)
The GPIOs requesting and numbering should be done by specifying the
chip, the port and the pin. We should be able to manipulate easily a
GPIO from one of 3 I2C chips and another one from our microprocessor.
We should be able to change several pins on the same port simultaneously
(if the driver of the port allows it). Maybe, all the operations should
be done by port (and not by pin), so that we can change several ports
simultaneously. We should be able to register several pins of a port,
and write and read from the port.
I'd like some comments about these features.
--
Asier Llano Palacios <a.llano@usyscom.com>
next prev parent reply other threads:[~2005-02-21 10:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-18 13:46 Jamey Hicks
2005-02-18 14:35 ` Jörn Engel
2005-02-21 10:02 ` Asier Llano Palacios [this message]
2005-02-21 10:18 ` Russell King
2005-02-22 2:18 ` Yoichi Yuasa
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=1108980144.15299.16.camel@localhost.localdomain \
--to=a.llano@usyscom.com \
--cc=jamey.hicks@hp.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
all inboxes | Powered by JetHome®