linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Taniya Das <taniya.das@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Pankaj Patil <pankaj.patil@oss.qualcomm.com>
Cc: sboyd@kernel.org, mturquette@baylibre.com, andersson@kernel.org,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	quic_rjendra@quicinc.com, linux-clk@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/7] clk: qcom: Add TCSR clock driver for Glymur
Date: Fri, 18 Jul 2025 22:36:40 +0530	[thread overview]
Message-ID: <0057e05d-efb6-4114-9a3e-f1166a8e99a8@oss.qualcomm.com> (raw)
In-Reply-To: <vawtojqbjrtoso4pjoza7vpaiog37hu6gbt7g6mmwbnmwladtx@ebh4amrwxwkk>



On 7/16/2025 9:05 PM, Dmitry Baryshkov wrote:
> On Wed, Jul 16, 2025 at 08:50:13PM +0530, Pankaj Patil wrote:

>>
>> +
>> +static int tcsr_cc_glymur_probe(struct platform_device *pdev)
>> +{
>> +	struct regmap *regmap;
>> +
>> +	regmap = qcom_cc_map(pdev, &tcsr_cc_glymur_desc);
>> +	if (IS_ERR(regmap))
>> +		return PTR_ERR(regmap);
>> +
>> +	return qcom_cc_really_probe(&pdev->dev, &tcsr_cc_glymur_desc, regmap);
> 
> This is just qcom_cc_probe();
> 

Will take care of it.

>> +}
>> +
>> +static struct platform_driver tcsr_cc_glymur_driver = {
>> +	.probe = tcsr_cc_glymur_probe,
>> +	.driver = {
>> +		.name = "tcsrcc-glymur",
>> +		.of_match_table = tcsr_cc_glymur_match_table,
>> +	},
>> +};
>> +
>> +static int __init tcsr_cc_glymur_init(void)
>> +{
>> +	return platform_driver_register(&tcsr_cc_glymur_driver);
>> +}
>> +subsys_initcall(tcsr_cc_glymur_init);
>> +
>> +static void __exit tcsr_cc_glymur_exit(void)
>> +{
>> +	platform_driver_unregister(&tcsr_cc_glymur_driver);
>> +}
>> +module_exit(tcsr_cc_glymur_exit);
>> +
>> +MODULE_DESCRIPTION("QTI TCSRCC GLYMUR Driver");
>> +MODULE_LICENSE("GPL");
>> -- 
>> 2.34.1
>>
> 

-- 
Thanks,
Taniya Das


  reply	other threads:[~2025-07-18 17:06 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-16 15:20 [PATCH 0/7] Add support for Clock controllers for Glymur Pankaj Patil
2025-07-16 15:20 ` [PATCH 1/7] dt-bindings: clock: qcom-rpmhcc: Add support for Glymur SoCs Pankaj Patil
2025-07-16 15:20 ` [PATCH 2/7] dt-bindings: clock: qcom: Add bindings documentation for the Glymur TCSR Pankaj Patil
2025-07-21  9:19   ` Krzysztof Kozlowski
2025-07-23  9:21     ` Taniya Das
2025-07-16 15:20 ` [PATCH 3/7] clk: qcom: Add TCSR clock driver for Glymur Pankaj Patil
2025-07-16 15:35   ` Dmitry Baryshkov
2025-07-18 17:06     ` Taniya Das [this message]
2025-07-16 15:20 ` [PATCH 4/7] clk: qcom: rpmh: Add support for Glymur rpmh clocks Pankaj Patil
2025-07-16 15:20 ` [PATCH 5/7] clk: qcom: clk-alpha-pll: Add support for Taycan EKO_T PLL Pankaj Patil
2025-07-16 15:36   ` Dmitry Baryshkov
2025-07-16 15:20 ` [PATCH 6/7] dt-bindings: clock: qcom: document the Glymur Global Clock Controller Pankaj Patil
2025-07-16 15:20 ` [PATCH 7/7] clk: qcom: gcc: Add support for " Pankaj Patil
2025-07-16 16:28   ` Krzysztof Kozlowski
2025-07-18 17:26     ` Taniya Das
2025-07-20  3:46     ` Bjorn Andersson
2025-07-20 12:18       ` Krzysztof Kozlowski
2025-07-22  3:28         ` Bjorn Andersson
2025-08-13 16:19         ` Greg KH
2025-08-14 22:51           ` Bjorn Andersson
2025-07-17  9:57   ` Abel Vesa
2025-07-17 10:08     ` Krzysztof Kozlowski
2025-07-18 17:37       ` Taniya Das
2025-07-20  4:00         ` Bjorn Andersson
2025-07-21 17:13           ` Taniya Das
2025-07-22  3:21             ` Bjorn Andersson
2025-07-16 16:12 ` [PATCH 0/7] Add support for Clock controllers for Glymur Krzysztof Kozlowski
2025-07-21  6:38   ` Pankaj Patil

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=0057e05d-efb6-4114-9a3e-f1166a8e99a8@oss.qualcomm.com \
    --to=taniya.das@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=pankaj.patil@oss.qualcomm.com \
    --cc=quic_rjendra@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;
as well as URLs for NNTP newsgroup(s).