From: Brian Masney <bmasney@redhat.com>
To: Rosen Penev <rosenp@gmail.com>
Cc: linux-clk@vger.kernel.org,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
David Lechner <david@lechnology.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] clk: davinci: add Kconfig symbol
Date: Mon, 27 Apr 2026 10:47:38 -0400 [thread overview]
Message-ID: <ae93CukeYoJEtaaH@redhat.com> (raw)
In-Reply-To: <20260427052354.959139-1-rosenp@gmail.com>
Hi Rosen,
On Sun, Apr 26, 2026 at 10:23:54PM -0700, Rosen Penev wrote:
> Add COMPILE_TEST support as a result so that the buildbots can run
> through this driver. There's nothing architecture specific about it.
>
> Signed-off-by: Rosen Penev <rosenp@gmail.com>
It'd be nice if the commit title and/or the commit description mentioned
that this is for an existing driver in the tree.
> ---
> drivers/clk/Kconfig | 7 +++++++
> drivers/clk/Makefile | 2 +-
> drivers/clk/davinci/Makefile | 6 +++---
> 3 files changed, 11 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/clk/Kconfig b/drivers/clk/Kconfig
> index 06a7ac971edf..42d84c0ed5fc 100644
> --- a/drivers/clk/Kconfig
> +++ b/drivers/clk/Kconfig
> @@ -317,6 +317,13 @@ config COMMON_CLK_AXI_CLKGEN
> Support for the Analog Devices axi-clkgen pcore clock generator for Xilinx
> FPGAs. It is commonly used in Analog Devices' reference designs.
>
> +config CLK_DA850
> + bool "DaVinci DA850 CLK support"
> + depends on ARCH_DAVINCI_DA850 || COMPILE_TEST
The clk driver is needed for this platform, so you can make it easier
for someone to configure their kernel like this:
depends on ARCH_ARM || COMPILE_TEST
default ARCH_DAVINCI_DA850
Brian
prev parent reply other threads:[~2026-04-27 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 5:23 [PATCH] clk: davinci: add Kconfig symbol Rosen Penev
2026-04-27 14:27 ` David Lechner
2026-04-27 14:47 ` Brian Masney [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=ae93CukeYoJEtaaH@redhat.com \
--to=bmasney@redhat.com \
--cc=david@lechnology.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=rosenp@gmail.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