Date: Wed, 23 May 2012 17:03:33 +0200 (CEST)
From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: Stephen Warren <swarren@wwwdotorg.org>
cc: Linus Walleij <linus.walleij@linaro.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pinctrl: add a pinctrl_mux_group_selected() function
In-Reply-To: <4FBCF9F0.1010901@wwwdotorg.org>
Message-ID: <Pine.LNX.4.64.1205231659310.21980@axis700.grange>
References: <Pine.LNX.4.64.1205230020210.11851@axis700.grange>
 <4FBCF9F0.1010901@wwwdotorg.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1582
Lines: 39

On Wed, 23 May 2012, Stephen Warren wrote:

> 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.

Well, yes, we could tra to ask for each thinkable configuration and see 
which one(s) succeed, but that doesn't seem very optimal either, even if 
we only have 3 possibilities for now.

> What's the use case for this new functionality?

It's MMC. MMC interfaces can use 1, 4, or 8 data lines, depending on the 
board configuration. The board knows, that it has, say, only 4 data lines 
routed to the interface, so, it specifies the respective pinctrl 
configuration as default. Now in the driver we have to know how many 
data-lines are connected.

Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/