On Mon, Oct 22, 2012 at 10:30 PM, Stephen Warren wrote:
> On 10/22/2012 02:21 AM, Linus Walleij wrote:
>> If this turns out to be a severe performance bottleneck, I
>> suggest to add some additional constraint API, like
>> pinctrl_set_pinmux_homegeneous_pinsets(true) that will
>> at runtime
On Mon, Oct 22, 2012 at 9:07 PM, Tony Lindgren wrote:
> * Linus Walleij [121022 01:22]:
>> If this turns out to be a severe performance bottleneck, I
>> suggest to add some additional constraint API, like
>> pinctrl_set_pinmux_homegeneous_pinsets(true) that will
>> at runtime select whether the
On Mon, Oct 22, 2012 at 9:07 PM, Tony Lindgren t...@atomide.com wrote:
* Linus Walleij linus.wall...@linaro.org [121022 01:22]:
If this turns out to be a severe performance bottleneck, I
suggest to add some additional constraint API, like
pinctrl_set_pinmux_homegeneous_pinsets(true) that will
On Mon, Oct 22, 2012 at 10:30 PM, Stephen Warren swar...@wwwdotorg.org wrote:
On 10/22/2012 02:21 AM, Linus Walleij wrote:
If this turns out to be a severe performance bottleneck, I
suggest to add some additional constraint API, like
pinctrl_set_pinmux_homegeneous_pinsets(true) that will
at
On 10/22/2012 02:21 AM, Linus Walleij wrote:
> On Fri, Oct 19, 2012 at 8:10 PM, Tony Lindgren wrote:
>> [Me]
>>> Instead: let use reserve the pins when the state is activated
>>> and drop them when the state is disabled, i.e. when we move to
>>> another state. This way different devices/functions
* Linus Walleij [121022 01:22]:
> On Fri, Oct 19, 2012 at 8:10 PM, Tony Lindgren wrote:
> > [Me]
> >> Instead: let use reserve the pins when the state is activated
> >> and drop them when the state is disabled, i.e. when we move to
> >> another state. This way different devices/functions can use
On Fri, Oct 19, 2012 at 8:10 PM, Tony Lindgren wrote:
> [Me]
>> Instead: let use reserve the pins when the state is activated
>> and drop them when the state is disabled, i.e. when we move to
>> another state. This way different devices/functions can use the
>> same pins at different times.
>
>
On Fri, Oct 19, 2012 at 8:10 PM, Tony Lindgren t...@atomide.com wrote:
[Me]
Instead: let use reserve the pins when the state is activated
and drop them when the state is disabled, i.e. when we move to
another state. This way different devices/functions can use the
same pins at different
* Linus Walleij linus.wall...@linaro.org [121022 01:22]:
On Fri, Oct 19, 2012 at 8:10 PM, Tony Lindgren t...@atomide.com wrote:
[Me]
Instead: let use reserve the pins when the state is activated
and drop them when the state is disabled, i.e. when we move to
another state. This way
On 10/22/2012 02:21 AM, Linus Walleij wrote:
On Fri, Oct 19, 2012 at 8:10 PM, Tony Lindgren t...@atomide.com wrote:
[Me]
Instead: let use reserve the pins when the state is activated
and drop them when the state is disabled, i.e. when we move to
another state. This way different
* Linus Walleij [121019 06:09]:
>
> Instead: let use reserve the pins when the state is activated
> and drop them when the state is disabled, i.e. when we move to
> another state. This way different devices/functions can use the
> same pins at different times.
Hmm doesn't this mean that we are
On 10/19/2012 07:05 AM, Linus Walleij wrote:
> From: Linus Walleij
>
> This switches the way that pins are reserved for multiplexing:
>
> We used to do this when the map was parsed, at the creation of
> the settings inside the pinctrl handle, in pinmux_map_to_setting().
>
> However this does
Tested-by: Jean Nicolas Graux
Le 10/19/2012 03:05 PM, Linus WALLEIJ a écrit :
From: Linus Walleij
This switches the way that pins are reserved for multiplexing:
We used to do this when the map was parsed, at the creation of
the settings inside the pinctrl handle, in pinmux_map_to_setting().
From: Linus Walleij
This switches the way that pins are reserved for multiplexing:
We used to do this when the map was parsed, at the creation of
the settings inside the pinctrl handle, in pinmux_map_to_setting().
However this does not work for us, because we want to use the
same set of pins
From: Linus Walleij linus.wall...@linaro.org
This switches the way that pins are reserved for multiplexing:
We used to do this when the map was parsed, at the creation of
the settings inside the pinctrl handle, in pinmux_map_to_setting().
However this does not work for us, because we want to
Tested-by: Jean Nicolas Graux jean-nicolas.gr...@stericsson.com
Le 10/19/2012 03:05 PM, Linus WALLEIJ a écrit :
From: Linus Walleijlinus.wall...@linaro.org
This switches the way that pins are reserved for multiplexing:
We used to do this when the map was parsed, at the creation of
the
On 10/19/2012 07:05 AM, Linus Walleij wrote:
From: Linus Walleij linus.wall...@linaro.org
This switches the way that pins are reserved for multiplexing:
We used to do this when the map was parsed, at the creation of
the settings inside the pinctrl handle, in pinmux_map_to_setting().
* Linus Walleij linus.wall...@stericsson.com [121019 06:09]:
Instead: let use reserve the pins when the state is activated
and drop them when the state is disabled, i.e. when we move to
another state. This way different devices/functions can use the
same pins at different times.
Hmm doesn't
18 matches
Mail list logo
