From: "Heiko Stübner" <heiko@sntech.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Patrice Chotard <patrice.chotard.st@gmail.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/2] pinctrl: common handling of generic pinconfig props in dt
Date: Sun, 9 Jun 2013 01:59:05 +0200 [thread overview]
Message-ID: <201306090159.05383.heiko@sntech.de> (raw)
Hi Linus,
following your suggestions for a common handling of things like pulls in dt,
I've come up with the following solution - hopefully I've gotten the correct
meaning of your explanaitions.
It handles all the pinconfigs that either ignore the argument, or have very
simple one, like PIN_CONFIG_OUTPUT does.
I've also attached my current rockchip pinctrl driver to show how it is using
this currently.
Heiko Stuebner (2):
pinctrl: add devicetree constants for simple generic pnconfig options
pinctrl: add function to separate combined pinconfig values
.../bindings/pinctrl/pinctrl-bindings.txt | 9 +++
drivers/pinctrl/pinconf-generic.c | 61 ++++++++++++++++++++
drivers/pinctrl/pinconf.h | 6 ++
include/dt-bindings/pinctrl/pinconfig.h | 37 ++++++++++++
4 files changed, 113 insertions(+), 0 deletions(-)
create mode 100644 include/dt-bindings/pinctrl/pinconfig.h
--
1.7.2.3
next reply other threads:[~2013-06-08 23:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-08 23:59 Heiko Stübner [this message]
2013-06-08 23:59 ` [PATCH 1/2] pinctrl: add devicetree constants for simple generic pnconfig options Heiko Stübner
2013-06-09 0:00 ` [PATCH 2/2] pinctrl: add function to separate combined pinconfig values Heiko Stübner
2013-06-09 0:01 ` [EXAMPLE PATCH] pinctrl: add pinctrl driver for Rockchip SoCs Heiko Stübner
2013-06-10 12:55 ` Linus Walleij
2013-06-10 13:00 ` Linus Walleij
2013-06-10 13:10 ` Heiko Stübner
2013-06-10 13:35 ` [PATCH v2] " Heiko Stübner
2013-06-10 13:40 ` [EXAMPLE PATCH] " Linus Walleij
2013-06-10 18:23 ` Stephen Warren
2013-06-10 19:53 ` Rob Herring
2013-06-11 8:50 ` Linus Walleij
2013-06-10 12:52 ` [PATCH 0/2] pinctrl: common handling of generic pinconfig props in dt Linus Walleij
2013-06-10 13:06 ` Heiko Stübner
2013-06-10 13:39 ` Linus Walleij
2013-06-10 13:54 ` Heiko Stübner
2013-06-10 14:08 ` 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=201306090159.05383.heiko@sntech.de \
--to=heiko@sntech.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrice.chotard.st@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