[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <162483810820.3259633.140425242172054700@swboyd.mtv.corp.google.com>
Date: Sun, 27 Jun 2021 16:55:08 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: Martin Botka <martin.botka@...ainline.org>
Cc: ~postmarketos/upstreaming@...ts.sr.ht,
konrad.dybcio@...ainline.org,
angelogioacchino.delregno@...ainline.org,
marijn.suijten@...ainline.org, jamipkettunen@...ainline.org,
Martin Botka <martin.botka@...ainline.org>,
Andy Gross <agross@...nel.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Michael Turquette <mturquette@...libre.com>,
Rob Herring <robh+dt@...nel.org>,
linux-arm-msm@...r.kernel.org, linux-clk@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 2/2] clk: qcom: Add SM6125 (TRINKET) GCC driver
Quoting Martin Botka (2021-06-05 05:10:38)
> From: Konrad Dybcio <konrad.dybcio@...ainline.org>
>
> Add the clocks supported in global clock controller, which clock the
> peripherals like BLSPs, SDCC, USB, MDSS etc. Register all the clocks
> to the clock framework for the clients to be able to request for them.
>
> Signed-off-by: Konrad Dybcio <konrad.dybcio@...ainline.org>
> Signed-off-by: Martin Botka <martin.botka@...ainline.org>
> ---
Applied to clk-next but there are a handful of clks in here that should
be boring register writes instead of modeled as clks. Basically whenever
there is a CLK_IS_CRITICAL flag and no parent we know it could just be
enabled during probe and ignored thereafter.
Powered by blists - more mailing lists