Date: Thu, 8 Mar 2018 12:33:44 +0100 From: Luc Hondareyte <hondareyte.luc@laposte.net> To: Emmanuel Vadot <manu@bidouilliste.com> Cc: Luc Hondareyte via freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: cpufreq support on Allwinner H3 Message-ID: <542a7663-b4e0-2093-4dfc-9b8e9c3b513b@laposte.net> In-Reply-To: <20180308061806.d9c9c7282d1a956d86b6bb22@bidouilliste.com> References: <5332936b-f38b-ca7a-03d9-dfc7c92e2727@laposte.net> <20180308061806.d9c9c7282d1a956d86b6bb22@bidouilliste.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Le 08/03/2018 à 06:18, Emmanuel Vadot a écrit : > On Tue, 6 Mar 2018 20:59:37 +0100 > Luc Hondareyte via freebsd-arm <freebsd-arm@freebsd.org> wrote: > >> Hi, >> >> I've just build 12-current for Allwinner H3 (armv7) and it seems that >> cpufreq support is missing (orangepi or nanopi): > There is no opp table (freq<->voltage table) in the DTS that's why > it's not working. This thread? http://lists.infradead.org/pipermail/linux-arm-kernel/2018-February/557940.html > I think I've seen patches on the linux-arm kernel mailing list to add > them but even with thoses we will need support for the v2 opp. v2 opp? Does it mean that, as a workaround, with the appropriate DTS patch and a switch back to armv6, this should work? I say that because, on nanopi neo, with the "old" 12-current image build by Ganbold Tsagaankhuu (that was available on FriendlyArm Wiki), cpu_freq support is OK and it’s run at full speed: root@allwinner-h3:~ # uname -a FreeBSD allwinner-h3 12.0-CURRENT FreeBSD 12.0-CURRENT #7 r308116M: Mon Oct 31 10:56:20 ULAT 2016 tsgan@beastie.mstride.com:/usr/obj/arm.armv6/usr/src/sys/GENERIC arm root@allwinner-h3:~ # sysctl dev.cpu.0.freq cpufreq: get returning known freq 1008 cpufreq: get returning known freq 1008 dev.cpu.0.freq: 1008 And this image does not seem to use Linux DTS. >> root@allwinner-h3:~ # service powerd onestart >> Starting powerd. >> powerd: no cpufreq(4) support -- aborting: No such file or directory >> /etc/rc.d/powerd: WARNING: failed to start powerd >> >> So, on nanopi neo, it's slowdown (not on orange-pi that seems to run at >> full speed). I am using a custom kernel conf that just contains: >> >> include GENERIC >> nooptions INVARIANTS >> nooptions INVARIANT_SUPPORT >> nooptions WITNESS >> nooptions WITNESS_SKIPSPIN >> nooptions BUF_TRACKING >> nooptions DEADLKRES >> nooptions FULL_BUF_TRACKING >> > You can use the GENERIC-NODEBUG for that > Oh, I missed that. Thanks.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?542a7663-b4e0-2093-4dfc-9b8e9c3b513b>