From: Michal Simek <michal.simek@xilinx.com>
To: <quanyang.wang@windriver.com>, <catalin.marinas@arm.com>,
<will@kernel.org>
Cc: michal.simek@xilinx.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: defconfig: enable clock driver for ZynqMP platforms
Date: Thu, 10 Dec 2020 15:09:31 +0100 [thread overview]
Message-ID: <177b4056-af6d-fc1e-1d09-d9190d6228cf@xilinx.com> (raw)
In-Reply-To: <20201209021416.1017790-1-quanyang.wang@windriver.com>
On 09. 12. 20 3:14, quanyang.wang@windriver.com wrote:
> From: Quanyang Wang <quanyang.wang@windriver.com>
>
> The Zynqmp Ultrascale clock controller generates clocks for peripherals
> by default. So enable this clock driver for ZynqMP platforms.
>
> Signed-off-by: Quanyang Wang <quanyang.wang@windriver.com>
> ---
> arch/arm64/configs/defconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> index 5cfe3cf6f2ac..95b5a963917e 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -872,6 +872,7 @@ CONFIG_COMMON_CLK_FSL_SAI=y
> CONFIG_COMMON_CLK_S2MPS11=y
> CONFIG_COMMON_CLK_PWM=y
> CONFIG_COMMON_CLK_VC5=y
> +CONFIG_COMMON_CLK_ZYNQMP=y
> CONFIG_COMMON_CLK_BD718XX=m
> CONFIG_CLK_RASPBERRYPI=m
> CONFIG_CLK_IMX8MM=y
>
Position based on savedefconfig should be different but there are a lot
of issues like this that's why
Acked-by: Michal Simek <michal.simek@xilinx.com>
Thanks,
Michal
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-12-10 14:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 2:14 [PATCH] arm64: defconfig: enable clock driver for ZynqMP platforms quanyang.wang
2020-12-10 14:09 ` Michal Simek [this message]
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=177b4056-af6d-fc1e-1d09-d9190d6228cf@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quanyang.wang@windriver.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;
as well as URLs for NNTP newsgroup(s).