From: Caleb Connolly <caleb@connolly.tech>
To: Dang Huynh <danct12@riseup.net>
Cc: Bjorn Andersson <andersson@kernel.org>,
Andy Gross <agross@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: qcom: sm6115: Select QCOM_GDSC
Date: Mon, 12 Sep 2022 13:16:47 +0000 [thread overview]
Message-ID: <0a2bb48f-c67d-0544-5037-d02f658a3351@connolly.tech> (raw)
In-Reply-To: <20220910170207.1592220-1-danct12@riseup.net>
On 10/09/2022 18:02, Dang Huynh wrote:
> While working on the Fxtec Pro1X device, this error shows up with
> my own minimal configuration:
>
> gcc-sm6115: probe of 1400000.clock-controller failed with error -38
>
> The clock driver depends on CONFIG_QCOM_GDSC and after enabling
> that, the driver probes successfully.
>
> Signed-off-by: Dang Huynh <danct12@riseup.net>
> ---
> drivers/clk/qcom/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/clk/qcom/Kconfig b/drivers/clk/qcom/Kconfig
> index 1cf1ef70e347..d566fbdebdf9 100644
> --- a/drivers/clk/qcom/Kconfig
> +++ b/drivers/clk/qcom/Kconfig
> @@ -645,6 +645,7 @@ config SM_DISPCC_6350
>
> config SM_GCC_6115
> tristate "SM6115 and SM4250 Global Clock Controller"
> + select QCOM_GDSC
depends on QCOM_GDSC
> help
> Support for the global clock controller on SM6115 and SM4250 devices.
> Say Y if you want to use peripheral devices such as UART, SPI,
> --
> 2.37.3
>
--
Kind Regards,
Caleb
next prev parent reply other threads:[~2022-09-12 13:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-10 17:02 Dang Huynh
2022-09-12 13:16 ` Caleb Connolly [this message]
2022-09-12 13:32 ` Dmitry Baryshkov
2022-09-12 13:42 ` Caleb Connolly
2022-09-12 13:33 ` Dmitry Baryshkov
2022-09-13 22:48 ` Bjorn Andersson
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=0a2bb48f-c67d-0544-5037-d02f658a3351@connolly.tech \
--to=caleb@connolly.tech \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=danct12@riseup.net \
--cc=konrad.dybcio@somainline.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=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®