> > > +device_initcall(register_fujitsu_mac_pmu_driver);
> > > diff --git a/include/linux/cpuhotplug.h b/include/linux/cpuhotplug.h
> > > index 2361ed4d2b15..e6e49e09488a 100644
> > > --- a/include/linux/cpuhotplug.h
> > > +++ b/include/linux/cpuhotplug.h
> > > @@ -227,6 +227,7 @@ enum cpuhp_state {
> > > CPUHP_AP_PERF_ARM_APM_XGENE_ONLINE,
> > > CPUHP_AP_PERF_ARM_CAVIUM_TX2_UNCORE_ONLINE,
> > > CPUHP_AP_PERF_ARM_MARVELL_CN10K_DDR_ONLINE,
> > > + CPUHP_AP_PERF_ARM_FUJITSU_MAC_ONLINE,
> >
> > Can this use CPU_AP_ONLINE_DYN
> > or are there some ordering contraints?
>
> It follows the same principles as other PMU drivers.
Some of them and I suspect the is cut and paste rather than justified.
+ Not sure how long the dynamic part has been available.
>
> >
> > > CPUHP_AP_PERF_POWERPC_NEST_IMC_ONLINE,
> > > CPUHP_AP_PERF_POWERPC_CORE_IMC_ONLINE,
> > > CPUHP_AP_PERF_POWERPC_THREAD_IMC_ONLINE,
>
> Best Regards,
> Yoshihiro Furudera
