Linux clock framework development
 help / color / mirror / Atom feed
From: Taniya Das <quic_tdas@quicinc.com>
To: Bjorn Andersson <andersson@kernel.org>,
	Melody Olvera <quic_molvera@quicinc.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Trilok Soni <quic_tsoni@quicinc.com>,
	"Satya Durga Srinivasu Prabhala --cc=linux-arm-msm @ vger .
	kernel . org" <quic_satyap@quicinc.com>,
	<linux-clk@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 5/7] clk: qcom: Add support for GCC clock controller on SM8750
Date: Wed, 6 Nov 2024 23:45:05 +0530	[thread overview]
Message-ID: <4b57566e-bcfa-4218-a4ba-8f1d49493df2@quicinc.com> (raw)
In-Reply-To: <4rp4h2inllsa2zd62yg6giyf45skhe3bzcgkjb5btwn4hhh33b@pdjllzwaqtks>



On 10/23/2024 9:30 AM, Bjorn Andersson wrote:
> On Mon, Oct 21, 2024 at 04:03:57PM GMT, Melody Olvera wrote:
> [..]
>> diff --git a/drivers/clk/qcom/gcc-sm8750.c b/drivers/clk/qcom/gcc-sm8750.c
> [..]
>> +static struct clk_regmap_mux gcc_pcie_0_pipe_clk_src = {
>> +	.reg = 0x6b080,
>> +	.shift = 0,
>> +	.width = 2,
>> +	.parent_map = gcc_parent_map_7,
>> +	.clkr = {
>> +		.hw.init = &(const struct clk_init_data) {
>> +			.name = "gcc_pcie_0_pipe_clk_src",
>> +			.parent_data = gcc_parent_data_7,
>> +			.num_parents = ARRAY_SIZE(gcc_parent_data_7),
>> +			.ops = &clk_regmap_mux_closest_ops,
> 
> Please confirm that the PCIe pipe clock sources should not be
> &clk_regmap_phy_mux_ops, as on other platforms.
> 

Yes Bjorn this will be fixed in the next series.

>> +		},
>> +	},
>> +};
>> +
> [..]
>> +static const struct freq_tbl ftbl_gcc_sdcc2_apps_clk_src[] = {
>> +	F(400000, P_BI_TCXO, 12, 1, 4),
>> +	F(25000000, P_GCC_GPLL0_OUT_EVEN, 12, 0, 0),
>> +	F(50000000, P_GCC_GPLL0_OUT_EVEN, 6, 0, 0),
>> +	F(100000000, P_GCC_GPLL0_OUT_EVEN, 3, 0, 0),
>> +	F(202000000, P_GCC_GPLL9_OUT_MAIN, 4, 0, 0),
>> +	{ }
>> +};
>> +
>> +static struct clk_rcg2 gcc_sdcc2_apps_clk_src = {
>> +	.cmd_rcgr = 0x1401c,
>> +	.mnd_width = 8,
>> +	.hid_width = 5,
>> +	.parent_map = gcc_parent_map_8,
>> +	.freq_tbl = ftbl_gcc_sdcc2_apps_clk_src,
>> +	.clkr.hw.init = &(const struct clk_init_data) {
>> +		.name = "gcc_sdcc2_apps_clk_src",
>> +		.parent_data = gcc_parent_data_8,
>> +		.num_parents = ARRAY_SIZE(gcc_parent_data_8),
>> +		.flags = CLK_SET_RATE_PARENT,
>> +		.ops = &clk_rcg2_shared_ops,
> 
> Please confirm that the sdcc apps_clk_src no longer needs to use
> &clk_rcg2_floor_ops.
> 

This too would be fixed in the next series.

>> +	},
>> +};
>> +
> [..]
>> +static struct gdsc gcc_pcie_0_gdsc = {
>> +	.gdscr = 0x6b004,
>> +	.en_rest_wait_val = 0x2,
>> +	.en_few_wait_val = 0x2,
>> +	.clk_dis_wait_val = 0xf,
>> +	.collapse_ctrl = 0x5214c,
>> +	.collapse_mask = BIT(0),
>> +	.pd = {
>> +		.name = "gcc_pcie_0_gdsc",
>> +	},
>> +	.pwrsts = PWRSTS_OFF_ON,
> 
> Shouldn't the PCIe GDSCs be PWRSTS_RET_ON?
> 

Not required.

>> +	.flags = POLL_CFG_GDSCR | RETAIN_FF_ENABLE | VOTABLE,
>> +};
>> +
> [..]
>> +static int gcc_sm8750_probe(struct platform_device *pdev)
>> +{
>> +	struct regmap *regmap;
>> +	int ret;
>> +
>> +	regmap = qcom_cc_map(pdev, &gcc_sm8750_desc);
>> +	if (IS_ERR(regmap))
>> +		return PTR_ERR(regmap);
>> +
>> +	ret = qcom_cc_register_rcg_dfs(regmap, gcc_dfs_clocks,
>> +				       ARRAY_SIZE(gcc_dfs_clocks));
>> +	if (ret)
>> +		return ret;
>> +
>> +	/*
>> +	 * Keep clocks always enabled:
>> +	 *	gcc_cam_bist_mclk_ahb_clk
>> +	 *	gcc_camera_ahb_clk
>> +	 *	gcc_camera_xo_clk
>> +	 *	gcc_disp_ahb_clk
>> +	 *	gcc_eva_ahb_clk
>> +	 *	gcc_eva_xo_clk
>> +	 *	gcc_gpu_cfg_ahb_clk
>> +	 *	gcc_pcie_rscc_cfg_ahb_clk
>> +	 *	gcc_pcie_rscc_xo_clk
>> +	 *	gcc_video_ahb_clk
>> +	 *	gcc_video_xo_clk
>> +	 */
>> +	regmap_update_bits(regmap, 0xa0004, BIT(0), BIT(0));
>> +	regmap_update_bits(regmap, 0x26004, BIT(0), BIT(0));
>> +	regmap_update_bits(regmap, 0x26034, BIT(0), BIT(0));
>> +	regmap_update_bits(regmap, 0x27004, BIT(0), BIT(0));
>> +	regmap_update_bits(regmap, 0x9f004, BIT(0), BIT(0));
>> +	regmap_update_bits(regmap, 0x9f01c, BIT(0), BIT(0));
>> +	regmap_update_bits(regmap, 0x71004, BIT(0), BIT(0));

>> +	regmap_update_bits(regmap, 0x52010, BIT(20), BIT(20));
>> +	regmap_update_bits(regmap, 0x52010, BIT(21), BIT(21));
These will still require to use the regmap_update_bits().

>> +	regmap_update_bits(regmap, 0x32004, BIT(0), BIT(0));
>> +	regmap_update_bits(regmap, 0x32038, BIT(0), BIT(0));
> 
> Any reason why qcom_branch_set_clk_en() can't be used here?
> 

Yes, I agree it is a miss.

>> +
>> +	/* FORCE_MEM_CORE_ON for ufs phy ice core clocks */
>> +	regmap_update_bits(regmap, gcc_ufs_phy_ice_core_clk.halt_reg,
>> +			   BIT(14), BIT(14));
> 
> qcom_branch_set_force_mem_core() ?
> 

It will be fixed.

> Regards,
> Bjorn
> 
>> +
>> +	return qcom_cc_really_probe(&pdev->dev, &gcc_sm8750_desc, regmap);
>> +}
>> +
>> +static struct platform_driver gcc_sm8750_driver = {
>> +	.probe = gcc_sm8750_probe,
>> +	.driver = {
>> +		.name = "gcc-sm8750",
>> +		.of_match_table = gcc_sm8750_match_table,
>> +	},
>> +};
>> +
>> +static int __init gcc_sm8750_init(void)
>> +{
>> +	return platform_driver_register(&gcc_sm8750_driver);
>> +}
>> +subsys_initcall(gcc_sm8750_init);
>> +
>> +static void __exit gcc_sm8750_exit(void)
>> +{
>> +	platform_driver_unregister(&gcc_sm8750_driver);
>> +}
>> +module_exit(gcc_sm8750_exit);
>> +
>> +MODULE_DESCRIPTION("QTI GCC SM8750 Driver");
>> +MODULE_LICENSE("GPL");
>> -- 
>> 2.46.1
>>

-- 
Thanks & Regards,
Taniya Das.

  reply	other threads:[~2024-11-06 18:15 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-21 23:03 [PATCH 0/7] clks: qcom: Introduce clks for SM8750 Melody Olvera
2024-10-21 23:03 ` [PATCH 1/7] dt-bindings: clock: qcom-rpmhcc: Add RPMHCC bindings " Melody Olvera
2024-10-22  6:16   ` Krzysztof Kozlowski
2024-11-06 18:14     ` Taniya Das
2024-10-21 23:03 ` [PATCH 2/7] clk: qcom: rpmh: Add support for SM8750 rpmh clocks Melody Olvera
2024-10-22  8:47   ` Bryan O'Donoghue
2024-11-06 18:14     ` Taniya Das
2024-10-23  3:40   ` Bjorn Andersson
2024-11-06 18:14     ` Taniya Das
2024-10-21 23:03 ` [PATCH 3/7] clk: qcom: clk-alpha-pll: Add support for controlling Taycan PLLs Melody Olvera
2024-10-23  3:48   ` Bjorn Andersson
2024-11-06 18:15     ` Taniya Das
2024-10-21 23:03 ` [PATCH 4/7] dt-bindings: clock: qcom: Add SM8750 GCC clock controller Melody Olvera
2024-10-22  6:18   ` Krzysztof Kozlowski
2024-11-06 18:14     ` Taniya Das
2024-10-23  3:52   ` Bjorn Andersson
2024-10-21 23:03 ` [PATCH 5/7] clk: qcom: Add support for GCC clock controller on SM8750 Melody Olvera
2024-10-23  4:00   ` Bjorn Andersson
2024-11-06 18:15     ` Taniya Das [this message]
2024-10-21 23:03 ` [PATCH 6/7] dt-bindings: clock: qcom: Document the SM8750 TCSR Clock Controller Melody Olvera
2024-10-23  8:15   ` Krzysztof Kozlowski
2024-10-21 23:03 ` [PATCH 7/7] clk: qcom: Add TCSR clock driver for SM8750 Melody Olvera
2024-10-23  3:30 ` [PATCH 0/7] clks: qcom: Introduce clks " 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=4b57566e-bcfa-4218-a4ba-8f1d49493df2@quicinc.com \
    --to=quic_tdas@quicinc.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=quic_molvera@quicinc.com \
    --cc=quic_satyap@quicinc.com \
    --cc=quic_tsoni@quicinc.com \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.org \
    /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