From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Bjorn Andersson <quic_bjorande@quicinc.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>
Cc: linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Johan Hovold <johan@kernel.org>
Subject: Re: [PATCH] arm64: defconfig: Enable Qualcomm SC8280XP camera clock controller
Date: Fri, 22 Dec 2023 13:08:45 +0000 [thread overview]
Message-ID: <61998a14-2f9a-4b37-a6d0-77451332ae6f@linaro.org> (raw)
In-Reply-To: <20231221-enable-sc8280xp-camcc-v1-1-2249581dd538@quicinc.com>
On 22/12/2023 04:47, Bjorn Andersson wrote:
> With the camera clock controller added to the DeviceTree of SC8280XP the
> interconnect providers no longer reaches sync_state, resulting in a
> noticeable reduction in battery life.
>
> Enable the camera clock controller (as a module) to avoid this, and
> hopefully soon provide some level of camera support.
>
> Signed-off-by: Bjorn Andersson <quic_bjorande@quicinc.com>
> ---
> arch/arm64/configs/defconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> index ef1061089548..e5ce6d08006e 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -1256,6 +1256,7 @@ CONFIG_QCM_GCC_2290=y
> CONFIG_QCM_DISPCC_2290=m
> CONFIG_QCS_GCC_404=y
> CONFIG_SA_GCC_8775P=y
> +CONFIG_SC_CAMCC_8280XP=m
> CONFIG_SC_DISPCC_8280XP=m
> CONFIG_SA_GPUCC_8775P=m
> CONFIG_SC_GCC_7180=y
>
> ---
> base-commit: 20d857259d7d10cd0d5e8b60608455986167cfad
> change-id: 20231221-enable-sc8280xp-camcc-969b2cf2e4d7
>
> Best regards,
Reviewed-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
next prev parent reply other threads:[~2023-12-22 13:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 4:47 Bjorn Andersson
2023-12-22 13:08 ` Bryan O'Donoghue [this message]
2023-12-23 3:23 ` 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=61998a14-2f9a-4b37-a6d0-77451332ae6f@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=johan@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_bjorande@quicinc.com \
--cc=will@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®