From: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
To: Raul Rangel <rrangel@chromium.org>
Cc: Stephen Boyd <sboyd@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, Rob Clark <robclark@gmail.com>,
Sean Paul <seanpaul@chromium.org>,
linux-arm-msm-owner@vger.kernel.org
Subject: Re: [RFC] clk: Remove cached cores in parent map during unregister
Date: Tue, 17 Sep 2019 21:25:27 +0530 [thread overview]
Message-ID: <da08fdaeaadd9b7b818f1b72535df94f@codeaurora.org> (raw)
In-Reply-To: <20190917153419.GA258455@google.com>
On 2019-09-17 21:04, Raul Rangel wrote:
> On Mon, Aug 26, 2019 at 02:24:14PM -0700, Stephen Boyd wrote:
>> >
>> > ---8<---
>> > diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
>> > index c0990703ce54..f42a803fb11a 100644
>> > --- a/drivers/clk/clk.c
>> > +++ b/drivers/clk/clk.c
>> > @@ -3737,6 +3737,37 @@ static const struct clk_ops clk_nodrv_ops = {
>> > .set_parent = clk_nodrv_set_parent,
>> > };
>> >
>> > +static void clk_core_evict_parent_cache_subtree(struct clk_core *root,
>> > + struct clk_core *target)
>> > +{
>> > + int i;
>> > + struct clk_core *child;
>> > +
>> > + if (!root)
>> > + return;
>>
>> I don't think we need this part. Child is always a valid pointer.
>>
>
> Bjorn or Saiprakash
> Are there any plans to send out Stephen's proposed patch?
>
Stephen has already sent out an updated patch for this here:
https://lore.kernel.org/lkml/20190828181959.204401-1-sboyd@kernel.org/
Thanks,
Sai
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a
member
of Code Aurora Forum, hosted by The Linux Foundation
prev parent reply other threads:[~2019-09-17 15:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 5:14 [RFC] clk: Remove cached cores in parent map during unregister Bjorn Andersson
2019-07-29 22:46 ` Stephen Boyd
2019-08-21 18:10 ` Stephen Boyd
2019-08-21 18:42 ` saiprakash.ranjan
2019-08-26 21:24 ` Stephen Boyd
2019-09-17 15:34 ` Raul Rangel
2019-09-17 15:55 ` Sai Prakash Ranjan [this message]
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=da08fdaeaadd9b7b818f1b72535df94f@codeaurora.org \
--to=saiprakash.ranjan@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-arm-msm-owner@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robclark@gmail.com \
--cc=rrangel@chromium.org \
--cc=sboyd@kernel.org \
--cc=seanpaul@chromium.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;
as well as URLs for NNTP newsgroup(s).