[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6719ffa5-f765-6ed1-6347-6558471e6bbb@canonical.com>
Date: Thu, 13 Jan 2022 14:36:30 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
To: Alim Akhtar <alim.akhtar@...sung.com>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Cc: soc@...nel.org, linux-clk@...r.kernel.org,
devicetree@...r.kernel.org, olof@...om.net,
linus.walleij@...aro.org, catalin.marinas@....com,
robh+dt@...nel.org, s.nawrocki@...sung.com,
linux-samsung-soc@...r.kernel.org, pankaj.dubey@...sung.com,
Aswani Reddy <aswani.reddy@...sung.com>, linux-fsd@...la.com
Subject: Re: [PATCH 23/23] clocksource: exynos_mct: Add support for handling
three clusters
On 13/01/2022 13:11, Alim Akhtar wrote:
> From: Aswani Reddy <aswani.reddy@...sung.com>
>
> This patch adds support for handling thress clusters
> (upto 12 CPUs)
>
> Cc: linux-fsd@...la.com
> Signed-off-by: Aswani Reddy <aswani.reddy@...sung.com>
> Signed-off-by: Alim Akhtar <alim.akhtar@...sung.com>
> ---
> drivers/clocksource/exynos_mct.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/clocksource/exynos_mct.c b/drivers/clocksource/exynos_mct.c
> index 5e3e96d3d1b9..ba3af940a687 100644
> --- a/drivers/clocksource/exynos_mct.c
> +++ b/drivers/clocksource/exynos_mct.c
> @@ -78,6 +78,10 @@ enum {
> MCT_L5_IRQ,
> MCT_L6_IRQ,
> MCT_L7_IRQ,
> + MCT_L8_IRQ,
> + MCT_L9_IRQ,
> + MCT_L10_IRQ,
> + MCT_L11_IRQ,
I think this should be variable, based on SoC compatible. The mistake
was done already when adding Exynos5420 support by Linaro/Samsung, but
at least let's correct it now.
Older MCTs/SoCs do not support 12 local interrupts, so they do not need
and should not register so many interrupts.
Best regards,
Krzysztof
Powered by blists - more mailing lists