linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Kathiravan T <kathirav@codeaurora.org>
To: catalin.marinas@arm.com, will@kernel.org,
	bjorn.andersson@linaro.org, shawnguo@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Cc: sivaprak@codeaurora.org
Subject: Re: [PATCH] arm64: defconfig: enable APSS clock driver for IPQ6018
Date: Thu, 8 Oct 2020 21:59:00 +0530	[thread overview]
Message-ID: <8edb1ab1-4afd-e36a-f2d4-f790cd7bd0cb@codeaurora.org> (raw)
In-Reply-To: <1600350970-26607-1-git-send-email-kathirav@codeaurora.org>

Bjorn,

Any comments on this? I would like to know if there is any chances of 
taking this patch for v5.10 merge window?

Thanks,

Kathiravan T.


On 9/17/2020 7:26 PM, Kathiravan T wrote:
> Lets enable the APSS clock driver for the DVFS support.
>
> Signed-off-by: Kathiravan T <kathirav@codeaurora.org>
> ---
>   arch/arm64/configs/defconfig | 1 +
>   1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> index 6d04b9577b0b..67244560f869 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -850,6 +850,7 @@ CONFIG_QCOM_A53PLL=y
>   CONFIG_QCOM_CLK_APCS_MSM8916=y
>   CONFIG_QCOM_CLK_SMD_RPM=y
>   CONFIG_QCOM_CLK_RPMH=y
> +CONFIG_IPQ_APSS_6018=y
>   CONFIG_IPQ_GCC_8074=y
>   CONFIG_IPQ_GCC_6018=y
>   CONFIG_MSM_GCC_8916=y
>
> base-commit: 856deb866d16e29bd65952e0289066f6078af773

-- 
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-10-08 16:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-17 13:56 [PATCH] arm64: defconfig: enable APSS clock driver for IPQ6018 Kathiravan T
2020-10-08 16:29 ` Kathiravan T [this message]
2020-10-29  4:09   ` Kathiravan T

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=8edb1ab1-4afd-e36a-f2d4-f790cd7bd0cb@codeaurora.org \
    --to=kathirav@codeaurora.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=sivaprak@codeaurora.org \
    --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;
as well as URLs for NNTP newsgroup(s).