On 02-01-2014 13:50, Matthew Longnecker wrote: > >> I think the platform driver may set governor for the thermal zone, >> so how about to add a property named as "governor", >> and parse it to tzp->governor_name, >> something like: >> ret = of_property_read_string(child, "governor", &str); >> if (ret == 0) >> if (strlen(str) < THERMAL_NAME_LENGTH) >> strcpy(tzp->governor_name, str); The above is not applicable to DT. The very first version of my proposed series did include some sort of governor treatment too, fetching such data from DT. >> >> Thanks. >> Wei. > > DT is supposed to describe the hardware, right? The governor isn't > hardware -- it's a software control policy. On the other hand, that > control policy must be tuned according to the behaviors of the platform > hardware otherwise the system will be unstable. Yes, this is the correct understanding. We can describe hardware, including thermal constraints, as long as they do not include policy or OS specific implementation. > > Is it appropriate to be naming the governor in DT? If so, is it equally > appropriate to describe any governor-specific parameters in DT (even > though they are pure software constructs)? No for both questions. However, for the parameters, as long as you can map the software parameter as a hardware descriptor, then we can discuss if that can be used as DT properties. > > -Matt > > -- You have got to be excited about what you are doing. (L. Lamport) Eduardo Valentin
Attachment:
signature.asc
Description: OpenPGP digital signature
