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 15:20:41 +0200 [thread overview]
Message-ID: <51F12629.7090909@parrot.com> (raw)
In-Reply-To: <CACRpkdZdbxEt67+YBKif4-BKAToOmN0_c8HFOdjSG91dtJwJQw@mail.gmail.com>
I don't know about pinctrl background but I don't really get why there
is such a distinction between gpio and other functions in most cases.
I understand that on some arch a pin can be muxed and used as a gpio at
the same time. But on most arch, isn't gpio just another function that
can be muxed on a pin, and therefore we should check that a pin can be
requested as a gpio just by checking desc->mux_owner ?
next prev parent reply other threads:[~2013-07-25 13:20 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 [this message]
2013-07-25 13:24 ` Linus Walleij
2013-07-25 14:42 ` Damien Riegel
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=51F12629.7090909@parrot.com \
--to=damien.riegel.ext@parrot$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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