public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Linus Walleij <linus.walleij@linaro.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pinctrl: add a pinctrl_mux_group_selected() function
Date: Wed, 23 May 2012 08:53:36 -0600	[thread overview]
Message-ID: <4FBCF9F0.1010901@wwwdotorg.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1205230020210.11851@axis700.grange>

On 05/22/2012 04:23 PM, Guennadi Liakhovetski wrote:
> This patch adds a new function to allow clients to verify, whether a
> certain group is selected in the currently active setting or not.
> 
> Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
> ---
> 
> Maybe there is already a way to do this without adding a new function, I 
> haven't found one, hence this patch.

This function doesn't currently exist because it breaks the pinctrl
conceptual model, which is that devices ask pinctrl for certain settings
whenever they need them, rather than information flowing the other way.

What's the use case for this new functionality?

  reply	other threads:[~2012-05-23 14:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-22 22:23 [PATCH] pinctrl: add a pinctrl_mux_group_selected() function Guennadi Liakhovetski
2012-05-23 14:53 ` Stephen Warren [this message]
2012-05-23 15:03   ` Guennadi Liakhovetski
2012-05-23 15:26     ` Stephen Warren
2012-06-05 12:40       ` Linus Walleij
2012-06-05 16:07         ` Stephen Warren
2012-06-06 21:47           ` Linus Walleij
2012-06-07  2:05       ` Guennadi Liakhovetski
2012-06-07 11:28         ` Linus Walleij
2012-06-07 15:14           ` Guennadi Liakhovetski
2012-06-12 11:13             ` Linus Walleij
2012-06-07 16:25         ` Stephen Warren
2012-06-12 11:21           ` 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=4FBCF9F0.1010901@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=g.liakhovetski@gmx.de \
    --cc=linus.walleij@linaro.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