From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] pinctrl: move the core per-device handlers to core
Date: Thu, 9 Feb 2012 20:00:50 +0100 [thread overview]
Message-ID: <1328814050-22715-1-git-send-email-linus.walleij@linaro.org> (raw)
After discussing with some people involved with pin control, we agreed
that it will just cause trouble to have separate handles for pin muxing
and pin configuration in callers - they will definately want to set all
pin aspects regarding muxing and other configuration with one single
call.
These three patches take the first step in this transformation by moving
the per-device handles over to core code, and renaming all related
functions with the pinctrl_* prefix.
Linus Walleij (3):
pinctrl: break out a pinctrl consumer header
pinctrl: move generic functions to the pinctrl_ namespace
pinctrl: factor pin control handles over to the core
Documentation/pinctrl.txt | 124 ++++---
arch/arm/mach-u300/core.c | 24 +-
drivers/pinctrl/core.c | 602 +++++++++++++++++++++++++++++++-
drivers/pinctrl/core.h | 34 ++-
drivers/pinctrl/pinctrl-coh901.c | 6 +-
drivers/pinctrl/pinmux.c | 732 ++++++--------------------------------
drivers/pinctrl/pinmux.h | 67 ++++-
include/linux/pinctrl/consumer.h | 118 ++++++
include/linux/pinctrl/machine.h | 8 +-
include/linux/pinctrl/pinconf.h | 39 --
include/linux/pinctrl/pinmux.h | 52 ---
11 files changed, 991 insertions(+), 815 deletions(-)
create mode 100644 include/linux/pinctrl/consumer.h
--
1.7.7.6
next reply other threads:[~2012-02-09 19:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 19:00 Linus Walleij [this message]
2012-02-10 4:58 ` [PATCH 0/3] pinctrl: move the core per-device handlers to core Stephen Warren
2012-02-10 20:51 ` Linus Walleij
2012-02-11 6:18 ` Stephen Warren
2012-02-13 19:48 ` Linus Walleij
2012-02-13 20:01 ` Stephen Warren
2012-02-16 18:49 ` 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=1328814050-22715-1-git-send-email-linus.walleij@linaro.org \
--to=linus.walleij@linaro.org \
--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).