From: Stephen Warren <swarren@nvidia.com>
To: Linus Walleij <linus.walleij@stericsson.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Stephen Warren <swarren@nvidia.com>
Subject: [PATCH 1/3] pinctrl: Implement PINMUX_MAP_SYS_HOG
Date: Fri, 9 Dec 2011 16:59:03 -0700 [thread overview]
Message-ID: <1323475145-26430-1-git-send-email-swarren@nvidia.com> (raw)
This is the same as PINMUX_MAP_PRIMARY_SYS_HOG, except that it allows
you to specify a particular control device.
Signed-off-by: Stephen Warren <swarren@nvidia.com>
---
include/linux/pinctrl/machine.h | 8 ++++++++
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/include/linux/pinctrl/machine.h b/include/linux/pinctrl/machine.h
index f537231..0ca32eb 100644
--- a/include/linux/pinctrl/machine.h
+++ b/include/linux/pinctrl/machine.h
@@ -66,6 +66,14 @@ struct pinmux_map {
{ .name = a, .ctrl_dev_name = b, .function = c }
/*
+ * Convenience macro to map a system function onto a certain pinctrl device,
+ * to be hogged by the pinmux core until the system shuts down.
+ */
+#define PINMUX_MAP_SYS_HOG(a, b, c) \
+ { .name = a, .ctrl_dev_name = b, .function = c, \
+ .hog_on_boot = true }
+
+/*
* Convenience macro to map a function onto the primary device pinctrl device
* this is especially helpful on systems that have only one pin controller
* or need to set up a lot of mappings on the primary controller.
--
1.7.0.4
next reply other threads:[~2011-12-09 23:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 23:59 Stephen Warren [this message]
2011-12-09 23:59 ` [PATCH 2/3] arm/u300: Don't use PINMUX_MAP_PRIMARY* Stephen Warren
2011-12-09 23:59 ` [PATCH 3/3] pinctrl: Don't create a device for each pin controller Stephen Warren
2011-12-12 12:52 ` Linus Walleij
2011-12-12 12:39 ` [PATCH 1/3] pinctrl: Implement PINMUX_MAP_SYS_HOG 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=1323475145-26430-1-git-send-email-swarren@nvidia.com \
--to=swarren@nvidia.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®