Hello tech@,
some time ago I sent patch for u-boot port (aarch4), enabling sxitemp
driver (though it's wasn't reviewed yet) - there were just some
entries in device tree missing that were added in the patch.
Then I noticed sxitemp (OpenBSD) and aw_thermal (FreeBSD) are showing
different values for
Hello Mark, tech@,
since A64 now supports dynamic frequencies and thermal zones I thought
I could go back to sxisid driver idea.
Device tree excerpts:
&{/soc} {
ths: thermal_sensor@1c25000 {
compatible = "allwinner,sun50i-a64-ths";
reg = <0x01c25000 0x100>;
> Date: Sun, 29 Sep 2019 21:25:11 +0200
> From: Krystian Lewandowski
>
> Hello Mark, tech@,
> since A64 now supports dynamic frequencies and thermal zones I thought
> I could go back to sxisid driver idea.
>
> Device tree excerpts:
>
> &{/soc} {
> ths: thermal_sensor@1c25000 {
>
Mark, thank you for quick feedback.
I'm not pushing or anything of course,
just want to provide more information.
I put radiator on A64+ I'm using (both were tested with radiator),
also FreeBSD and OpenBSD may have been using different clocks
(648MHz vs 768MHz), original mail was sent in April, l
> Date: Sun, 29 Sep 2019 23:14:14 +0200
> From: Krystian Lewandowski
>
> Mark, thank you for quick feedback.
>
> I'm not pushing or anything of course,
> just want to provide more information.
>
> I put radiator on A64+ I'm using (both were tested with radiator),
> also FreeBSD and OpenBSD may
