Message ID | cover.1697781921.git.quic_varada@quicinc.com |
---|---|
Headers | show |
Series | Enable cpufreq for IPQ5332 & IPQ9574 | expand |
On Fri, Oct 20, 2023 at 12:39:47PM +0530, Viresh Kumar wrote: > On 20-10-23, 11:49, Varadarajan Narayanan wrote: > > Varadarajan Narayanan (9): > > cpufreq: qti: Enable cpufreq for ipq53xx > > cpufreq: qti: Introduce cpufreq for ipq95xx > > Can I pick just these two ? ipq53xx patch is dependent on the previous safe source switching patch, hence not safe to pick that. No -> cpufreq: qti: Enable cpufreq for ipq53xx Yes -> cpufreq: qti: Introduce cpufreq for ipq95xx Thanks Varada
On Fri, 20 Oct 2023 11:49:30 +0530, Varadarajan Narayanan wrote: > Depends On: > https://lore.kernel.org/lkml/20230913-gpll_cleanup-v2-6-c8ceb1a37680@quicinc.com/T/ > > This patch series aims to enable cpufreq for IPQ5332 and IPQ9574. > For IPQ5332, a minor enhancement to Stromer Plus ops and a safe > source switch is needed before cpu freq can be enabled. > > [...] Applied, thanks! [1/9] clk: qcom: config IPQ_APSS_6018 should depend on QCOM_SMEM commit: 6a15647d0adc686226045e8046369f34d6ab03ed [2/9] clk: qcom: clk-alpha-pll: introduce stromer plus ops commit: 84da48921a97cee3dd1391659e93ee01d122b78b [3/9] clk: qcom: apss-ipq-pll: Use stromer plus ops for stromer plus pll commit: 267e29198436a8cb6770213471f72502c895096a [4/9] clk: qcom: apss-ipq-pll: Fix 'l' value for ipq5332_pll_config commit: 5b7a4d3d2b33398330aef69e0ff5656273483587 [5/9] clk: qcom: apss-ipq6018: ipq5332: add safe source switch for a53pll commit: 00331227f42045314b3775957f2f7809fb3ac32f Best regards,
On 10/20/23 08:19, Varadarajan Narayanan wrote: > The config IPQ_APSS_6018 should depend on QCOM_SMEM, to > avoid the following error reported by 'kernel test robot' > > loongarch64-linux-ld: drivers/clk/qcom/apss-ipq6018.o: in function `apss_ipq6018_probe': > >> apss-ipq6018.c:(.text+0xd0): undefined reference to `qcom_smem_get_soc_id' > > Fixes: 5e77b4ef1b19 ("clk: qcom: Add ipq6018 apss clock controller") > Reported-by: kernel test robot <yujie.liu@intel.com> > Closes: https://lore.kernel.org/r/202310181650.g8THtfsm-lkp@intel.com/ > Signed-off-by: Varadarajan Narayanan <quic_varada@quicinc.com> > --- > v5: Update commit log with the error message > --- Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org> Konrad
On 10/20/23 08:19, Varadarajan Narayanan wrote: > The set rate and determine rate operations are different between > Stromer and Stromer Plus PLLs. Since the programming sequence is > different, the PLLs dont get configured properly and random, > inexplicable crash/freeze is seen. Hence, use stromer plus ops > for ipq_pll_stromer_plus. > > Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org> > Acked-by: Stephen Boyd <sboyd@kernel.org> > Fixes: c7ef7fbb1ccf ("clk: qcom: apss-ipq-pll: add support for IPQ5332") > Signed-off-by: Kathiravan T <quic_kathirav@quicinc.com> > Signed-off-by: Varadarajan Narayanan <quic_varada@quicinc.com> > --- Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org> Konrad
On Fri, 20 Oct 2023 11:49:30 +0530, Varadarajan Narayanan wrote: > Depends On: > https://lore.kernel.org/lkml/20230913-gpll_cleanup-v2-6-c8ceb1a37680@quicinc.com/T/ > > This patch series aims to enable cpufreq for IPQ5332 and IPQ9574. > For IPQ5332, a minor enhancement to Stromer Plus ops and a safe > source switch is needed before cpu freq can be enabled. > > [...] Applied, thanks! [7/9] arm64: dts: qcom: ipq5332: populate the opp table based on the eFuse commit: 62073bc9f1ecc0d91fc260e7ae380cbadd33e9fc [9/9] arm64: dts: qcom: ipq9574: populate the opp table based on the eFuse commit: b36074357baf2794c825ea1c145de1d22b15380b Best regards,
On 20-10-23, 13:33, Varadarajan Narayanan wrote: > On Fri, Oct 20, 2023 at 12:39:47PM +0530, Viresh Kumar wrote: > > On 20-10-23, 11:49, Varadarajan Narayanan wrote: > > > Varadarajan Narayanan (9): > > > cpufreq: qti: Enable cpufreq for ipq53xx > > > cpufreq: qti: Introduce cpufreq for ipq95xx > > > > Can I pick just these two ? > > ipq53xx patch is dependent on the previous safe source switching > patch, hence not safe to pick that. > > No -> cpufreq: qti: Enable cpufreq for ipq53xx > Yes -> cpufreq: qti: Introduce cpufreq for ipq95xx The patches don't apply cleanly. Please resend.
On Wed, Oct 25, 2023 at 11:55:08AM +0530, Viresh Kumar wrote: > On 20-10-23, 13:33, Varadarajan Narayanan wrote: > > On Fri, Oct 20, 2023 at 12:39:47PM +0530, Viresh Kumar wrote: > > > On 20-10-23, 11:49, Varadarajan Narayanan wrote: > > > > Varadarajan Narayanan (9): > > > > cpufreq: qti: Enable cpufreq for ipq53xx > > > > cpufreq: qti: Introduce cpufreq for ipq95xx > > > > > > Can I pick just these two ? > > > > ipq53xx patch is dependent on the previous safe source switching > > patch, hence not safe to pick that. > > > > No -> cpufreq: qti: Enable cpufreq for ipq53xx > > Yes -> cpufreq: qti: Introduce cpufreq for ipq95xx > > The patches don't apply cleanly. Please resend. Have posted v6 with just these two patches and rebased to latest top. Please pick that. Thanks Varada