From: neil.armstrong@linaro.org
To: Jonathan Marek <jonathan@marek.ca>, linux-arm-msm@vger.kernel.org
Cc: Bjorn Andersson <andersson@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Jagadeesh Kona <quic_jkona@quicinc.com>,
"open list:COMMON CLK FRAMEWORK" <linux-clk@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] clk: qcom: videocc-sm8550: depend on either gcc-sm8550 or gcc-sm8650
Date: Mon, 7 Oct 2024 09:11:41 +0200 [thread overview]
Message-ID: <c32226a8-43ac-4dc7-b2ce-8ce9464c6eba@linaro.org> (raw)
In-Reply-To: <20241005144047.2226-1-jonathan@marek.ca>
On 05/10/2024 16:40, Jonathan Marek wrote:
> This driver is compatible with both sm8550 and sm8650, fix the Kconfig
> entry to reflect that.
>
> Fixes: da1f361c887c ("clk: qcom: videocc-sm8550: Add SM8650 video clock controller")
> Signed-off-by: Jonathan Marek <jonathan@marek.ca>
> ---
> drivers/clk/qcom/Kconfig | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/clk/qcom/Kconfig b/drivers/clk/qcom/Kconfig
> index a3e2a09e2105b..4444dafa4e3df 100644
> --- a/drivers/clk/qcom/Kconfig
> +++ b/drivers/clk/qcom/Kconfig
> @@ -1230,11 +1230,11 @@ config SM_VIDEOCC_8350
> config SM_VIDEOCC_8550
> tristate "SM8550 Video Clock Controller"
> depends on ARM64 || COMPILE_TEST
> - select SM_GCC_8550
> + depends on SM_GCC_8550 || SM_GCC_8650
> select QCOM_GDSC
> help
> Support for the video clock controller on Qualcomm Technologies, Inc.
> - SM8550 devices.
> + SM8550 or SM8650 devices.
> Say Y if you want to support video devices and functionality such as
> video encode/decode.
>
Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
next prev parent reply other threads:[~2024-10-07 7:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-05 14:40 [PATCH] clk: qcom: videocc-sm8550: depend on either gcc-sm8550 or gcc-sm8650 Jonathan Marek
2024-10-06 17:32 ` Dmitry Baryshkov
2024-10-07 7:11 ` neil.armstrong [this message]
2024-10-16 20:42 ` 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=c32226a8-43ac-4dc7-b2ce-8ce9464c6eba@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=andersson@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=jonathan@marek.ca \
--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=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;
as well as URLs for NNTP newsgroup(s).