ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion
shailangsa has joined #linux-rockchip
kevery has quit [Read error: Connection reset by peer]
kevery has joined #linux-rockchip
camus has quit [Remote host closed the connection]
camus has joined #linux-rockchip
lurchi__ is now known as lurchi_
shoragan has quit [Ping timeout: 250 seconds]
shoragan has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
camus has quit [Ping timeout: 250 seconds]
camus has joined #linux-rockchip
kevery has quit [Remote host closed the connection]
kevery has joined #linux-rockchip
kevery has quit [Remote host closed the connection]
kevery has joined #linux-rockchip
lurchi_ is now known as lurchi__
lurchi__ has quit [Ping timeout: 240 seconds]
lurchi_ has joined #linux-rockchip
lurchi_ is now known as lurchi__
camus has quit [Ping timeout: 256 seconds]
camus has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 256 seconds]
kevery1 is now known as kevery
montjoie has joined #linux-rockchip
<montjoie> hello, does it exists a full datasheet of rockchip rk3328 ?
macromorgan has quit [Read error: Connection reset by peer]
stikonas has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 256 seconds]
kevery1 is now known as kevery
kevery1 has joined #linux-rockchip
kevery has quit [Read error: Connection reset by peer]
kevery1 is now known as kevery
warpme___ has joined #linux-rockchip
<wens> probably under NDA?
<macc24> wens: haha nope
<macc24> literally 5 clicks away from search results when googling "rk3328 datasheet"
<macc24> i counted.
<phh> (very first result on ecosia thus bing)
<macc24> phh: i think by "full datasheet" they meant trm
<macc24> technical reference manual\
<phh> right
<macc24> it's in deepest corner of internet - behind more than 1 click after searching
<phh> fwiw, all the chips I know call datasheet the specs + electric specs, and call TRM the register specs
<phh> I know I'm also culprit sometimes saying I want datasheet when I actually want TRM
* macc24 blames intel datasheets
<macc24> they have register definitions too
kevery1 has joined #linux-rockchip
kevery has quit [Remote host closed the connection]
kevery1 is now known as kevery
<wens> macc24: that's likely not the whole thing :p
<macc24> wens: do you expect to find silicon diagrams in datasheets?
lurchi__ is now known as lurchi_
<montjoie> wens: macc24: I found the TRM, but unfortunatly no crypto register layout
<montjoie> anyway irq number and addresses permit to start crypto working
kevery1 has joined #linux-rockchip
kevery has quit [Read error: Connection reset by peer]
kevery1 is now known as kevery
<macc24> macromorgan: you remember that issue in supertuxkart whre under cpu usage the music weirdly slowed down?
<macc24> err, gpu usage
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
camus has quit [Ping timeout: 256 seconds]
camus has joined #linux-rockchip
macromorgan has joined #linux-rockchip
<macc24> macromorgan: you remember that issue in supertuxkart whre depending on gpu usage the music would weirdly slow down?
<macromorgan> vaguely, did you find the root cause?
<macc24> i remember it being fixed
<macc24> i forgot how
<macc24> you remember?
<macromorgan> nope, sorry
<macc24> :|
<macromorgan> could it be a clock issue?
<macc24> i have no idea
chewitt has joined #linux-rockchip
<macromorgan> so I think I'm at a loss at this battery driver. No matter what I do I can't seem to get it right. If the device has a partial charge and is plugged in it overestimates the capacity of the battery
<macromorgan> basically... I should have 20% when it says I have 50%
<macromorgan> I wonder if we can just take the factory driver, modify it a bit, and push that upstream?
<macc24> macromorgan: yea cause the voltage jumps up when charging and the driver thinks it means higher capacity?
<macromorgan> correct
<macromorgan> and while there's an ocv voltage it don't mean shit it seems...
<macc24> why then not rely solely on coulomb counter or whatever?
<macromorgan> because you need to init it when the system boots with what you guess the capacity is
<macromorgan> and I can't seem to accurately guess that
<macc24> hmm
* macc24 shrugs
<macc24> just look at bsp battery driver, imo it's beyond repair
<macc24> it took me faster to write a new driver from scratch than it took me to get it working on mainline kernel
<macromorgan> I think the bsp driver writes the capacity to nvram periodically, I might have to just do that
<macromorgan> maybe we'll get lucky and the pine folks (having the rk817 in their new pinenote) will want to take a stab at this with someone more skilled than we?
<macc24> idk
<macc24> if you can't get capacity rating just push the driver without it lol
<macc24> better to have just voltage/current readout than to have none readout
<macromorgan> I mean, I can do that I guess?
<macc24> i can try taking a shot at tackling any capacity readout
<macromorgan> maybe I should ask someone on the PM team if they think voltage/current is better than nothing at all?
<macromorgan> since I can't even measure charge accurately currently
* macc24 points at drivers/power/supply/s3c_adc_battery.c
<macc24> that driver is in mainline tree with no capacity measurement so i guess it's fine
<macromorgan> it has charge now which is something I'm struggling to get right
<macromorgan> (charge now is basically capacity if you know the full charge and empty charge)
<macromorgan> which that driver has all 3 of
<macromorgan> capacity is just those 3 numbers and some math
<macc24> hmm
* macc24 shrugs
<macromorgan> I can't even do charge, because if I boot plugged in I can't get accurate values to do an OCV lookup to get the estimated capacity
<macromorgan> (unless the device is fully charged of course)
<macc24> lol disable charging in software and measure it that way xD
shailangsa has quit [Remote host closed the connection]
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 250 seconds]
kevery1 is now known as kevery
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 250 seconds]
kevery1 is now known as kevery
vagrantc has joined #linux-rockchip
camus1 has joined #linux-rockchip
camus has quit [Ping timeout: 252 seconds]
camus1 is now known as camus
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 256 seconds]
kevery1 is now known as kevery
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 256 seconds]
kevery1 is now known as kevery
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 256 seconds]
kevery1 is now known as kevery
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
lurchi_ is now known as lurchi__
System_Error has quit [Remote host closed the connection]
System_Error has joined #linux-rockchip
lurchi__ is now known as lurchi_
lurchi_ is now known as lurchi__
kilobyte1 has quit [Quit: WeeChat 2.3]
kilobyte_ch has joined #linux-rockchip
lurchi__ is now known as lurchi_
camus1 has joined #linux-rockchip
camus has quit [Ping timeout: 250 seconds]
camus1 is now known as camus
lurchi_ is now known as lurchi__
lurchi__ is now known as lurchi_