Hi Geert-san, Simon-san, > -----Original Message----- > From: linux-renesas-soc-owner@xxxxxxxxxxxxxxx [mailto:linux-renesas-soc-owner@xxxxxxxxxxxxxxx] On Behalf Of Simon > Horman > Sent: Wednesday, March 7, 2018 5:11 PM [snip] > > > > Documentation/devicetree/bindings/arm/cpu-capacity.txt: > > > > "capacity-dmips-mhz is an optional cpu node [1] property: u32 value > > representing CPU capacity expressed in normalized DMIPS/MHz. At boot time, the > > maximum frequency available to the cpu is then used to calculate the capacity > > value internally used by the kernel." > > > > IIUIC, you should thus not use 15532585 and 6241541 directly, but > > scale them to the frequency. > > > > So the formula for CA53 becomes: > > > > 1024 / (15532585 / 1500) * (6241541 / 1200) = 514 > > > > > Considering cpufreq is available later, is it better to set the value(514) > > > for CA53 scaled by different maximum frequencies? > > > > DT describes the hardware, not software limitations, so IMHO 514 is the correct > > value. Sorry, I misunderstood the intention of definition in DT. Thanks for your detailed explanation. I understood it. > Yes agreed. Please refresh this patchset accordingly. I will update v2 patch. Regards, Inami -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
