From: Raul Rangel <rrangel@chromium.org>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>,
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>
Subject: Re: [RFC] clk: Remove cached cores in parent map during unregister
Date: Tue, 17 Sep 2019 09:34:19 -0600 [thread overview]
Message-ID: <20190917153419.GA258455@google.com> (raw)
In-Reply-To: <20190826212415.ABD3521848@mail.kernel.org>
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?
Thanks
next prev parent reply other threads:[~2019-09-17 15:34 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 [this message]
2019-09-17 15:55 ` Sai Prakash Ranjan
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=20190917153419.GA258455@google.com \
--to=rrangel@chromium.org \
--cc=bjorn.andersson@linaro.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=saiprakash.ranjan@codeaurora.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 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.