linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] improved support for runtime muxing for pinctrl
Date: Tue, 16 Jul 2013 02:05:24 -0700	[thread overview]
Message-ID: <20130716090310.5541.36777.stgit@localhost> (raw)

Hi all,

As discussed earlier, the pinctrl support for changing some of the
consumer device pins during runtime needs some improvment.

Here are the patches to do that, I'll also post a minimal sample
patch as a reply to this thread on how to do the muxing for
runtime PM.

Regards,

Tony

---

Tony Lindgren (4):
      pinctrl: Remove duplicate code in pinctrl_pm_select_state functions
      pinctrl: Allow pinctrl to have multiple active states
      pinctrl: Add support for additional dynamic states
      drivers: Add pinctrl handling for dynamic pin states


 drivers/base/pinctrl.c                |   39 +++++
 drivers/pinctrl/core.c                |  250 ++++++++++++++++++++++++++++-----
 drivers/pinctrl/core.h                |   10 +
 include/linux/pinctrl/consumer.h      |   46 ++++++
 include/linux/pinctrl/devinfo.h       |    4 +
 include/linux/pinctrl/pinctrl-state.h |   15 ++
 6 files changed, 321 insertions(+), 43 deletions(-)

-- 
Signature

             reply	other threads:[~2013-07-16  9:05 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-16  9:05 Tony Lindgren [this message]
2013-07-16  9:05 ` [PATCH 1/4] pinctrl: Remove duplicate code in pinctrl_pm_select_state functions Tony Lindgren
2013-07-16 13:15   ` Grygorii Strashko
2013-07-16 13:41     ` Tony Lindgren
2013-07-16 14:25       ` Grygorii Strashko
2013-07-17  6:31         ` Tony Lindgren
2013-07-16  9:05 ` [PATCH 2/4] pinctrl: Allow pinctrl to have multiple active states Tony Lindgren
2013-07-17 20:55   ` Stephen Warren
2013-07-16  9:05 ` [PATCH 3/4] pinctrl: Add support for additional dynamic states Tony Lindgren
2013-07-16  9:35   ` Felipe Balbi
2013-07-16 12:06     ` Tony Lindgren
2013-07-17 21:14   ` Stephen Warren
2013-07-18  7:25     ` Tony Lindgren
2013-07-18 10:53       ` Tony Lindgren
2013-07-18 19:21       ` Stephen Warren
2013-07-19  7:29         ` Tony Lindgren
2013-07-19 18:52           ` Stephen Warren
2013-07-29  9:05             ` Tony Lindgren
2013-07-29 22:01               ` Stephen Warren
2013-08-14 16:41                 ` Linus Walleij
2013-07-17 21:23   ` Stephen Warren
2013-07-18  7:36     ` Tony Lindgren
2013-07-18 19:26       ` Stephen Warren
2013-07-19  7:39         ` Tony Lindgren
2013-07-19 10:29           ` Grygorii Strashko
2013-07-19 19:03             ` Stephen Warren
2013-07-22 23:15               ` Linus Walleij
2013-07-29  9:08               ` Tony Lindgren
2013-07-19 18:58           ` Stephen Warren
2013-07-29  9:21             ` Tony Lindgren
2013-07-29 22:08               ` Stephen Warren
2013-07-22 23:07   ` Linus Walleij
2013-07-29  9:31     ` Tony Lindgren
2013-07-16  9:05 ` [PATCH 4/4] drivers: Add pinctrl handling for dynamic pin states Tony Lindgren
2013-07-17 21:21   ` Stephen Warren
2013-07-18  7:50     ` Tony Lindgren
2013-07-18 13:48       ` Tony Lindgren
2013-07-16  9:14 ` [PATCH 0/4] improved support for runtime muxing for pinctrl Tony Lindgren
2013-07-17 11:49 ` Grygorii Strashko

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=20130716090310.5541.36777.stgit@localhost \
    --to=tony@atomide.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).