From: Krzysztof Kozlowski <krzk@kernel.org>
To: Abel Vesa <abel.vesa@oss.qualcomm.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>,
Luca Weiss <luca.weiss@fairphone.com>,
Taniya Das <taniya.das@oss.qualcomm.com>,
Taniya Das <quic_tdas@quicinc.com>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/6] dt-bindings: clock: qcom: document the Eliza Global Clock Controller
Date: Tue, 17 Feb 2026 11:31:51 +0100 [thread overview]
Message-ID: <d3dee7f6-987c-4d9e-9097-c08c800921cf@kernel.org> (raw)
In-Reply-To: <20260216-eliza-clocks-v3-1-8afc5a7e3a98@oss.qualcomm.com>
On 16/02/2026 14:43, Abel Vesa wrote:
> From: Taniya Das <taniya.das@oss.qualcomm.com>
>
> Add bindings documentation for the Global Clock Controller on Qualcomm
> Eliza SoC. Reuse the Milos bindings schema since the controller resources
> are exactly the same, even though the controllers are incompatible between
> them.
>
> Signed-off-by: Taniya Das <taniya.das@oss.qualcomm.com>
> Signed-off-by: Abel Vesa <abel.vesa@oss.qualcomm.com>
> ---
> .../devicetree/bindings/clock/qcom,milos-gcc.yaml | 9 +-
> include/dt-bindings/clock/qcom,eliza-gcc.h | 218 +++++++++++++++++++++
> 2 files changed, 225 insertions(+), 2 deletions(-)
>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-17 10:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 13:43 [PATCH v3 0/6] clk: qcom: Add support for basic clocks providers on Eliza SoC Abel Vesa
2026-02-16 13:43 ` [PATCH v3 1/6] dt-bindings: clock: qcom: document the Eliza Global Clock Controller Abel Vesa
2026-02-17 10:31 ` Krzysztof Kozlowski [this message]
2026-02-16 13:43 ` [PATCH v3 2/6] dt-bindings: clock: qcom: Document the Eliza TCSR " Abel Vesa
2026-02-16 13:43 ` [PATCH v3 3/6] dt-bindings: clock: qcom-rpmhcc: Add RPMHCC for Eliza Abel Vesa
2026-02-16 13:43 ` [PATCH v3 4/6] clk: qcom: rpmh: Add support for Eliza rpmh clocks Abel Vesa
2026-02-16 15:05 ` Konrad Dybcio
2026-02-16 17:14 ` Abel Vesa
2026-02-16 13:43 ` [PATCH v3 5/6] clk: qcom: Add support for Global clock controller on Eliza Abel Vesa
2026-02-16 15:38 ` Konrad Dybcio
2026-02-17 7:58 ` Abel Vesa
2026-02-17 10:15 ` Konrad Dybcio
2026-02-23 10:48 ` Abel Vesa
2026-02-16 15:57 ` Konrad Dybcio
2026-02-17 7:57 ` Abel Vesa
2026-02-17 9:26 ` Konrad Dybcio
2026-02-23 10:50 ` Abel Vesa
2026-02-17 13:50 ` Krzysztof Kozlowski
2026-02-16 13:43 ` [PATCH v3 6/6] clk: qcom: Add TCSR clock driver for Eliza Abel Vesa
2026-02-16 15:08 ` Konrad Dybcio
2026-02-17 2:10 ` kernel test robot
2026-02-17 7:53 ` Abel Vesa
2026-02-17 2:31 ` kernel test robot
2026-02-17 7:53 ` Abel Vesa
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=d3dee7f6-987c-4d9e-9097-c08c800921cf@kernel.org \
--to=krzk@kernel.org \
--cc=abel.vesa@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=luca.weiss@fairphone.com \
--cc=mturquette@baylibre.com \
--cc=quic_tdas@quicinc.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=taniya.das@oss.qualcomm.com \
/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