From: Stephen Boyd <sboyd@kernel.org>
To: Michael Turquette <mturquette@baylibre.com>,
Taniya Das <tdas@codeaurora.org>,
robh+dt@kernel.org
Cc: David Brown <david.brown@linaro.org>,
Rajendra Nayak <rnayak@codeaurora.org>,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 3/3] clk: qcom: Add Global Clock controller (GCC) driver for SC7180
Date: Fri, 04 Oct 2019 16:20:21 -0700 [thread overview]
Message-ID: <20191004232022.062A1215EA@mail.kernel.org> (raw)
In-Reply-To: <81a2fa46-a7e6-66a2-9649-009f22813c81@codeaurora.org>
Quoting Taniya Das (2019-10-04 10:39:31)
> Hi Stephen,
>
> On 10/3/2019 9:31 PM, Stephen Boyd wrote:
> > Quoting Taniya Das (2019-10-03 03:31:15)
> >> Hi Stephen,
> >>
> >> On 10/1/2019 8:08 PM, Stephen Boyd wrote:
> >>>
> >>> Why do you want to keep them critical and registered? I'm suggesting
> >>> that any clk that is marked critical and doesn't have a parent should
> >>> instead become a register write in probe to turn the clk on.
> >>>
> >> Sure, let me do a one-time enable from probe for the clocks which
> >> doesn't have a parent.
> >> But I would now have to educate the clients of these clocks to remove
> >> using them.
> >>
> >
> > If anyone is using these clks we can return NULL from the provider for
> > the specifier so that we indicate there isn't support for them in the
> > kernel. At least I hope that code path still works given all the recent
> > changes to clk_get().
> >
>
> Could you please confirm if you are referring to update the below?
I wasn't suggesting that explicitly but sure. Something like this would
be necessary to make clk_get() pass back a NULL pointer to the caller.
Does everything keep working with this change?
next prev parent reply other threads:[~2019-10-04 23:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 9:50 [PATCH v3 0/3] Add Global Clock controller (GCC) driver for SC7180 Taniya Das
2019-09-18 9:50 ` [PATCH v3 1/3] clk: qcom: rcg: update the DFS macro for RCG Taniya Das
2019-09-18 9:50 ` [PATCH v3 2/3] dt-bindings: clk: qcom: Add YAML schemas for the GCC clock bindings Taniya Das
2019-09-18 17:52 ` Matthias Kaehlcke
2019-09-23 6:33 ` Taniya Das
2019-09-27 17:27 ` Rob Herring
2019-10-14 10:16 ` Taniya Das
[not found] ` <20190918212614.448FC20882@mail.kernel.org>
2019-10-14 10:17 ` Taniya Das
2019-09-18 9:50 ` [PATCH v3 3/3] clk: qcom: Add Global Clock controller (GCC) driver for SC7180 Taniya Das
2019-09-19 11:08 ` Rajendra Nayak
2019-09-20 4:00 ` Taniya Das
2019-09-20 4:44 ` Rajendra Nayak
[not found] ` <20190918213946.DC03521924@mail.kernel.org>
2019-09-23 8:01 ` Taniya Das
2019-09-24 23:12 ` Stephen Boyd
2019-09-25 11:20 ` Taniya Das
2019-09-25 13:03 ` Stephen Boyd
2019-09-27 7:37 ` Taniya Das
2019-10-01 14:38 ` Stephen Boyd
2019-10-03 10:31 ` Taniya Das
2019-10-03 16:01 ` Stephen Boyd
2019-10-04 17:39 ` Taniya Das
2019-10-04 23:20 ` Stephen Boyd [this message]
2019-10-09 9:19 ` Taniya Das
2019-10-10 4:16 ` Stephen Boyd
2019-10-11 10:28 ` Taniya Das
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=20191004232022.062A1215EA@mail.kernel.org \
--to=sboyd@kernel.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=rnayak@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=tdas@codeaurora.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).