On Sat, Oct 29, 2011 at 3:48 AM, Sylwester Nawrocki <snjw23@xxxxxxxxx> wrote: > > You're putting whole driver under arch/arm/, I'm wondering whether the functionality > it provides could be handled by some generic framework, like cpufreq or devfreq. > How this driver is different from cpufreq drivers ? I think there would be futher usage with ASV if IEM and proper PMICs are attaches; however, for now, ASV guides proper vddarm and vddint voltages for each freuquency. Both drivers in cpufreq(vddarm and arm core freq) and devfreq(vddint and memory/bus freq.. and GPU or MMC later?) should use the result value of ASV because they both alter voltages according to the ASV value. Thus, if this is going to be located in drivers/, it'd better be in elsewhere (drivers/misc? drivers/hwmon? ..???) and capable of providing values to other device drivers, at least to cpufreq and devfreq drivers. Cheers! MyungJoo > > -- > Thanks, > Sylwester > -- > To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- MyungJoo Ham, Ph.D. Mobile Software Platform Lab, DMC Business, Samsung Electronics -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |