From: Taniya Das <taniya.das@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: kernel@oss.qualcomm.com, Pankaj Patil <quic_pankpati@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>,
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>,
Taniya Das <quic_tdas@quicinc.com>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/7] dt-bindings: clock: qcom: Document the Glymur TCSR Clock Controller
Date: Wed, 6 Aug 2025 15:27:26 +0530 [thread overview]
Message-ID: <5d75904a-05f5-4cee-9ff3-821b692f6a6f@oss.qualcomm.com> (raw)
In-Reply-To: <48610dd9-16c0-48ec-9997-2de9e0f7b3b6@kernel.org>
On 8/1/2025 2:40 PM, Krzysztof Kozlowski wrote:
> On 01/08/2025 06:14, Taniya Das wrote:
>>
>>
>> On 7/30/2025 12:47 PM, Krzysztof Kozlowski wrote:
>>> On Tue, Jul 29, 2025 at 11:12:36AM +0530, Taniya Das wrote:
>>>> Add bindings documentation for the Glymur TCSR Clock Controller.
>>>
>>> Same question as for v1, what is Glymur?
>>
>> Glymur is the Qualcomm's next gen compute SoC.
>
> Explain it in at least one commit msg, not in reply to me.
>
Yes, I will explain it in my next patchset.
>>
>>>
>>> Where is any DTS using this (or explanation of lack of DTS)?
>>>
>>
>> Krzysztof, the DTS will be posted separately once the driver and
>> bindings are reviewed.
>
> Hm? That's not what I was told thus I ask. I am sure that above is not
> true, but if you insist and put it that way it is incorrect. You cannot
> send DTS because you wait with drivers to be reviewed. We want to see
> entire picture.
>
Sorry for the confusion, Krzysztof. What I meant to convey is that we
plan to post the DTS after the public announcement of the SoC, which is
expected to happen within the next couple of months. In the meantime,
we’re hoping to get the code reviewed.
--
Thanks,
Taniya Das
next prev parent reply other threads:[~2025-08-06 9:57 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 5:42 [PATCH v3 0/7] Add support for Clock controllers for Glymur Taniya Das
2025-07-29 5:42 ` [PATCH v3 1/7] dt-bindings: clock: qcom-rpmhcc: Add support for Glymur SoCs Taniya Das
2025-07-30 7:15 ` Krzysztof Kozlowski
2025-07-29 5:42 ` [PATCH v3 2/7] dt-bindings: clock: qcom: Document the Glymur TCSR Clock Controller Taniya Das
2025-07-30 7:17 ` Krzysztof Kozlowski
2025-08-01 4:14 ` Taniya Das
2025-08-01 7:28 ` Dmitry Baryshkov
2025-08-01 9:10 ` Krzysztof Kozlowski
2025-08-04 9:01 ` Taniya Das
2025-08-06 9:57 ` Taniya Das [this message]
2025-08-06 10:00 ` Krzysztof Kozlowski
2025-07-29 5:42 ` [PATCH v3 3/7] clk: qcom: Add TCSR clock driver for Glymur Taniya Das
2025-07-29 10:49 ` Dmitry Baryshkov
2025-07-30 11:25 ` Abel Vesa
2025-08-01 4:32 ` Taniya Das
2025-08-01 5:31 ` Abel Vesa
2025-08-01 11:54 ` Konrad Dybcio
2025-08-04 9:00 ` Taniya Das
2025-08-04 9:36 ` Abel Vesa
2025-08-04 13:10 ` Konrad Dybcio
2025-08-04 14:21 ` Taniya Das
2025-08-06 10:04 ` Konrad Dybcio
2025-08-06 10:21 ` Taniya Das
2025-08-07 13:07 ` Konrad Dybcio
2025-08-08 9:54 ` Taniya Das
2025-07-29 5:42 ` [PATCH v3 4/7] clk: qcom: rpmh: Add support for Glymur rpmh clocks Taniya Das
2025-07-29 10:48 ` Dmitry Baryshkov
2025-07-29 5:42 ` [PATCH v3 5/7] clk: qcom: clk-alpha-pll: Add support for Taycan EKO_T PLL Taniya Das
2025-07-29 5:42 ` [PATCH v3 6/7] dt-bindings: clock: qcom: document the Glymur Global Clock Controller Taniya Das
2025-07-29 5:42 ` [PATCH v3 7/7] clk: qcom: gcc: Add support for " Taniya Das
2025-07-29 10:01 ` Konrad Dybcio
2025-07-29 10:48 ` Dmitry Baryshkov
2025-07-29 10:49 ` Konrad Dybcio
2025-08-01 4:25 ` Taniya Das
2025-07-30 7:15 ` [PATCH v3 0/7] Add support for Clock controllers for Glymur Krzysztof Kozlowski
2025-07-31 10:25 ` Taniya Das
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=5d75904a-05f5-4cee-9ff3-821b692f6a6f@oss.qualcomm.com \
--to=taniya.das@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@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=quic_pankpati@quicinc.com \
--cc=quic_tdas@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
all inboxes | Powered by JetHome®