Turl changed the topic of #linux-sunxi to: Allwinner/sunxi /development discussion - did you try looking at our wiki? https://linux-sunxi.org - Don't ask to ask. Just ask and wait! - https://github.com/linux-sunxi/ - Logs at http://irclog.whitequark.org/linux-sunxi
jstein has quit [Remote host closed the connection]
TheSeven has quit [Disconnected by services]
[7] has joined #linux-sunxi
apritzel has quit [Ping timeout: 244 seconds]
egbert has quit [Disconnected by services]
egbert has joined #linux-sunxi
ninolein_ has joined #linux-sunxi
ninolein has quit [Ping timeout: 276 seconds]
cnxsoft has joined #linux-sunxi
cnxsoft has quit [Read error: Connection reset by peer]
cnxsoft has joined #linux-sunxi
<wens> montjoie: fyi i would drop the regulator bindings for now, since a) we don't support the pmic, and b) there's discussion on how to do power sequencing for various busses
<wens> that would also include stuff like enable and reset gpios
leoncito81 has joined #linux-sunxi
leoncito81 has quit [Remote host closed the connection]
p1u3sch1 has quit [Ping timeout: 252 seconds]
p1u3sch1 has joined #linux-sunxi
reev has joined #linux-sunxi
<montjoie> wens chich regulator bindings ? regulator_io ?
kaspter has joined #linux-sunxi
scream has joined #linux-sunxi
scream has quit [Remote host closed the connection]
<wens> montjoie: both
<wens> hmm... a83 psci patches popped out from nowhere
IgorPec has joined #linux-sunxi
<plaes> o_O
<plaes> u-boot list?
<wens> yup
libcg has joined #linux-sunxi
<wens> out of the blue
jernej has quit [Ping timeout: 276 seconds]
jernej has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
IgorPec has quit [Ping timeout: 244 seconds]
jernej has quit [Ping timeout: 260 seconds]
<plaes> ...and with info almost noone outside allwinner has..
reinforce has joined #linux-sunxi
IgorPec has joined #linux-sunxi
<wens> well i guess most of it is available in the kernel code
<wens> i dislike code that has a proper explanation though
<wens> uh... s/has/doesn't have/
staplr has quit [Remote host closed the connection]
libcg has quit [Quit: libcg]
iamfrankenstein has joined #linux-sunxi
premoboss has joined #linux-sunxi
cnxsoft has quit [Quit: cnxsoft]
cnxsoft has joined #linux-sunxi
clonak has joined #linux-sunxi
apritzel has joined #linux-sunxi
lemonzest has joined #linux-sunxi
lemonzest has quit [Remote host closed the connection]
Mr__Anderson has joined #linux-sunxi
Worf has joined #linux-sunxi
<Amit_T> apritzel: Hello, sorry to bother. In the logs shared yesterday ,did you see rsb initialized well ?
<plaes> Amit_T: use the IRC log
<apritzel> what RSB initialization are you referring to?
<apritzel> U-Boot?
<plaes> IIRC, he said no
<Amit_T> Yes
<apritzel> Amit_T: just a message saying "RSB initialized" does not say much, I guess
<Amit_T> Yeah but from dump/values , did you confirm ?
<apritzel> Amit_T: and frankly, I don't care so much about U-Boot and the RSB, at least not in the long run outside of some hacking
<apritzel> Amit_T: what exactly do you mean? When you booted via FEL, the RSB did not seem to be initialized
<apritzel> Amit_T: well, this didn't change from yesterday ;-)
<apritzel> (17:27:58) apritzel1: Amit_T: thanks for that, so indeed the RSB is not initialized, the registers are all in reset state
<apritzel> (17:28:11) apritzel1: which is proof that this is done by boot0, not BROM
<apritzel> (17:28:19) apritzel1: so we need code to do it in ATF
<Amit_T> apritzel: I booted two different version of u-boot via FEL, one has RSB initialized(tried some changes) and one has no RSB(without RSB).
<Amit_T> apritzel: ok.
<apritzel> Amit_T: why are actually still caring about the RSB in U-Boot?
<Amit_T> Just wanted to play around and wanted to test emac driver on pine64
<apritzel> I see
<apritzel> I have the code now in ATF, I improved the init sequence yesterday, though it's still depending on boot0 at the moment
<apritzel> and I have now SYSTEM_OFF working in PSCI
<apritzel> so if you type "poweroff" in Linux, it really turns off (like the BSP kernel/firmware)
ricardocrudo has joined #linux-sunxi
<apritzel> Amit_T: to verify that the RSB works correclty, you can try to read some registers from the PMIC
<apritzel> there is register 0x3 for instance, which should read 0x51
<wens> apritzel: still depending on boot0?
<apritzel> wens: well, I just didn't test it without it, I meant
<wens> i see
<apritzel> wens: while you are here: two questions about that RSB init sequence
<wens> sure
<wens> (feel free to ask anytime though, my timezone is UTC+8, and i'm around during the daytime)
The_Loko has joined #linux-sunxi
iamfrankenstein1 has joined #linux-sunxi
iamfrankenstein has quit [Ping timeout: 260 seconds]
iamfrankenstein1 is now known as iamfrankenstein
<apritzel> wens: (sorry, got distracted)
<apritzel> wens: so how does this SRTA command work? this ties the runtime address to the slave's hardware address, right?
<wens> yes
<apritzel> but the (A83) manual does not say much about the expected data format
<wens> runtime address or hardware address?
<apritzel> so what should be in the DADDR0 register
<apritzel> wens: well, both I guess?
<apritzel> my understanding is that I send a SRTA command telling the RSB that hardware address 0x1d1 is now knows as runtime address 0x2d
<wens> DADDR0 register?
<apritzel> arg, DATA0 I meant
<wens> no, with the SRTA command you use the SADDR register
<apritzel> oh
<wens> lower 16 bits are the hardware address
<apritzel> alright
<wens> which you don't fill when you issue the other commands
<apritzel> ahh
<apritzel> I was wondering about that
<apritzel> so bits 16:23 as always used
<wens> yup
<apritzel> Thanks, got it now
<apritzel> the other thing is that "PMU mode control register"
<apritzel> does PMU refer to the PMIC here?
<wens> yes
<apritzel> and do I have to write this register with bit 31 set?
<wens> the only usage is to tell the PMICs to switch to RSB mode
<wens> iirc PMU_INIT_DATA should be set to 0x7c
<apritzel> which would have been my next question ;-)
<wens> 0x3e is actually p2wi mode, found on axp221(s)
<apritzel> does that mean that I don't need to initialize I2C first just to switch the PMIC into RSB mode?
<wens> The AXP803 datasheet actually lists register 0x3e
<wens> apritzel: i don't know how the hardware actually works, but i guess that particular register is designed to send an i2c write command
<apritzel> right, that would make sense ...
<wens> with no proper way to switch everyone back lol
<apritzel> wens: thanks a ton, that was very helpful
<wens> :)
<apritzel> those were the two things I was missing
Gerwin_J has joined #linux-sunxi
<apritzel> I guess I could have learnt this by looking at some code of yours as well ;-)
<apritzel> once I get this to work properly, I will put that info into the Wiki
Gerwin_J has quit [Client Quit]
<apritzel> wens: please bug me if I forget this
<wens> i will probably forget sooner than you :|
<apritzel> ;-)
<apritzel> Amit_T: please you bug me then ;-)
<Amit_T> What would be solution if some one really don't know to use ATF and just relay on u-boot to boot kernel (how some one then use PHY) ?
<wens> mripard: i got drm working on my q8 tablet :)
<jelle> nice!
<mripard> wens: cool, what was the issue?
<wens> mripard: one was the LCD enable pin being turned off (because it is AXP209's GPIO0 / LDO5)
<wens> mripard: the other was the panel probe defer (or lack of)
<wens> and that also triggered a NULL pointer reference, which i'll send a patch for
<wens> i'll clean up the stuff and send some patches, and probably ask hans to help test them
<wens> he has way more q8 tablets
<jelle> I also have two q8 tablets
matthias_bgg has joined #linux-sunxi
<jelle> but I think I need more microsd cards :-)
<wens> codec works too
<wens> otg should work (i have it working in uboot), but i think i broke the vbus detect pin when i broke my uart soldering :(
<wens> jelle: fyi it's a q8 a13 tablet, not the newer a23/a33 ones
<jelle> wens: oh I only have a33's I think
<jelle> yes they are A33, since it has a dualcore
* wens looks at mripard's wip branch
<plaes> mripard: which chipset?
<plaes> err.. wens ^^
<plaes> ah.. Q8 has A13
matthias_bgg has quit [Quit: Leaving]
Gerwin_J has joined #linux-sunxi
Gerwin_J has quit [Ping timeout: 244 seconds]
book` has quit [Quit: Leaving]
luoyi has quit [Quit: Page closed]
kaspter has quit [Ping timeout: 260 seconds]
book` has joined #linux-sunxi
raknaz has joined #linux-sunxi
enrico_ has joined #linux-sunxi
premoboss has quit [Remote host closed the connection]
raknaz has quit [Quit: raknaz]
hansg has joined #linux-sunxi
book` has quit [Quit: Leaving]
hansg has quit [Quit: Leaving]
<MoeIcenowy> jelle: dual is A23
<MoeIcenowy> A33 is quad
<MoeIcenowy> (I have now 2 A33 tablets, one of them have its touch screen broken
<MoeIcenowy> (another one has a da*ned gsl1680 touchscreen and a da*ned esp8089 wifi card, and it's a q8, and it comes with only 512MB RAM
<wens> hans seems to be working on gsl1680
<plaes> yea
book` has joined #linux-sunxi
Amit_T has quit [Ping timeout: 265 seconds]
Net147 has quit [Ping timeout: 240 seconds]
Net147 has joined #linux-sunxi
Amit_T has joined #linux-sunxi
Net147 has quit [Ping timeout: 260 seconds]
Net147 has joined #linux-sunxi
<MoeIcenowy> wens: I made the old gsl1680 userspace driver running on it with mainline kernel
<jelle> MoeIcenowy: I have one with a esp8089 too
<jelle> I want to get it working, but first other things
<jelle> MoeIcenowy: I heard the gls1680 also has a lot of different firmware files :S
Net147 has quit [Ping timeout: 276 seconds]
Net147 has joined #linux-sunxi
iamfrankenstein1 has joined #linux-sunxi
iamfrankenstein has quit [Ping timeout: 260 seconds]
iamfrankenstein1 is now known as iamfrankenstein
paulk-leonov has joined #linux-sunxi
paulk-leonov has quit [Remote host closed the connection]
<MoeIcenowy> jelle: I've recently created a pull request to the fw_extractor of gsl1680.
Shirasaka-Hazumi has quit [Ping timeout: 250 seconds]
<MoeIcenowy> Now at least I can get usable firmwares :-(
<jelle> nice!
<MoeIcenowy> and I forked the userspace driver
<MoeIcenowy> added invert_x_y support for it
<MoeIcenowy> (I mean swap_x_y
<MoeIcenowy> now the most important ic to hack on the tablet is esp8089 :-):-):-)
paulk-leonov has joined #linux-sunxi
formruga has quit [Read error: Connection reset by peer]
<MoeIcenowy> I have also a A31s tablet with rtl8723as... It's not mine, but the owner lended it to me, as he want to get a GNU/Linux running on it
formruga has joined #linux-sunxi
<jelle> I might have that one too ;-)
<MoeIcenowy> jelle: which one?
<jelle> looking it up on the wiki
<jelle> MoeIcenowy: oh grrr it's A33
<MoeIcenowy> jelle: your q8 is a33?
<jelle> and it's an RDA5991
<MoeIcenowy> what model?
<MoeIcenowy> rda5991... God bless you
<jelle> haha
<jelle> I have another tablet but didn't open and solder it
<MoeIcenowy> I think it can at least run a mainline kernel with USB-OTG enabled
<MoeIcenowy> using q8-a33-tablet dt
<jelle> yup
Shirasaka-Hazumi has joined #linux-sunxi
<jelle> I should update the instructions
<MoeIcenowy> this tablet has at least a UART...
<MoeIcenowy> mine have no UART foud
<MoeIcenowy> :-(:-(:-(
<MoeIcenowy> (the boot log of boot0 on my tablet is shown via uSD breakout :-)
<MoeIcenowy> wens: has any one worked on ESP8089?
<MoeIcenowy> I found it really a disaster
<jelle> MoeIcenowy: haha
<jelle> MoeIcenowy: well it does bluetooth / wifi and radio?
<plaes> MoeIcenowy: there's a driver for that in rockchip SDK
<MoeIcenowy> plaes: I found a dedicated one on github
<MoeIcenowy> however, the firmware shipped in the driver is different than the firmware shipped in my A33 SDK
<plaes> hrm
<plaes> ...all those "dedicated" ones should end up in staging
<MoeIcenowy> jelle: esp8089 has only wifi
<MoeIcenowy> plaes: In fact the kernel of my distro included rtl8723bs driver directly in the staging driver :-)
<MoeIcenowy> esp8089 is a strange chip... it has even a 32-bit Application Processor in it
<MoeIcenowy> jelle: the photo of TZX-723Qa4 is not sharp at all...
staplr has joined #linux-sunxi
<plaes> esp8266 is powered by 8089
<MoeIcenowy> plaes: yes
<MoeIcenowy> the datasheet of esp8089 is a sh*t
<MoeIcenowy> I have it in Chinese, it 's more like an advertisement than a datasheet
<plaes> :)
<plaes> you need user manual
staplr has quit [Remote host closed the connection]
<jelle> uhhhh
paulk-leonov has quit [Ping timeout: 250 seconds]
<jelle> I have either one of those
<MoeIcenowy> https://github.com/al177/esp8089 is the dedicated driver I found
orly_owl_ has joined #linux-sunxi
<plaes> yea
<plaes> now if someone would clean it up and submit it to staging
* jelle looks at MoeIcenowy
<MoeIcenowy> jelle: don't look at me
<MoeIcenowy> I cannot now even make it work1
<MoeIcenowy> !
<jelle> I don't think the RDA5990 is in mainline right?
orly_owl_ has quit [Client Quit]
orly_owl_ has joined #linux-sunxi
<MoeIcenowy> jelle: I don't think also
<MoeIcenowy> s/also/either
orly_owl_ has quit [Client Quit]
<jelle> MoeIcenowy: I think my brain is so messed up and I think that one does have bluetooth :p
<MoeIcenowy> the SDIO id of esp8089 is 6666:1111
<jelle> well I have th RDA5991
<jelle> *the
<MoeIcenowy> jelle: esp8089 has reserved btcoex support, but itself didn't support bluetooth
<MoeIcenowy> 6666:1111 Is Espressif kidding me
orly_owl has quit [Ping timeout: 252 seconds]
<plaes> could you guys improve this page a bit: http://linux-sunxi.org/Wifi
orly_owl has joined #linux-sunxi
<MoeIcenowy> plaes: yes
<MoeIcenowy> I'm working on it
<jelle> plaes: what would you like to see there?
<jelle> plaes: links to android driver sources?
<MoeIcenowy> jelle: for rda5991 it's welcomed
<MoeIcenowy> and if you can, you can add the sdio number of rda599
<MoeIcenowy> rda5991
<MoeIcenowy> plaes: how to make a GPIO initially as gpio_out HIGH at boot time?
<MoeIcenowy> it's needed for esp8089's sdio probing
nashpa has quit [Quit: Going away]
yann|work has joined #linux-sunxi
nashpa has joined #linux-sunxi
<MoeIcenowy> what's the meaning of "smc 0 err, cmd 53, RD RTO !!"
<wens> MoeIcenowy: i tried esp8089 and gave up pretty quickly
<wens> MoeIcenowy: you can just ignore that
<MoeIcenowy> wens: the next line is "data error, sending stop command" "send stop command failed"
<wens> MoeIcenowy: uh... probably the chip is still in reset?
<wens> fyi quite a few wifi chips have application processors
<MoeIcenowy> wens: ...
<MoeIcenowy> maybe esp8089 should be resetted in the driver
<MoeIcenowy> however in this driver code the code of resetting is a stub
<wens> normally it's up to the bsp code to do that
<MoeIcenowy> (I now used fixed-regulator binded to r_pio to keep the chip powered up
<wens> with mainline sdio you use the pwrseq stuff
matthias_bgg has joined #linux-sunxi
<MoeIcenowy> wens: the sdio driver can request pwrseq change?
<wens> MoeIcenowy: the mmc core takes care of the stuff
<wens> iirc with esp8089 there are multiple lines you need to drive high?
<MoeIcenowy> wens: seems to be two
<MoeIcenowy> one is called chip_en
<MoeIcenowy> another is called rst
<MoeIcenowy> in the fex file
<MoeIcenowy> http://pastebin.com/mnspsDty it's my dts now
<MoeIcenowy> PL11 is rst PL6 is chip_en
<MoeIcenowy> pwrseq is now used to drive rst pin
<MoeIcenowy> (some of the comments are copied from the dt of cubietruck and chip
formruga has quit [Quit: Konversation terminated!]
reev has quit [Ping timeout: 276 seconds]
<MoeIcenowy> wens: If I want to reset the pwrseq in the driver code
<MoeIcenowy> should I use mmc_can_reset ?
formruga has joined #linux-sunxi
<wens> reset-gpios can take a list of pins
<wens> not just one
<wens> so you would have reset-gpios = <&r_pio 0 6 GPIO_ACTIVE_HIGH>, <&r_pio 0 11 GPIO_ACTIVE_LOW>;
<MoeIcenowy> wens: it seems that the code of esp8089 drivers consists some code of card activitation and rescan...
<MoeIcenowy> (although they're now only stubs
<apritzel> longsleep: is there any safe CPU frequency/voltage pair you can recommend on the Pine64?
<apritzel> longsleep: maybe a bit less conservative than 816MHz@1.1V
<apritzel> tkaiser: if you read this ^^^
JohnDoe_71Rus has quit [Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org]
tkaiser has joined #linux-sunxi
<tkaiser> apritzel: Are you able to limit SMP to 2 cores only?
<apritzel> I'd rather not, but technically totally possible
<apritzel> I am with a lower frequency, just was thinking that 816MHz might be a bit too slow
<apritzel> *I am OK with ...*
<tkaiser> apritzel: 40 percent less than 'top speed' ;) Most people do not feel performance changes of 25 percent
Worf has quit [Quit: Konversation terminated!]
<apritzel> tkaiser: I know ;-)
<apritzel> tkaiser: so you cannot safely recommend anything beyond 816 MHz then?
<apritzel> I was hoping for something near 1000 MHz, maybe
<tkaiser> apritzel: What's your target audience? The average KS backer or people with reading skills that think a Readme.md is worth a look?
afaerber has quit [Quit: Ex-Chat]
<tkaiser> apritzel: With 1008 MHz, no heatsink and cpuburn-a53 you can watch your A64 burn away :)
<apritzel> upstream kernel users
<apritzel> for the time being a rather limited audience, I guess
<apritzel> for my part I don't really want to run cpuburn all of the time, but a "make -j5" would be nice
<tkaiser> apritzel: make is a rather light workload. The best idea would be to test it out using BSP kernel (longsleep's Xenial image).
<apritzel> tkaiser: at what frequency does the Pine64 survive cpuburn without a heat-sink?
<apritzel> is that 816?
<tkaiser> Puh, let's have a look
afaerber has joined #linux-sunxi
<tkaiser> apritzel: Nope, it's less. Now trying 720 MHz
<apritzel> oh dear
Nacho has quit [Ping timeout: 252 seconds]
<tkaiser> Nope, now trying 600 MHz
buZz has quit [Ping timeout: 260 seconds]
<apritzel> I should hack the kernel to disallow exec() of something which contains "cpuburn" ;-)
enrico_ has quit [Ping timeout: 244 seconds]
pmattern has joined #linux-sunxi
enrico__ has joined #linux-sunxi
<tkaiser> apritzel: 600 MHz @ 1.04V works. 91¡C (at 23¡C ambient)
<apritzel> yeah, so that's exactly half of the advertised frequency!
clonak_ has joined #linux-sunxi
<wens> :(
clonak has quit [Ping timeout: 240 seconds]
<tkaiser> apritzel: With a really heavy CPU bound workload
diego71 has quit [Ping timeout: 246 seconds]
<apritzel> so how does this show on the BSP kernel? Does the system crash?
<apritzel> or does the arisc kicks in and turns everything off?
<tkaiser> When the Pine64 folks made their marketing video stuff showing 38¡C and low consumption I would assume they already were running on a single CPU core since back then BSP throttling settings were as broken as we already knew from H3/A83T
Nacho has joined #linux-sunxi
diego71 has joined #linux-sunxi
<tkaiser> apritzel: Nope, we improved the THS settings back in March. Before with longsleep's kernel he also lost CPU cores all the time. With the new settings throttling works reliable and killed CPU cores only happen with weird stuff like.... cpuburn-a53
<apritzel> tkaiser: I'd guess "impressive" Android games may stress more the GPU than all CPU cores
<tkaiser> Exactly. They still run nicely even if 3 CPU cores were killed already due to short load peaks before
afaerber has quit [Ping timeout: 250 seconds]
<apritzel> so you give it more saner operating points then?
<tkaiser> apritzel: Yes, we increased both count of cpufreq steps to make throttling more efficient, added also more dvfs operating points and tuned the THS settings
<tkaiser> Now BSP kernel starts a shutdown when reaching 108¡C
<tkaiser> And behaves more sane before that happens trying to throttle down instead of killing CPU cores
<tkaiser> apritzel: Temperature between 88¡C and 92¡C at 600 MHz. So with 816 MHz @ 1.1V you can harm to A64 for sure :) At least with cpuburn-a53 or cpuminer
<wens> why would people not put a heatsink on it...
<tkaiser> wens: The only reason my remaining Pine64 doesn't wear one is to compare. But I sent my other Pine64 to another dev in the meantime so that will change soon
<tkaiser> The 'el cheapo' heatsinks for A20 (web search for '20x20 cubie heatsink') for 0.5$ reduce upper temperatures by 10¡C-15¡C
<apritzel> has anyone tried to do those tests without throttling / core-killing? I wonder if the system would crash (so removing the load) or whether the CPU would actually be harmed due to overheating
hansg has joined #linux-sunxi
montjoie has quit [Ping timeout: 260 seconds]
montjoie has joined #linux-sunxi
<tkaiser> apritzel: I had sudden power-offs back then but still no clue what the reason was (PMIC responsibly cutting power or something else)
paulk-leonov has joined #linux-sunxi
<tkaiser> But so far either those mysterious power-offs or shutdown initiated by kernel
buZz has joined #linux-sunxi
enrico_ has joined #linux-sunxi
buZz is now known as Guest88239
<tkaiser> apritzel: How many Pine64 do you have lying around?
enrico__ has quit [Ping timeout: 260 seconds]
<apritzel> tkaiser: ;-) Enough to risk one of them
<tkaiser> apritzel: Nice, then give it a go :)
* apritzel looks for the next fire extinguisher ;-)
afaerber has joined #linux-sunxi
enrico_ has quit [Ping timeout: 244 seconds]
enrico_ has joined #linux-sunxi
cnxsoft has quit [Quit: cnxsoft]
Guest88239 is now known as buZz
<tkaiser> apritzel: With 'stress -m 3 -c 3' temperature at 816MHz@1.08V doesn't exceed 70¡C so I would consider 816MHz as 'safe' unless people want to run special code
<apritzel> tkaiser: thanks a lot for those tests
<apritzel> so I rather keep it at 816 MHz for the time being, until I have some DVFS or throttling in place
enrico_ has quit [Ping timeout: 246 seconds]
enrico_ has joined #linux-sunxi
<tkaiser> apritzel: Or if it's just for testing purposes limit CPU cores to 2 and allow higher clockspeeds?
<apritzel> Personally I rather have 4 lower clocked cores than 2 higher clocked ones
<tkaiser> apritzel: Same with me
<tkaiser> apritzel: BTW: we had the same discussion today regarding throttling behaviour with H3: https://github.com/igorpecovnik/lib/issues/298#issuecomment-219697724
<tkaiser> But there we make use of dvfs already and then all cores at lower clockspeeds are more efficient than less cores at higher clockspeeds
Amit_t_ has joined #linux-sunxi
<tkaiser> apritzel: Did another test with 'sysbench --test=cpu'. This one is that light that I get 88¡C @ 1056MHz/1.24V, so maybe 816 MHz is really too conservative for 'normal' workloads
reinforce has quit [Quit: Leaving.]
<tkaiser> apritzel: Now 'make -j5' with OpenSSL. Throttling limits this to 960MHz@1.16V and temperature slightly exceeds 90¡C
<apritzel> tkaiser: thanks, I will try some tests myself, though I don't have a suitable thermometer which goes beyond 42C ;-)
<apritzel> but those laser gun type ones seem to be cheaper than I expected
<tkaiser> apritzel: All results rely solely on the thermal sensor (to be more precise on the one for the CPU -- according to user manual there are 3 inside. See chapter
<tkaiser> Since all three are there for only one reason -- throttling and over-temperature protection -- I think we can trust the readouts
<tkaiser> If NEON is not used and you make wearing a heatsink a requirement then 960MHz@1.16V should be fine
hansg has quit [Quit: Leaving]
IgorPec has quit [Ping timeout: 250 seconds]
enrico__ has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
enrico_ has quit [Ping timeout: 240 seconds]
orly_owl has quit [Ping timeout: 244 seconds]
<MoeIcenowy> Oh seems that recent Allwinner SoCs are all facing heat problem?
<MoeIcenowy> from H3 to A64
<MoeIcenowy> (I have now only A31s and A33
<buZz> MoeIcenowy: heat problems = needing a heatsink ?
<buZz> or what kinda problems
apritzel has quit [Ping timeout: 244 seconds]
<Amit_t_> What these address(parameters) to this function sunxi_rsb_config(AXP81X_ADDR, 0x3a3) are calculated ?
apritzel has joined #linux-sunxi
<MoeIcenowy> buZz: yes
<tkaiser> MoeIcenowy: I would suspect that's true for most SoCs from this and last year.
<buZz> then its not really a problem, is it?
<buZz> cpus get faster -> need cooling
<buZz> nothing weird, is it?
<MoeIcenowy> tkaiser: yes
<tkaiser> buZz: Heatsinks and even small fans won't help with heavy workloads. You need a thermal sensor inside and code to prevent damage
<buZz> ah, thats not in hw already?
<Amit_t_> I mean, how these address(parameters to this function) sunxi_rsb_config(AXP81X_ADDR, 0x3a3) are calculated ?
<tkaiser> And that's the problem with newer SoCs and mainline kernel: If you use the defaults used by 'vendor kernel' and haven't implemented thermal readouts/throttling damage might occur
The_Loko has quit [Quit: Leaving]
<wens> Amit_t_: they are not calculated
<wens> Amit_t_: the hardware address is hardwired in the pmic
<wens> Amit_t_: the runtime address is from a list of valid addresses
<wens> (there is a description in mainline drivers/bus/sunxi-rsb.c)
drummer_A20 has joined #linux-sunxi
<Amit_t_> wens: Thanks, for axp803 where should I look to find it ?
<wens> all the primary pmics use the same one
<wens> apritzel: ^
<wens> almost forgot about this page
<apritzel> wens: yeah, I found it and I will extended after $work today
<apritzel> including a redirect from RSB ;-)
VargaD has quit [Ping timeout: 250 seconds]
* KotCzarny smells burning pines and brings marshmallows
<tkaiser> apritzel: Graphs from the tests: http://kaiser-edv.de/tmp/4ThBM2/
avph has quit [Ping timeout: 260 seconds]
<tkaiser> apritzel: If you don't need further testings I'll shut the board down since I need the PSU within the next hour
<plaes> KotCzarny: you don't want to do that :P
<KotCzarny> plaes: you are right, not enough supply, i'll bring more twigs to keep them burning
paulk-leonov has quit [Ping timeout: 240 seconds]
<wens> mripard: hi, the chip dts lists ldo5 as an 1.8v regulator, however i don't see this in the schematics
avph has joined #linux-sunxi
massi_ has joined #linux-sunxi
reinforce has joined #linux-sunxi
<apritzel> tkaiser: that much more testing than I could ever hope for, thanks a ton!
<tkaiser> apritzel: Glad to help
<Amit_t_> wens: AXP81X_ADDR is set 0x11 , which I could not really find out how ?
<ssvb> apritzel: just received this W25Q Windbond Serial Flash Memory Module, now only need to solder pin headers to it and do some experiments :-)
<apritzel> ssvb: yeah!
<apritzel> ssvb: do you know how to tell Linux about it properly? the kernel has a "driver" for that particular chip, I just didn't find an easy way to access it (lost in MTD translation)
<ssvb> I don't intend to use Linux, but will rather talk to it directly over SPI
tkaiser has quit [Quit: jIRCii - http://www.oldschoolirc.com]
akaizen has quit [Remote host closed the connection]
<apritzel> well, or that, but I guess you use Linux for that as well (spidev?), don't you? Are there some tools you can recommend?
akaizen has joined #linux-sunxi
nove has joined #linux-sunxi
<wens> Amit_t_: that's an invalid address
<jelle> I wonder how I determined that I have an RDA5991
<jelle> KotCzarny: how do get the usb id for the wifi wiki?
<wens> lsusb
<jelle> oh in linux, or can I do it in android too?
<KotCzarny> you can go cmd line in droid too
<KotCzarny> with adb for example
<jelle> oh nice
<KotCzarny> adb sh
<KotCzarny> or something
<wens> you could then look under /sys/bus/usb
<Amit_t_> its set here in line 656
<KotCzarny> wens, there is a slight chance for lsusb to be installed
<KotCzarny> but there is also dmesg
<jelle> KotCzarny: hmm seems there is no lsusb :p
<KotCzarny> then go for wens' hint
<jelle> <6>[ 25.780563] rda_5991e_wifi_power_on bt_power_on=0
<jelle> ah that was it
<KotCzarny> keep in mind that driver might control different devices
<jelle> well I don't even have the source sdk
<KotCzarny> you only need adb command i think
<KotCzarny> it's statically compiled
<jelle> hmm I wonder if it's usb
<KotCzarny> i have 32bit version if you need it (seems there is only 64bit sdks available nowadays)
<wens> Amit_t_: it's just an id, not the hardware address nor the runtime address
<wens> Amit_t_: see sunxi_rsb_config() on line 560
<KotCzarny> at /sys/bus/usb/devices/*/id*
<KotCzarny> cat /sys/bus/usb/devices/*/id*
<wens> i think rda is sdio based?
<jelle> KotCzarny: there is stuff there
<wens> in which case you would cat /sys/bus/sdio/devices/*/modalias
<jelle> sdio:c07v5449d0145
<wens> you'd get something like sdio:c00v02D0dA962, which is sdio ID 02D0:A962
<wens> bed time
<Amit_t_> ok, Good night.
p1u3sch1 has quit [Ping timeout: 276 seconds]
paulk-collins has joined #linux-sunxi
p1u3sch1 has joined #linux-sunxi
<MoeIcenowy> jelle: you can now fill the Wiki page with the RDA sdio id
<MoeIcenowy> it's 5449:0145
<jelle> MoeIcenowy: will do
vagrantc has joined #linux-sunxi
oliv3r has quit [Remote host closed the connection]
zuikis has joined #linux-sunxi
<apritzel> do we have a DT binding and/or Linux driver for the Allwinner mailboxes yet?
<ssvb> apritzel: for communication with arisc?
<apritzel> possibly, though I was thinking more of communicating with ATF
<apritzel> SCPI transport is via mailboxes
diego71 has quit [Remote host closed the connection]
<apritzel> if we would have a mailbox driver, we'd get the Linux side of DVFS for free
IgorPec has joined #linux-sunxi
leoncito81 has joined #linux-sunxi
<leoncito81> Ok. To I'm a total noob.
<leoncito81> Anyone not?
<leoncito81> Anyone on. Lol. (Stupid autocorrect)
<KotCzarny> freudian slip?
<leoncito81> Lol
<leoncito81> So I found this chat room.
<KotCzarny> if it was autocorrect you would've sent knob instead of noob :P
<leoncito81> Too true.
<leoncito81> And I have minimal programming experience
<KotCzarny> most people were exposed to some programming class in their lives
<leoncito81> What can I do to help move the new A64 chip to mainline kernel
vagrantc has quit [Ping timeout: 260 seconds]
<leoncito81> True. Back on the TRS80
<leoncito81> (Totally dating myself there....)
<MoeIcenowy> leoncito81: mainlining is difficult work
<KotCzarny> test, do bug reports maybe, coerce allwinner to send documentation, those kind of things maybe
<apritzel> leoncito81: get USB and Ethernet working
<apritzel> if you are done with that, come back here ;-)
<apritzel> ;-)
<leoncito81> Lol
<KotCzarny> read and bookmark this page for starters
vagrantc has joined #linux-sunxi
<leoncito81> Ok.
<leoncito81> Bookmark done...
scream has joined #linux-sunxi
<apritzel> leoncito81: you could go through the Pine64 wiki page and try to get something to work. Then either fix the Wiki page or report here what's missing or wrong
<leoncito81> Ok. By try to get something to work, what do you mean?
<apritzel> try to boot some kernel, for instance
<leoncito81> Ok
<jelle> ah my other tablet has an RTL8710AS wifi chip, but I broke android...
<apritzel> assuming you have a board (and assuming it's the Pine64)
<leoncito81> I have one of longsleep's Arch distros up on my pine now
<jelle> *8703AS
diego_ has joined #linux-sunxi
<apritzel> leoncito81: OK, then you could check whether the instructions are any good
diego_ is now known as diego71
<plaes> jelle: check what CHIP has
<leoncito81> Ok. I'll start there.
<apritzel> leoncito81: I have the feeling we are missing a lot here, the people who care know what to do, but other people might get lost
<jelle> plaes: that has a different one
<leoncito81> True
<plaes> jelle: damn realtek :)
<jelle> plaes: oh well more things to do!
<MoeIcenowy> plaes: realtek is much better than espressif :-(
diego71 has quit [Client Quit]
<MoeIcenowy> I now only want to say something dirty to espressif
<apritzel> MoeIcenowy: be expressive about espressif?
<jelle> MoeIcenowy: no docs, no bsp driver?
<plaes> no market so far?
<MoeIcenowy> jelle: nearly no docs
<MoeIcenowy> I have some driver source codes from A33/RK3188 SDKs
<jelle> MoeIcenowy: ahhh
<jelle> RDA you can request documentation but hrrm
<jelle> not sure if that will work
<plaes> MoeIcenowy: at least they have been doing everything right
dev1990 has joined #linux-sunxi
diego_ has joined #linux-sunxi
<plaes> esp8266 is using bsd-licensed software stack
diego_ is now known as diego71
<MoeIcenowy> esp8089's driver is something strange...
<MoeIcenowy> It will first add a dummy sdio driver to the driver list
<MoeIcenowy> to check whether the card is probed by mmc_host
<MoeIcenowy> then it's remove and the real driver is inserted
<MoeIcenowy> after the first time the real driver initialized
<MoeIcenowy> the driver will be unloaded and then loaded again
massi_ has quit [Remote host closed the connection]
<MoeIcenowy> I got drunk.
vickycq has quit [Ping timeout: 244 seconds]
leoncito81_ has joined #linux-sunxi
<KotCzarny> balmer peak coding?
apritzel1 has joined #linux-sunxi
vickycq has joined #linux-sunxi
leoncito81__ has joined #linux-sunxi
<plaes> KotCzarny: legacy code review :P
leoncito81 has quit [Remote host closed the connection]
<KotCzarny> not enough WTFs, must be good enough
matthias_bgg has quit [Ping timeout: 260 seconds]
apritzel has quit [Ping timeout: 244 seconds]
leoncito81_ has quit [Ping timeout: 250 seconds]
staplr has joined #linux-sunxi
leoncito81__ has left #linux-sunxi [#linux-sunxi]
leoncito81__ has joined #linux-sunxi
Netlynx has joined #linux-sunxi
Netlynx has joined #linux-sunxi
IgorPec has quit [Ping timeout: 244 seconds]
enrico__ has quit [Quit: Bye]
leoncito81__ has quit [Remote host closed the connection]
VargaD_ has joined #linux-sunxi
VargaD- has joined #linux-sunxi
VargaD- is now known as VargaD
<MoeIcenowy> how to deal with "probe of mmc0:0001:1 failed with error -110" ...
VargaD_ has quit [Ping timeout: 276 seconds]
leoncito81__ has joined #linux-sunxi
VargaD has quit [Ping timeout: 260 seconds]
leoncito81__ has quit [Remote host closed the connection]
apritzel1 has quit [Ping timeout: 244 seconds]
Mr__Anderson has quit [Quit: Leaving.]
Amit_t_ has quit [Quit: Page closed]
VargaD has joined #linux-sunxi
VargaD_ has joined #linux-sunxi
VargaD has quit [Ping timeout: 260 seconds]
VargaD_ is now known as VargaD
leoncito81__ has joined #linux-sunxi
leoncito81__ has quit [Remote host closed the connection]
ricardocrudo has quit [Remote host closed the connection]
IgorPec11119 has joined #linux-sunxi
<MoeIcenowy> Finally got a wlan1... Hooray.
<MoeIcenowy> (wlan0 is r8712u usb wlan card on otg)
<MoeIcenowy> Hooray!!! I got esp8089 work!!!
VargaD has quit [Ping timeout: 276 seconds]
<plaes> MoeIcenowy: congratz
jernej has joined #linux-sunxi
<MoeIcenowy> https://github.com/Icenowy/esp8089 contains my modified driver source (only deleted some includes specified to rk platform...) and a device tree for Aoson M751s
<MoeIcenowy> I'll now go sleep. Good night everyone.
VargaD has joined #linux-sunxi
<MoeIcenowy> wens: Here's another problem to a "general" q8 dt: some cards (such as esp8089) needs to be re-probed after boot, thus they needs "broken-cd;" in &mmc1 of dt
jstein has joined #linux-sunxi
apritzel has joined #linux-sunxi
p1u3sch1 has quit [Ping timeout: 250 seconds]
leoncito81 has joined #linux-sunxi
p1u3sch1 has joined #linux-sunxi
orly_owl has joined #linux-sunxi
leoncito81__ has joined #linux-sunxi
leoncito81__ has quit [Remote host closed the connection]
leoncito81 has quit [Remote host closed the connection]
Netlynx has quit [Quit: Leaving]
afaerber has quit [Quit: Ex-Chat]
apritzel has quit [Ping timeout: 244 seconds]
sherpa has joined #linux-sunxi
staplr has quit [Read error: No route to host]
vagrantc has quit [Ping timeout: 276 seconds]
vagrantc has joined #linux-sunxi
<KotCzarny> wow, pxz | gzip results in ~58C on my banana
<KotCzarny> first time it went over 48C
<willmore> KotCzarny, got a nice heatsink on there?
<KotCzarny> none
<KotCzarny> :)
IgorPec has joined #linux-sunxi
IgorPec11119 has quit [Ping timeout: 260 seconds]
<jelle> weird can't find anything about the RTL8703S
<MoeIcenowy> jelle: what's the sdio number
<jelle> MoeIcenowy: oh good question
<jelle> MoeIcenowy: sdio:c07v024CdB723
<jelle> returns hits for rtl8723
<MoeIcenowy> jelle: you can try https://github.com/hadess/rtl8723bs
<MoeIcenowy> (I will soon also try to use this driver for rtl8723as
<jelle> this one is not merged?
<MoeIcenowy> jelle: not merged
<jelle> if that works for this chip too :-)
<jelle> hah lsmod shows rtl8150
<jelle> but the chip did read RTL8703 when I opened it
<MoeIcenowy> jelle: stock firmware?
<jelle> MoeIcenowy: android
<MoeIcenowy> jelle: I also found it on my 8723as tablet
<jelle> ahhh
<MoeIcenowy> but i googled and found 8150 to be a wired chip
<jelle> ahhh
<jelle> I wonder what the accel chip is
* jelle looks at this mess mxc622x and gslX680 loaded
<MoeIcenowy> jelle: you may check dmesg
<MoeIcenowy> reboot your device and when the boot animation is done, run dmesg on adb
<MoeIcenowy> then copy the log
<jelle> ok let's see
<jelle> I have a gslx680 yeah
<jelle> MoeIcenowy: well found my accelometer
<MoeIcenowy> jelle: to successfully drive a device, you should at first extract its script.bin
<MoeIcenowy> for example, which firmware does gsl1680 used is stored in the fex (although the firmware will be stored in /vendor/modules/gslX680.ko)
<jelle> MoeIcenowy: yeah I know :-)
afaerber has joined #linux-sunxi
<MoeIcenowy> https://github.com/onitake/gsl-firmware tools/fw_extractor can extract out the firmware from the ko
<jelle> MoeIcenowy: yeah I am aware I already pulled them off
<jelle> maybe upstreaming the accel wouldnt be that hard
<MoeIcenowy> I now have a tablet with at least most functions I needed using mainline kernel...
<jelle> MoeIcenowy: nice
JohnDoe7 has joined #linux-sunxi
zuikis has left #linux-sunxi [#linux-sunxi]
JohnDoe_71Rus has quit [Ping timeout: 244 seconds]
JohnDoe7 has quit [Quit: KVIrc 4.9.2 Aria http://www.kvirc.net/]
iamfrankenstein1 has joined #linux-sunxi
iamfrankenstein has quit [Ping timeout: 250 seconds]
iamfrankenstein1 is now known as iamfrankenstein
oliv3r has joined #linux-sunxi
leoncito81__ has joined #linux-sunxi
leoncito81__ has quit [Remote host closed the connection]
pmattern has quit [Quit: Genug für heute.]
IgorPec has quit [Ping timeout: 276 seconds]
apritzel has joined #linux-sunxi
IgorPec11119 has joined #linux-sunxi
ricardocrudo has joined #linux-sunxi
IgorPec11119 has quit [Ping timeout: 260 seconds]
paulk-collins has quit [Quit: Leaving]
nove has quit [Quit: nove]
ptx0 has quit [Ping timeout: 276 seconds]
fl_0 has quit [Quit: STRG + Q]
ptx0 has joined #linux-sunxi
fl_0 has joined #linux-sunxi
leoncito81__ has joined #linux-sunxi
leoncito81__ has quit [Remote host closed the connection]
jernej_ has joined #linux-sunxi
jernej has quit [Ping timeout: 276 seconds]
raknaz has joined #linux-sunxi
dev1990 has quit [Quit: Konversation terminated!]
andoma has quit [Quit: No Ping reply in 180 seconds.]
andoma has joined #linux-sunxi
scream has quit [Remote host closed the connection]
raknaz has quit [Quit: raknaz]
jstein has quit [Remote host closed the connection]
montjoie has quit [Ping timeout: 260 seconds]
montjoie has joined #linux-sunxi
ricardocrudo has quit [Remote host closed the connection]
reinforce has quit [Quit: Leaving.]
Net147 has quit [Ping timeout: 244 seconds]
Net147 has joined #linux-sunxi
andoma has quit [Ping timeout: 260 seconds]
andoma has joined #linux-sunxi
Sakami_ has quit [Ping timeout: 276 seconds]
vagrantc has quit [Quit: leaving]