<megi>
eh, it fits, it's just that offset is after the division
<megi>
2719/14.186
<megi>
I'd just drop the comments, or add explanantion for meaning of offset and scale
<megi>
if it confuses me :), poor reviewers
<megi>
yeah, that would work
<megi>
^ the patch above
<megi>
the measured temperatures were close enough to my IR thermometer, and we really don't know what coefficients are completely "right" anyway for H3, so there's not much point to those comments
<anarsoul>
I don't have IR thermometer, so I can't actually check whether A64 values are correct. But they match BSP
<anarsoul>
and values look reasonable
<megi>
yeah
<megi>
also add my SoB please
<megi>
to the driver
<anarsoul>
right
<anarsoul>
will do
<megi>
thanks
<megi>
you shouldn't be adding #cooling-cells to cpu in your dts patch, that's for later when we'll be hooking up thermal zones to cpufreq
<megi>
and you have to have it on every cpu then, anyway
<megi>
anarsoul: otherwise you'll run into issues if you hotplug cpu0 core out ^
<anarsoul>
megi: thanks, I'll drop it
<anarsoul>
(I haven't tested it yet)
<tuxd3v>
megi: in the kernel menuconfig, were is the thermal driver to activate?
<tuxd3v>
activate -> compile
<anarsoul>
force-pushed ths-5.4 branch with fixes
<megi>
hmm
<megi>
interesting that /sys/kernel/debug/regmap/5070400.ths/registers shows just the first reg
<anarsoul>
because last_reg is not set in regmap config?
<megi>
probably
<megi>
last reg is 0xc4 on H6, may be 0x8 on 3-sensor SoCs
<megi>
0xc8
<megi>
not sure in which units last_reg is supposed to be given :)
<anarsoul>
address
<megi>
a83t has last_reg 0x88
<anarsoul>
it's actually .max_register
<megi>
so maybe just set it to 0xfc? to get 0x100 range?
<megi>
nicely rounded :)
<anarsoul>
sounds good
<megi>
h3 and h5 also end at 0x80 and 0x84
<anarsoul>
wanna try it on your boards?
<megi>
I'll probably try tomorrow, it's getting too late
<megi>
I think it will just work
ChriChri_ has joined #linux-sunxi
<megi>
I deffed your version with mine, and it's the same, except for comments and whitespace
<megi>
diffed
<megi>
so it's already tested, I guess :)
ChriChri has quit [Ping timeout: 276 seconds]
ChriChri_ is now known as ChriChri
<anarsoul>
megi: I mean .max_register change
<megi>
ah
<anarsoul>
I'll test it myself on A64 tonight
<megi>
I'll patch it in, and test
<megi>
that should be quick enough
<megi>
it works everywhere
<megi>
you can even use it to check that there are non-default values in the calibration registers, to see what the driver loaded from sid on A64
<megi>
should be 0x800+-0x200
NeuroScr has quit [Quit: NeuroScr]
<megi>
probably much less, for me on H6, it's just 0x800+6, on H3 +0x62, and on H5 -0x20 or so
<anarsoul>
IIRC it's pretty close to 0x800
Mangy_Dog has quit [Ping timeout: 268 seconds]
<anarsoul>
single digit difference
<megi>
allwinner is getting better with their chip tuning process on newer SoCs then :)
<anarsoul>
or worse at calibration
<anarsoul>
:)
<megi>
hehe
<megi>
tuxd3v: CONFIG_SUN8I_THERMAL
<tuxd3v>
megi, I found it, thanks
<tuxd3v>
:)
NeuroScr has joined #linux-sunxi
<megi>
off I go :) good luck with testing, anarsoul and thanks for pushing the patches
<anarsoul>
np, thanks for cleaning it all up
megi has quit [Ping timeout: 250 seconds]
marcodiego has joined #linux-sunxi
lurchi_ is now known as lurchi__
NeuroScr has quit [Ping timeout: 268 seconds]
huawei has quit [Ping timeout: 250 seconds]
huawei has joined #linux-sunxi
juri__ has joined #linux-sunxi
juri_ has quit [Ping timeout: 268 seconds]
huawei has quit [Ping timeout: 250 seconds]
huawei has joined #linux-sunxi
kaspter has quit [Ping timeout: 250 seconds]
kaspter has joined #linux-sunxi
[7] has quit [Ping timeout: 250 seconds]
TheSeven has joined #linux-sunxi
marcodiego has quit [Quit: Leaving]
smaeul has quit [Read error: Connection reset by peer]
smaeul_ has joined #linux-sunxi
smaeul_ is now known as smaeul
<KotCzarny>
anarsoul: you should grab the human IR thermo, they are cheap and often come with 'object temperature' mode, which allows to measure real world temps (~0-100C)
lurchi_ has joined #linux-sunxi
lurchi__ has quit [Ping timeout: 265 seconds]
<anarsoul>
KotCzarny: no so cheap here
NeuroScr has joined #linux-sunxi
tl_lim has joined #linux-sunxi
tllim has quit [Ping timeout: 245 seconds]
selfbg has joined #linux-sunxi
reinforce has joined #linux-sunxi
pmpp has joined #linux-sunxi
pmp-p has quit [Ping timeout: 245 seconds]
<KotCzarny>
anarsoul, aliexpress then? these cost ~5-10usd
<KotCzarny>
and come handy if you dont have flir/seekcam
kilobyte1 has joined #linux-sunxi
kilobyte_ch has quit [Ping timeout: 265 seconds]
yann|work has quit [Ping timeout: 276 seconds]
dddddd has quit [Remote host closed the connection]
florian_kc has joined #linux-sunxi
diego_r has joined #linux-sunxi
tl_lim has quit [Read error: Connection reset by peer]
spikerguy[m] has quit [Remote host closed the connection]
atopuzov[m] has quit [Write error: Connection reset by peer]
mic-e[m] has quit [Read error: Connection reset by peer]
agates[m] has quit [Write error: Connection reset by peer]
hpagseddy[m] has quit [Read error: Connection reset by peer]
EmilKarlson has quit [Read error: Connection reset by peer]
t4h4[m] has quit [Read error: Connection reset by peer]
JuniorJPDJ has quit [Read error: Connection reset by peer]
k40s[m] has quit [Remote host closed the connection]
MartijnBraam has quit [Write error: Connection reset by peer]
z3ntu_ has quit [Write error: Connection reset by peer]
Danct12 has quit [Write error: Connection reset by peer]
clementp[m] has quit [Remote host closed the connection]
Jeremy_Rand_Talo has quit [Read error: Connection reset by peer]
fevv8[m] has quit [Write error: Connection reset by peer]
insep[m]1 has quit [Write error: Connection reset by peer]
davidebeatrici has quit [Write error: Connection reset by peer]
romainmahoux[m] has quit [Write error: Connection reset by peer]
freddor has quit [Read error: Connection reset by peer]
Jorik[m]1 has quit [Remote host closed the connection]
solderfumes has quit [Read error: Connection reset by peer]
thefloweringash has quit [Write error: Connection reset by peer]
vagrantc has joined #linux-sunxi
florian_kc has joined #linux-sunxi
pmpp is now known as pmp-p
florian_kc is now known as florian
clementp[m] has joined #linux-sunxi
yann|work has joined #linux-sunxi
megi has joined #linux-sunxi
chewitt has quit [Quit: Zzz..]
ldevulder_ has joined #linux-sunxi
ldevulder has quit [Ping timeout: 268 seconds]
kilobyte_ch has joined #linux-sunxi
flevopolder has joined #linux-sunxi
kilobyte1 has quit [Ping timeout: 245 seconds]
AneoX has quit [Ping timeout: 276 seconds]
AneoX has joined #linux-sunxi
kilobyte1 has joined #linux-sunxi
kilobyte_ch has quit [Ping timeout: 252 seconds]
insep[m]1 has joined #linux-sunxi
davidebeatrici has joined #linux-sunxi
oliv3r[m] has joined #linux-sunxi
fevv8[m] has joined #linux-sunxi
t4h4[m] has joined #linux-sunxi
romainmahoux[m] has joined #linux-sunxi
hpagseddy[m] has joined #linux-sunxi
EmilKarlson has joined #linux-sunxi
JuniorJPDJ has joined #linux-sunxi
agates[m] has joined #linux-sunxi
thefloweringash has joined #linux-sunxi
k40s[m] has joined #linux-sunxi
mic-e[m] has joined #linux-sunxi
Danct12 has joined #linux-sunxi
z3ntu_ has joined #linux-sunxi
solderfumes has joined #linux-sunxi
Jeremy_Rand_Talo has joined #linux-sunxi
MartijnBraam has joined #linux-sunxi
atopuzov[m] has joined #linux-sunxi
freddor has joined #linux-sunxi
kilobyte_ch has joined #linux-sunxi
kilobyte1 has quit [Ping timeout: 276 seconds]
kilobyte_ch has quit [Ping timeout: 268 seconds]
kilobyte_ch has joined #linux-sunxi
DonkeyHotei has joined #linux-sunxi
flevopolder has joined #linux-sunxi
kilobyte1 has joined #linux-sunxi
kilobyte_ch has quit [Read error: Connection reset by peer]
chewitt has joined #linux-sunxi
rra has joined #linux-sunxi
<flevopolder>
does anyone know of any common gotchas when trying to interface an ina219 breakoutboard with an olimex olinuxino a64?
<karlp>
what's your actual question?
<KotCzarny>
i've read it as 'anyone else did that?'
<DuClare>
common gotchas with something oddly specific? hehe
<flevopolder>
i have set up a breakout board, wired it to the olimex running armbian and enabled the overlay but the interface doesn't show up
<flevopolder>
so the i2c interface doesn't come up
<KotCzarny>
start from the bottom up
<flevopolder>
meaning?
<KotCzarny>
read docs? armbian forum about olinuxino a64 and i2c?
<KotCzarny>
i2c-detect etc?
<flevopolder>
yeah I've been through all of those. The main issue is I can't get the /dev/i2c1 to load but I get no usable output whatsover. Is it possible to enable this interface without having something wired at all?
chewitt has quit [Quit: Zzz..]
Mangy_Dog has joined #linux-sunxi
rra has left #linux-sunxi [#linux-sunxi]
flevopolder has quit [Remote host closed the connection]
flevopolder has joined #linux-sunxi
chewitt has joined #linux-sunxi
chewitt has quit [Quit: Zzz..]
flevopolder has quit [Quit: Leaving]
flevopolder has joined #linux-sunxi
vagrantc has quit [Quit: leaving]
chewitt has joined #linux-sunxi
gaston1980 has joined #linux-sunxi
AneoX has quit [Ping timeout: 246 seconds]
AneoX has joined #linux-sunxi
<lurchi_>
flevopolder: 1. there are two drivers for the ina2xx, one for hwmon and one for iio
<karlp>
neither of which will matter if they're trying to use i2c userspace and don't have an i2c dev node though
chewitt has quit [Quit: Zzz..]
chewitt has joined #linux-sunxi
<megi>
flevopolder: maybe ask on armbian forums?
airstorm has quit [Quit: airstorm]
NeuroScr has quit [Ping timeout: 276 seconds]
JohnDoe_71Rus has joined #linux-sunxi
<montjoie>
mripard_: you said applied for pine64 model b but I still didnt saw them in linux-next
<montjoie>
mripard_: where is your "next" tree ? the one I find seems obsoletes
<GNUtoo>
What's the name of the Manufacturer: FriendlyARM or FriendlyElec?
florian_kc has quit [Ping timeout: 268 seconds]
<GNUtoo>
sams IP address inded
<GNUtoo>
Like when adding a new device should I put the manufacturer as FriendlyARM or FriendlyElec, and if it's FriendlyElec, do the other boards need to be changed to FriendlyElec?
<anarsoul>
montjoie: it applies more or less cleanly on linux-next, some dts patches are fuzzy, but it's OK. Anyway, I'll rebase it onto linux-next before sending v7