linux-clk.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephan Gerhold <stephan.gerhold@linaro.org>
To: Bjorn Andersson <andersson@kernel.org>
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>,
	Taniya Das <quic_tdas@quicinc.com>,
	 Jagadeesh Kona <quic_jkona@quicinc.com>,
	 Konrad Dybcio <konradybcio@kernel.org>,
	Abel Vesa <abel.vesa@linaro.org>,
	 Johan Hovold <johan@kernel.org>,
	 Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
	 Stefan Schmidt <stefan.schmidt@linaro.org>,
	linux-arm-msm@vger.kernel.org,  linux-clk@vger.kernel.org,
	devicetree@vger.kernel.org,  linux-kernel@vger.kernel.org
Subject: [PATCH 2/6] clk: qcom: videocc-sm8550: Allow building without SM8550/SM8560 GCC
Date: Tue, 01 Jul 2025 19:28:34 +0200	[thread overview]
Message-ID: <20250701-x1e-videocc-v1-2-785d393be502@linaro.org> (raw)
In-Reply-To: <20250701-x1e-videocc-v1-0-785d393be502@linaro.org>

From the build perspective, the videocc-sm8550 driver doesn't depend on
having one of the GCC drivers enabled. It builds just fine without the GCC
driver. In practice, it doesn't make much sense to have it enabled without
the GCC driver, but currently this extra dependency is inconsistent with
most of the other VIDEOCC entries in Kconfig. This can easily cause
confusion when you see the VIDEOCC options for some of the SoCs but not for
all of them.

Let's just drop the depends line to allow building the videocc driver
independent of the GCC selection. Compile testing with randconfig will also
benefit from keeping the dependencies minimal.

Signed-off-by: Stephan Gerhold <stephan.gerhold@linaro.org>
---
 drivers/clk/qcom/Kconfig | 1 -
 1 file changed, 1 deletion(-)

diff --git a/drivers/clk/qcom/Kconfig b/drivers/clk/qcom/Kconfig
index 36d6e6e1e7f0162d53f02f39125f4593517e0dba..26752bd79f508612347ce79fd3693359d4dd656d 100644
--- a/drivers/clk/qcom/Kconfig
+++ b/drivers/clk/qcom/Kconfig
@@ -1391,7 +1391,6 @@ config SM_VIDEOCC_8350
 config SM_VIDEOCC_8550
 	tristate "SM8550 Video Clock Controller"
 	depends on ARM64 || COMPILE_TEST
-	depends on SM_GCC_8550 || SM_GCC_8650
 	select QCOM_GDSC
 	help
 	  Support for the video clock controller on Qualcomm Technologies, Inc.

-- 
2.49.0


  parent reply	other threads:[~2025-07-01 17:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-01 17:28 [PATCH 0/6] clk: qcom: Add video clock controller and resets for X1E80100 Stephan Gerhold
2025-07-01 17:28 ` [PATCH 1/6] dt-bindings: clock: qcom,sm8450-videocc: Document X1E80100 compatible Stephan Gerhold
2025-07-04 15:08   ` Bryan O'Donoghue
2025-07-08 16:17   ` Rob Herring (Arm)
2025-07-01 17:28 ` Stephan Gerhold [this message]
2025-07-04 15:08   ` [PATCH 2/6] clk: qcom: videocc-sm8550: Allow building without SM8550/SM8560 GCC Bryan O'Donoghue
2025-07-01 17:28 ` [PATCH 3/6] clk: qcom: videocc-sm8550: Add separate frequency tables for X1E80100 Stephan Gerhold
2025-07-04 15:24   ` Bryan O'Donoghue
2025-07-01 17:28 ` [PATCH 4/6] dt-bindings: clock: qcom,x1e80100-gcc: Add missing video resets Stephan Gerhold
2025-07-04 15:36   ` Bryan O'Donoghue
2025-07-08 16:21   ` Rob Herring (Arm)
2025-07-01 17:28 ` [PATCH 5/6] clk: qcom: gcc-x1e80100: " Stephan Gerhold
2025-07-04 15:36   ` Bryan O'Donoghue
2025-07-08 17:05   ` Konrad Dybcio
2025-07-01 17:28 ` [PATCH 6/6] arm64: dts: qcom: x1e80100: Add videocc Stephan Gerhold
2025-07-04 15:37   ` Bryan O'Donoghue
2025-07-08 17:01   ` Konrad Dybcio

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=20250701-x1e-videocc-v1-2-785d393be502@linaro.org \
    --to=stephan.gerhold@linaro.org \
    --cc=abel.vesa@linaro.org \
    --cc=andersson@kernel.org \
    --cc=bryan.odonoghue@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=johan@kernel.org \
    --cc=konradybcio@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=mturquette@baylibre.com \
    --cc=quic_jkona@quicinc.com \
    --cc=quic_tdas@quicinc.com \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=stefan.schmidt@linaro.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).