[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <160767062876.1580929.14564723998233527816@swboyd.mtv.corp.google.com>
Date: Thu, 10 Dec 2020 23:10:28 -0800
From: Stephen Boyd <sboyd@...nel.org>
To: Vinod Koul <vkoul@...nel.org>
Cc: linux-arm-msm@...r.kernel.org,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Vivek Aknurwar <viveka@...eaurora.org>,
Andy Gross <agross@...nel.org>,
Michael Turquette <mturquette@...libre.com>,
Rob Herring <robh+dt@...nel.org>,
Taniya Das <tdas@...eaurora.org>, linux-clk@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
Jeevan Shriram <jshriram@...eaurora.org>
Subject: Re: [PATCH v2 5/5] clk: qcom: gcc: Add clock driver for SM8350
Quoting Vinod Koul (2020-12-10 21:43:49)
> On 10-12-20, 12:43, Stephen Boyd wrote:
> > > +static struct clk_branch gcc_camera_ahb_clk = {
> > > + .halt_reg = 0x26004,
> > > + .halt_check = BRANCH_HALT_DELAY,
> > > + .hwcg_reg = 0x26004,
> > > + .hwcg_bit = 1,
> > > + .clkr = {
> > > + .enable_reg = 0x26004,
> > > + .enable_mask = BIT(0),
> > > + .hw.init = &(struct clk_init_data){
> > > + .name = "gcc_camera_ahb_clk",
> > > + .flags = CLK_IS_CRITICAL,
> >
> > Why is it critical? Can we just enable it in driver probe and stop
> > modeling it as a clk?
>
> it does not have a parent we control, yeah it would make sense to do
> that. Tanya do you folks agree ..?
>
Maybe it is needed for camera clk controller? Have to check other SoCs
and see if they're using it.
Powered by blists - more mailing lists