| Message ID | 20220113121143.22280-24-alim.akhtar@samsung.com (mailing list archive) |
|---|---|
| State | Not Applicable, archived |
| Headers | show |
| Series | [01/23] dt-bindings: clock: Document FSD CMU bindings | expand |
On 13/01/2022 13:11, Alim Akhtar wrote: > From: Aswani Reddy <aswani.reddy@samsung.com> > > This patch adds support for handling thress clusters > (upto 12 CPUs) > > Cc: linux-fsd@tesla.com > Signed-off-by: Aswani Reddy <aswani.reddy@samsung.com> > Signed-off-by: Alim Akhtar <alim.akhtar@samsung.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
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, MCT_NR_IRQS, }; @@ -89,7 +93,7 @@ static int mct_irqs[MCT_NR_IRQS]; struct mct_clock_event_device { struct clock_event_device evt; unsigned long base; - char name[10]; + char name[11]; }; static void exynos4_mct_write(unsigned int value, unsigned long offset)