> Thats more complex than it needs to be. Easy solution is to allways > compile in full set from semiconductor vendor and then maybe only use > subset. Completely disagree. That solution might be easy from a first glance, but you definitely not seeing the whole picture. Let's think a bit how it all should work from the embedded POV. For a SoC, there can be different use cases, like GPS navigator, GSM/GPRS phone, WiFi phone, MP3 player and so on. For EACH use case (which is usually denoted as a 'policy'), there will be different sets of devices enabled and sets of operating points valid for this use case. Given that the operating points are defined in kernel, how the userspace application managing operating point transitions (power management daemon) will work? The situation would be rather ridiculous in this case: the description of valid OPs for a policy and OP transitions will be separated from the description of OPs themselves, and it would lead to a lot of redundant code and pretty unclear overall structure. So, the bottom line is: all OPs compiled in kernel and no runtime OPs creation is the idea that is *orthogonal* to the dynamic power management concept.
