From: Taniya Das <taniya.das@oss.qualcomm.com>
To: Luca Weiss <luca.weiss@fairphone.com>,
Bjorn Andersson <andersson@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@somainline.org>
Cc: ~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] clk: qcom: camcc-sm6350: Add *_wait_val values for GDSCs
Date: Mon, 28 Apr 2025 23:07:53 +0530 [thread overview]
Message-ID: <2d85a2c0-8084-4bd3-b5f9-e7dfa8303b65@oss.qualcomm.com> (raw)
In-Reply-To: <20250425-sm6350-gdsc-val-v1-1-1f252d9c5e4e@fairphone.com>
On 4/25/2025 5:42 PM, Luca Weiss wrote:
> Compared to the msm-4.19 driver the mainline GDSC driver always sets the
> bits for en_rest, en_few & clk_dis, and if those values are not set
> per-GDSC in the respective driver then the default value from the GDSC
> driver is used. The downstream driver only conditionally sets
> clk_dis_wait_val if qcom,clk-dis-wait-val is given in devicetree.
>
> Correct this situation by explicitly setting those values. For all GDSCs
> the reset value of those bits are used.
>
> Fixes: 80f5451d9a7c ("clk: qcom: Add camera clock controller driver for SM6350")
> Signed-off-by: Luca Weiss <luca.weiss@fairphone.com>
> ---
> drivers/clk/qcom/camcc-sm6350.c | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/drivers/clk/qcom/camcc-sm6350.c b/drivers/clk/qcom/camcc-sm6350.c
> index 1871970fb046d7ad6f5b6bfcce9f8ae10b3f2e93..8aac97d29ce3ff0d12e7d09fe65fd51a5cb43c87 100644
> --- a/drivers/clk/qcom/camcc-sm6350.c
> +++ b/drivers/clk/qcom/camcc-sm6350.c
> @@ -1695,6 +1695,9 @@ static struct clk_branch camcc_sys_tmr_clk = {
>
> static struct gdsc bps_gdsc = {
> .gdscr = 0x6004,
> + .en_rest_wait_val = 0x2,
> + .en_few_wait_val = 0x2,
> + .clk_dis_wait_val = 0xf,
> .pd = {
> .name = "bps_gdsc",
> },
> @@ -1704,6 +1707,9 @@ static struct gdsc bps_gdsc = {
>
> static struct gdsc ipe_0_gdsc = {
> .gdscr = 0x7004,
> + .en_rest_wait_val = 0x2,
> + .en_few_wait_val = 0x2,
> + .clk_dis_wait_val = 0xf,
> .pd = {
> .name = "ipe_0_gdsc",
> },
> @@ -1713,6 +1719,9 @@ static struct gdsc ipe_0_gdsc = {
>
> static struct gdsc ife_0_gdsc = {
> .gdscr = 0x9004,
> + .en_rest_wait_val = 0x2,
> + .en_few_wait_val = 0x2,
> + .clk_dis_wait_val = 0xf,
> .pd = {
> .name = "ife_0_gdsc",
> },
> @@ -1721,6 +1730,9 @@ static struct gdsc ife_0_gdsc = {
>
> static struct gdsc ife_1_gdsc = {
> .gdscr = 0xa004,
> + .en_rest_wait_val = 0x2,
> + .en_few_wait_val = 0x2,
> + .clk_dis_wait_val = 0xf,
> .pd = {
> .name = "ife_1_gdsc",
> },
> @@ -1729,6 +1741,9 @@ static struct gdsc ife_1_gdsc = {
>
> static struct gdsc ife_2_gdsc = {
> .gdscr = 0xb004,
> + .en_rest_wait_val = 0x2,
> + .en_few_wait_val = 0x2,
> + .clk_dis_wait_val = 0xf,
> .pd = {
> .name = "ife_2_gdsc",
> },
> @@ -1737,6 +1752,9 @@ static struct gdsc ife_2_gdsc = {
>
> static struct gdsc titan_top_gdsc = {
> .gdscr = 0x14004,
> + .en_rest_wait_val = 0x2,
> + .en_few_wait_val = 0x2,
> + .clk_dis_wait_val = 0xf,
> .pd = {
> .name = "titan_top_gdsc",
> },
>
Reviewed-by: Taniya Das <quic_tdas@quicinc.com>
next prev parent reply other threads:[~2025-04-28 17:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 12:12 [PATCH 0/4] Add *_wait_val values for GDSCs in all SM6350 clock drivers Luca Weiss
2025-04-25 12:12 ` [PATCH 1/4] clk: qcom: camcc-sm6350: Add *_wait_val values for GDSCs Luca Weiss
2025-04-28 17:37 ` Taniya Das [this message]
2025-04-25 12:12 ` [PATCH 2/4] clk: qcom: dispcc-sm6350: " Luca Weiss
2025-04-28 17:39 ` Taniya Das
2025-04-25 12:12 ` [PATCH 3/4] clk: qcom: gcc-sm6350: " Luca Weiss
2025-04-28 17:39 ` Taniya Das
2025-04-25 12:12 ` [PATCH 4/4] clk: qcom: gpucc-sm6350: " Luca Weiss
2025-04-28 17:41 ` Taniya Das
2025-05-07 5:18 ` [PATCH 0/4] Add *_wait_val values for GDSCs in all SM6350 clock drivers Bjorn Andersson
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=2d85a2c0-8084-4bd3-b5f9-e7dfa8303b65@oss.qualcomm.com \
--to=taniya.das@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=angelogioacchino.delregno@somainline.org \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=mturquette@baylibre.com \
--cc=phone-devel@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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