On Sat, 2015-07-25 at 22:54 +0800, Chen-Yu Tsai wrote: > On Sat, Jul 25, 2015 at 10:46 PM, Leonardo Canducci > <leonardo.candu...@gmail.com> wrote: > > I got lost somewhere in that long thread but I saw cpufreq on > cubie* works > > for someone [0]. It's just a matter of loading two modules. I tried > myself > > on my jessie install (kernel from experimental) and can confirm > that: > > > > leo@cubetto:~$ sudo modprobe axp20x-regulator > > leo@cubetto:~$ sudo modprobe cpufreq-dt > > leo@cubetto:~$ ls /sys/devices/system/cpu/cpu0/cpufreq/ > > affected_cpus related_cpus > scaling_governor > > cpuinfo_cur_freq scaling_available_frequencies > scaling_max_freq > > cpuinfo_max_freq scaling_available_governors > > > scaling_min_freq > > cpuinfo_min_freq scaling_cur_freq > scaling_setspeed > > cpuinfo_transition_latency scaling_driver stats > > > > How do I make this change persistent? > > Add both module names to /etc/modules.
Is there any way to arrange for these modules to be loaded automatically without the user needing to configure it manually, like any other h/w driver? I'd expect at least the axp20x-regulator driver to get autoloaded when the relevant hardware is present. Not sure about the cpufreq-dt one, but should it not be loaded if the relevant nodes are present? Thanks, Ian. > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
