From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] clk: Make __clk_lookup() use a list instead of tree search
Date: Thu, 4 Sep 2014 23:02:48 -0700 [thread overview]
Message-ID: <20140905060248.GA22593@codeaurora.org> (raw)
In-Reply-To: <1409880209-25094-1-git-send-email-sboyd@codeaurora.org>
On 09/04, Stephen Boyd wrote:
> In the near future we're going to move the prepare lock to be a
> per-clock ww_mutex. __clk_lookup() is called very deep in the
> set-rate path and we would like to avoid having to take all the
> locks in the clock tree to search for a clock (basically
> defeating the purpose of introducing per-clock locks). Introduce
> a new list that contains all clocks registered in the system and
> walk this list until the clock is found.
>
> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
> ---
Actually this won't work. We can't grab the list lock while the
prepare lock is held. So we need to do the debugfs stuff with a
different lock and do it outside of the prepare lock.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@codeaurora.org>
To: Rob Clark <robdclark@gmail.com>
Cc: Mike Turquette <mturquette@linaro.org>,
linux-arm-kernel@lists.infradead.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/2] clk: Make __clk_lookup() use a list instead of tree search
Date: Thu, 4 Sep 2014 23:02:48 -0700 [thread overview]
Message-ID: <20140905060248.GA22593@codeaurora.org> (raw)
In-Reply-To: <1409880209-25094-1-git-send-email-sboyd@codeaurora.org>
On 09/04, Stephen Boyd wrote:
> In the near future we're going to move the prepare lock to be a
> per-clock ww_mutex. __clk_lookup() is called very deep in the
> set-rate path and we would like to avoid having to take all the
> locks in the clock tree to search for a clock (basically
> defeating the purpose of introducing per-clock locks). Introduce
> a new list that contains all clocks registered in the system and
> walk this list until the clock is found.
>
> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
> ---
Actually this won't work. We can't grab the list lock while the
prepare lock is held. So we need to do the debugfs stuff with a
different lock and do it outside of the prepare lock.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2014-09-05 6:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 0:46 ccf vs iommu vs drm locking fun Rob Clark
2014-09-05 0:46 ` Rob Clark
2014-09-05 1:15 ` Stephen Boyd
2014-09-05 1:15 ` Stephen Boyd
2014-09-05 1:23 ` [PATCH 1/2] clk: Make __clk_lookup() use a list instead of tree search Stephen Boyd
2014-09-05 1:23 ` Stephen Boyd
2014-09-05 1:23 ` [PATCH 2/2] clk: Don't hold prepare_lock across debugfs creation Stephen Boyd
2014-09-05 1:23 ` Stephen Boyd
2014-09-05 6:02 ` Stephen Boyd [this message]
2014-09-05 6:02 ` [PATCH 1/2] clk: Make __clk_lookup() use a list instead of tree search Stephen Boyd
2014-09-05 6:37 ` [PATCH v2] clk: Don't hold prepare_lock across debugfs creation Stephen Boyd
2014-09-05 6:37 ` Stephen Boyd
2014-09-06 0:00 ` Stephen Boyd
2014-09-06 0:00 ` Stephen Boyd
2014-09-10 21:43 ` Mike Turquette
2014-09-10 21:43 ` Mike Turquette
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=20140905060248.GA22593@codeaurora.org \
--to=sboyd@codeaurora.org \
--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.