devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Dybcio <konradybcio@kernel.org>
To: 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>,
	 Rajendra Nayak <quic_rjendra@quicinc.com>,
	 Konrad Dybcio <konradybcio@kernel.org>,
	 Wesley Cheng <wesley.cheng@oss.qualcomm.com>,
	 Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
	 Sibi Sankar <quic_sibis@quicinc.com>,
	Abel Vesa <abel.vesa@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
	 devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	 Bryan O'Donoghue <bod@kernel.org>
Subject: [PATCH v2 0/3] X1E GCC USB4 clock fix-ups
Date: Fri, 03 Oct 2025 20:14:37 +0200	[thread overview]
Message-ID: <20251003-topic-hamoa_gcc_usb4-v2-0-61d27a14ee65@oss.qualcomm.com> (raw)

Some of the USB4 clock infrastructure has been left undescribed.

Following the example of Glymur, add all the required muxes and resets.

These changes have passed a smoke test with their intended usecase.

Signed-off-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
---
Changes in v2:
- pick up tags
- get rid of uncaught unused declarations
- Link to v1: https://lore.kernel.org/r/20250926-topic-hamoa_gcc_usb4-v1-0-25cad1700829@oss.qualcomm.com

---
Konrad Dybcio (3):
      dt-bindings: clock: qcom,x1e80100-gcc: Add missing USB4 clocks/resets
      clk: qcom: gcc-x1e80100: Add missing USB4 clocks/resets
      arm64: dts: qcom: x1e80100: Extend the gcc input clock list

 .../bindings/clock/qcom,x1e80100-gcc.yaml          |  62 +-
 arch/arm64/boot/dts/qcom/x1e80100.dtsi             |  29 +-
 drivers/clk/qcom/gcc-x1e80100.c                    | 698 ++++++++++++++++++++-
 include/dt-bindings/clock/qcom,x1e80100-gcc.h      |  61 ++
 4 files changed, 828 insertions(+), 22 deletions(-)
---
base-commit: 8e2755d7779a95dd61d8997ebce33ff8b1efd3fb
change-id: 20250926-topic-hamoa_gcc_usb4-35eb6741b141

Best regards,
-- 
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>


             reply	other threads:[~2025-10-03 18:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-03 18:14 Konrad Dybcio [this message]
2025-10-03 18:14 ` [PATCH v2 1/3] dt-bindings: clock: qcom,x1e80100-gcc: Add missing USB4 clocks/resets Konrad Dybcio
2025-10-03 18:14 ` [PATCH v2 2/3] clk: qcom: gcc-x1e80100: " Konrad Dybcio
2025-10-03 19:37   ` Dmitry Baryshkov
2025-10-07  8:36   ` Abel Vesa
2025-10-09  4:22   ` Taniya Das
2025-10-03 18:14 ` [PATCH v2 3/3] arm64: dts: qcom: x1e80100: Extend the gcc input clock list Konrad Dybcio
2025-10-03 19:38   ` Dmitry Baryshkov
2025-10-07  8:34   ` 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=20251003-topic-hamoa_gcc_usb4-v2-0-61d27a14ee65@oss.qualcomm.com \
    --to=konradybcio@kernel.org \
    --cc=abel.vesa@linaro.org \
    --cc=andersson@kernel.org \
    --cc=bod@kernel.org \
    --cc=bryan.odonoghue@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@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=quic_rjendra@quicinc.com \
    --cc=quic_sibis@quicinc.com \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=wesley.cheng@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;
as well as URLs for NNTP newsgroup(s).