[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <e44c751a-f0f5-42d8-aa99-743b349fdf9b@linaro.org>
Date: Sat, 28 Oct 2023 20:13:26 +0100
From: Bryan O'Donoghue <bryan.odonoghue@...aro.org>
To: Vincent Knecht <vincent.knecht@...loo.org>,
Andy Gross <agross@...nel.org>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konrad.dybcio@...aro.org>,
Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
Stephan Gerhold <stephan@...hold.net>,
linux-arm-msm@...r.kernel.org, linux-clk@...r.kernel.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH] clk: qcom: gcc-msm8939: Add missing CSI2 related clocks
On 28/10/2023 13:10, Vincent Knecht wrote:
> When adding in the indexes for this clock-controller we missed
> GCC_CAMSS_CSI2_AHB_CLK, GCC_CAMSS_CSI2_CLK, GCC_CAMSS_CSI2PHY_CLK,
> GCC_CAMSS_CSI2PIX_CLK and GCC_CAMSS_CSI2RDI_CLK.
>
> Add them in now.
>
> Signed-off-by: Vincent Knecht <vincent.knecht@...loo.org>
> ---
> No fixes tag because camss is a not-yet-enabled feature for msm8939.
>
> Also didn't rename ftbl_gcc_camss_csi0_1_clk now that csi2 uses it
> to avoid not-required-churn... should it be done anyway ?
An aesthetic choice with no right answer but, downstream calls it
ftbl_gcc_camss_csi0_1_2_clk,
maybe that's reasonable.
Assuming Krz's comments acted upon.
Reviewed-by: Bryan O'Donoghue <bryan.odonoghue@...aro.org>
Powered by blists - more mailing lists