> -----Original Message----- > From: ext [email protected] > [mailto:[email protected]] > Sent: Tuesday, August 11, 2015 10:34 AM > To: [email protected] > Cc: [email protected]; [email protected]; Savolainen, Petri > (Nokia - FI/Espoo); [email protected]; Hongbo Zhang > Subject: [API-NEXT PATCH v4 05/10] linux-generic: sysinfo: clarify the > API for max CPU frequency > > From: Hongbo Zhang <[email protected]> > > Currently the API to get CPU frequency is vague, it needs to be > clarified > whether max or current frequency is returned, and now most use cases > want > to get max capacity of CPU in fact, so this patch makes it clear that > the > cpu_hz stand for max CPU frequency. (there is no need to store current > instant frequency) > > Accordingly the API odp_cpu_hz() is renamed to odp_cpu_hz_max(). > > While there may still be some use case of acquiring the current CPU > frequency, so the previous odp_cpu_hz() will be re-implemented for this > purpose in the next patch.
Again, for easier tracking of API changes it's not good idea to first remove cpu_hz completely and then add it back in next patch. Instead add the new API first and then convert code to use it in next steps: 1) PATCH api: cpu: added odp_cpu_hz_max "Adds new API for reading CPU max frequency ..." 2) PATCH validation: use maximum cpu freq instead of current freq "Changes validation tests to use max frequency instead of current frequency, when it is the original intention ..." -Petri _______________________________________________ lng-odp mailing list [email protected] https://lists.linaro.org/mailman/listinfo/lng-odp
