On 11/10/20 2:59 PM, Daniel Lezcano wrote:
On 10/11/2020 12:05, Lukasz Luba wrote:
Actually I've found one issue when I have been trying to clean
my testing branch with modified scmi-cpufreq.c.
IMO, those errors are not the dtpm framework fault but the scmi-cpufreq.
True, I have added this proposed macro directly into driver, but it's
not strictly the framework.
You should add a component in the drivers/powercap which does the glue
between the scmi-cpufreq and the dtpm. No stub will be needed in this
case as the component will depend on CONFIG_DTPM.
Make sense, the glue stick should take care in this scenario.
In this case, please keep the Reviewed-by and Tested-by and ignore
the previous email.
