From: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] clk: qcom: Add defaults for desired arm64 drivers
Date: Thu, 16 Apr 2026 10:36:35 +0200 [thread overview]
Message-ID: <a19a487a-a896-41fc-bc5b-1476e2b5dfbc@oss.qualcomm.com> (raw)
In-Reply-To: <357baf04-44ed-4d79-896e-16b7063fbbee@oss.qualcomm.com>
On 16/04/2026 10:30, Konrad Dybcio wrote:
> On 4/16/26 10:10 AM, Krzysztof Kozlowski wrote:
>> Clock controller drivers are essential for booting up SoCs and are not
>> really optional for a given platform. Kernel should not ask users
>> choice of drivers when that choice is obvious and known to the
>> developers that answer should be 'yes' or 'module'.
>>
>> Enable drivers for upstreamed or being upstreamed SoCs, which are not
>> yed enabled in defconfig: Glymur, Nord, SC7180, SC8180X, SC8280XP,
>> SC7280, QDU1000, SM4450, SM7150, SM8150, SM8450, SM6125, SM6375. Note
>> that main GCC clock controller drivers are usually already enabled for
>> these.
>>
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
>> ---
>
> [...]
>
>> tristate "Nord Global Clock Controller"
>> depends on ARM64 || COMPILE_TEST
>> select QCOM_GDSC
>> + default ARCH_QCOM
>> help
>> Support for the global clock controller on Nord devices.
>> Say Y if you want to use peripheral devices such as UART,
>
> So Nord GCC is "desired", but Kaanapali GCC is "important"? ;)
The difference is only what was already in defconfig thus which change
has impact on autoconf.h.
There is no upstream user of Nord GCC, thus I would not call it
important yet. I predict there will be such user, thus it is desired
just like every new SoC.
>
> In any case, as far as I'm concerned patches 2 and 3 could be one
Much easier to test impact on autoconf and resulted image when changes
supposedly transparent are really separate.
>
> Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-04-16 8:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 8:10 [PATCH 0/4] clk: qcom: Add sane defaults and drop defconfig Krzysztof Kozlowski
2026-04-16 8:10 ` [PATCH 1/4] clk: qcom: Restrict IPQ5424, IPQ6018,IPQ9574, QCM2290 and others to ARM64 Krzysztof Kozlowski
2026-04-18 20:23 ` Dmitry Baryshkov
2026-04-16 8:10 ` [PATCH 2/4] clk: qcom: Make important arm64 drivers default Krzysztof Kozlowski
2026-04-16 8:12 ` Krzysztof Kozlowski
2026-04-16 8:28 ` Konrad Dybcio
2026-04-16 8:33 ` Krzysztof Kozlowski
2026-04-16 8:10 ` [PATCH 3/4] clk: qcom: Add defaults for desired arm64 drivers Krzysztof Kozlowski
2026-04-16 8:30 ` Konrad Dybcio
2026-04-16 8:36 ` Krzysztof Kozlowski [this message]
2026-04-16 8:10 ` [PATCH 4/4] arm64: defconfig: Switch Qualcomm SDM845, SM8150 and SM8250 drivers to modules Krzysztof Kozlowski
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=a19a487a-a896-41fc-bc5b-1476e2b5dfbc@oss.qualcomm.com \
--to=krzysztof.kozlowski@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--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