From: damien.riegel.ext@parrot.com (Damien Riegel)
To: linux-arm-kernel@lists.infradead.org
Subject: Issue with gpio and pinmux
Date: Thu, 25 Jul 2013 16:42:59 +0200 [thread overview]
Message-ID: <51F13973.70806@parrot.com> (raw)
In-Reply-To: <CACRpkdb-hVE1Jj69ttrn+zf5cEuMHhxNh2OyhfTtrG+yUiO+jg@mail.gmail.com>
> Does this recently submitted documentation patch help in explaining
> some of your questions?
> http://marc.info/?l=linux-kernel&m=137442899829271&w=2
This is a very helpful addition to the existing documentation.
My reflection rather was: when gpio is not orthogonal, we could just
check mux_owner to see if pin is available; and when it is, use the
current implementation.
But well, we obviously need to way to tell if gpios are orthogonal or
not, and adding a function to struct pinmux_ops is an elegant solution
to do so since it even allows a pin granularity.
I guess I sent my previous mail a bit too quickly.
next prev parent reply other threads:[~2013-07-25 14:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 9:45 Issue with gpio and pinmux Damien Riegel
2013-07-18 18:11 ` Stephen Warren
2013-07-20 22:44 ` Linus Walleij
2013-07-21 3:44 ` Stephen Warren
2013-07-22 8:35 ` Christian Ruppert
2013-07-23 15:47 ` Stephen Warren
2013-07-26 9:26 ` Christian Ruppert
2013-07-25 9:37 ` Linus Walleij
2013-07-25 13:20 ` Damien Riegel
2013-07-25 13:24 ` Linus Walleij
2013-07-25 14:42 ` Damien Riegel [this message]
2013-07-25 15:06 ` Linus Walleij
2013-07-26 9:26 ` Christian Ruppert
2013-07-26 16:01 ` Stephen Warren
2013-07-26 22:39 ` Linus Walleij
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=51F13973.70806@parrot.com \
--to=damien.riegel.ext@parrot.com \
--cc=linux-arm-kernel@lists.infradead.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).