From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] pinctrl: reserve pins when states are activated
Date: Fri, 19 Oct 2012 11:10:19 -0700 [thread overview]
Message-ID: <20121019181019.GP4730@atomide.com> (raw)
In-Reply-To: <1350651909-5337-1-git-send-email-linus.walleij@stericsson.com>
* Linus Walleij <linus.walleij@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 this mean that we are now doing lots of extra
reserving and dropping of pins? Performance is important from
latency point of view for cases where we need to remux pins
constantly runtime PM.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Linus Walleij <linus.walleij@stericsson.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Stephen Warren <swarren@nvidia.com>,
Anmar Oueja <anmar.oueja@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
Patrice Chotard <patrice.chotard@st.com>,
Jean Nicolas Graux <jean-nicolas.graux@stericsson.com>,
Loic Pallardy <loic.pallardy@st.com>
Subject: Re: [PATCH v2] pinctrl: reserve pins when states are activated
Date: Fri, 19 Oct 2012 11:10:19 -0700 [thread overview]
Message-ID: <20121019181019.GP4730@atomide.com> (raw)
In-Reply-To: <1350651909-5337-1-git-send-email-linus.walleij@stericsson.com>
* Linus Walleij <linus.walleij@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 this mean that we are now doing lots of extra
reserving and dropping of pins? Performance is important from
latency point of view for cases where we need to remux pins
constantly runtime PM.
Regards,
Tony
next prev parent reply other threads:[~2012-10-19 18:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 13:05 [PATCH v2] pinctrl: reserve pins when states are activated Linus Walleij
2012-10-19 13:05 ` Linus Walleij
2012-10-19 14:51 ` Jean-Nicolas GRAUX
2012-10-19 14:51 ` Jean-Nicolas GRAUX
2012-10-19 16:18 ` Stephen Warren
2012-10-19 16:18 ` Stephen Warren
2012-10-19 18:10 ` Tony Lindgren [this message]
2012-10-19 18:10 ` Tony Lindgren
2012-10-22 8:21 ` Linus Walleij
2012-10-22 8:21 ` Linus Walleij
2012-10-22 19:07 ` Tony Lindgren
2012-10-22 19:07 ` Tony Lindgren
2012-10-23 8:58 ` Linus Walleij
2012-10-23 8:58 ` Linus Walleij
2012-10-22 20:30 ` Stephen Warren
2012-10-22 20:30 ` Stephen Warren
2012-10-23 9:31 ` Linus Walleij
2012-10-23 9:31 ` 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=20121019181019.GP4730@atomide.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.