.kernel.org; linux-kernel@vger.kernel.org; mark.rutl...@arm.com;
> mturque...@baylibre.com; robh...@kernel.org; s.ha...@pengutronix.de;
> shawn...@kernel.org; Aisheng Dong ; Anson
> Huang ; Daniel Baluta
> Cc: dl-linux-imx
> Subject: RE: [PATCH RESEND V6 2/2] clk: imx: scu: ad
Quoting Anson Huang (2019-02-22 18:32:28)
> > > + cluster_id = 0;
> >
> > Do we still need to check this anymore? Why not just always use cluster_id
> > 0?
>
> The i.MX8QXP ONLY has 1 cluster named A35, while on i.MX8QM there will be
> 2 clusters, A53 and A72, so we need to use the
.kernel.org; linux-kernel@vger.kernel.org; mark.rutl...@arm.com;
> mturque...@baylibre.com; robh...@kernel.org; s.ha...@pengutronix.de;
> shawn...@kernel.org; Aisheng Dong ; Anson
> Huang ; Daniel Baluta
> Cc: dl-linux-imx
> Subject: Re: [PATCH RESEND V6 2/2] clk: imx: scu: ad
Quoting Anson Huang (2019-02-21 18:32:10)
> On NXP's i.MX SoCs with system controller inside, CPU frequency
> scaling can ONLY be done by system controller firmware, and it
> can ONLY be requested from secure mode, so Linux kernel has to
> call ARM SMC to trap to ARM-Trusted-Firmware to request sys
Quoting Anson Huang (2019-02-21 18:32:10)
> On NXP's i.MX SoCs with system controller inside, CPU frequency
> scaling can ONLY be done by system controller firmware, and it
> can ONLY be requested from secure mode, so Linux kernel has to
> call ARM SMC to trap to ARM-Trusted-Firmware to request sys
On NXP's i.MX SoCs with system controller inside, CPU frequency
scaling can ONLY be done by system controller firmware, and it
can ONLY be requested from secure mode, so Linux kernel has to
call ARM SMC to trap to ARM-Trusted-Firmware to request system
controller firmware to do CPU frequency scalin
6 matches
Mail list logo
