From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: Vincent Whitchurch <vincent.whitchurch@axis.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>
Cc: kernel@axis.com, alim.akhtar@samsung.com,
linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clocksource/drivers/exynos_mct: Enable building on ARTPEC
Date: Mon, 7 Mar 2022 09:46:59 +0100 [thread overview]
Message-ID: <e021ee5d-1d4d-61ea-8eb4-51ca87820b2f@canonical.com> (raw)
In-Reply-To: <20220307083744.1592533-1-vincent.whitchurch@axis.com>
On 07/03/2022 09:37, Vincent Whitchurch wrote:
> This timer block is used on ARTPEC-8.
>
> Signed-off-by: Vincent Whitchurch <vincent.whitchurch@axis.com>
> ---
> drivers/clocksource/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/clocksource/Kconfig b/drivers/clocksource/Kconfig
> index ae95d06a4a8f..2ea981ef23af 100644
> --- a/drivers/clocksource/Kconfig
> +++ b/drivers/clocksource/Kconfig
> @@ -419,7 +419,7 @@ config ATMEL_TCB_CLKSRC
> config CLKSRC_EXYNOS_MCT
> bool "Exynos multi core timer driver" if COMPILE_TEST
> depends on ARM || ARM64
> - depends on ARCH_EXYNOS || COMPILE_TEST
> + depends on ARCH_ARTPEC || ARCH_EXYNOS || COMPILE_TEST
This looks ok, but please also provide compatible in the bindings (if
driver stays the same) on top of my patches specifying number of interrupts:
https://github.com/krzk/linux/commits/n/dt-bindings-exynos-mct-v2
Best regards,
Krzysztof
_______________________________________________
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:[~2022-03-07 8:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 8:37 [PATCH] clocksource/drivers/exynos_mct: Enable building on ARTPEC Vincent Whitchurch
2022-03-07 8:46 ` Krzysztof Kozlowski [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=e021ee5d-1d4d-61ea-8eb4-51ca87820b2f@canonical.com \
--to=krzysztof.kozlowski@canonical.com \
--cc=alim.akhtar@samsung.com \
--cc=daniel.lezcano@linaro.org \
--cc=kernel@axis.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=vincent.whitchurch@axis.com \
/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