ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion | Wiki at http://linux-rockchip.info | Logs at http://irclog.whitequark.org/linux-rockchip | ML at http://groups.google.com/group/linux-rockchip
<naobsd> I think there is not so much registers for usb phy
<mmind00> naobsd: there are some registers grf_uoc0_con0 and friends
<mmind00> the currently posted phy driver uses only one bit, but there are quite some more functions
levd has joined #linux-rockchip
<ganbold_> naobsd: boot loops in t-firefly
<ganbold_> oh, it boots to shell after several boot loop
levd1 has joined #linux-rockchip
<naobsd> ganbold_: strange
<naobsd> I tested several times
<naobsd> ganbold_: which power supply are you using?
<naobsd> ganbold_: is fan connected to proper pins(fan+/-)? or disconnected?
levd has quit [Ping timeout: 244 seconds]
Tony_ has quit [Read error: Connection reset by peer]
<ganbold_> oh, fan is ok, I'm using iphone power adapter so that is why maybe
<ganbold_> :D
<jmcneill> evening
<jmcneill> i broke down and ordered a radxa lite
<ganbold_> cool :)
<jmcneill> firefly was tempting but i couldn't find the trm
<ganbold_> naobsd: where was rk3288 trm?
<ganbold_> I think hipboi has it
<jmcneill> i haven't been through rk3188 trm yet, how is it?
<jmcneill> awin a80 driving me crazy with omissions
<BorgCuba> ganbold_, where is the loop point?
<hipboi> ganbold_, yes, we do have it
BorgCuba has quit [Quit: leaving]
<ganbold_> hipboi: jmcneill is netbsd developer
<hipboi> oh, hi, jmcneill :)
<jmcneill> hi!
<ganbold_> jmcneill: hipboi is Tom Cubie :)
<jmcneill> famous guy
<ganbold_> jmcneill: now you know him :)
<jmcneill> i'm going to have to get an rk3288 now aren't i
<hipboi> jmcneill, yes
<jmcneill> arg
<jmcneill> are you still involved with cubietech?
<hipboi> jmcneill, no
levd has joined #linux-rockchip
<hipboi> jmcneill, Lee is now the owner of cubietech
<jmcneill> ah, so you won't mind then that rockchip will distract me from netbsd/cubie work :)
<hipboi> jmcneill, i am open minded, it's the open market
<jmcneill> omissions in a80 trm have made my cubie4 work challenging
levd1 has quit [Ping timeout: 255 seconds]
<jmcneill> no mention of hdmi in the user manual at all :(
<ganbold_> jmcneill is very fast :)
<jmcneill> how is rockchip on freebsd, ganbold?
<ganbold_> jmcneill: I have Radxa Rock ES and basic stuff works
<ganbold_> and SMP
<jmcneill> awesome
<jmcneill> is that your dmesg on the raxda wiki?
<ganbold_> yes
cnxsoft has joined #linux-rockchip
<jmcneill> es is 3088?
<ganbold_> 3188
<jmcneill> or the 3088 drivers happen to be compatible?
<ganbold_> I think it was 3066
<ganbold_> dual core A9
<jmcneill> well that's good
<jmcneill> hopefully 3288 is somewhat compatible as well
<jmcneill> i'll get one once i can get my hands on the trm
<ganbold_> jmcneill: ask hipboi, maybe he has 3188 trm too :)
<hipboi> ganbold_, 3188 trm is public
<jmcneill> 3188 is public
<hipboi> with other socs from rockchip
<hipboi> rockchip.fr
<jmcneill> looks like there are some omissions as well
<hipboi> julien collected them
<ganbold_> oh, yes, rockchip.fr
<ganbold_> cool
levd1 has joined #linux-rockchip
<jmcneill> nand, emmc, gpu, vcodec, ipp, rga, efuse -- all "see also <some doc you dont have>.pdf"
levd has quit [Ping timeout: 252 seconds]
<hipboi> the exception is the px2 trm
<hipboi> px2 trm has more than rk3xxx
<jmcneill> are the modules similar or the same?
<naobsd> yes, PX2 has some more info not "see also"
<naobsd> PX2 TRM
<hipboi> px2 is basically rk3066
<naobsd> RK3066/RK3188/RK3288 are similar, but some units are different a little
<naobsd> emmc/sdmmc is dwc
<naobsd> usb otg/host is also dwc
<jmcneill> should get your stuff checked in
<jmcneill> thanks for the px2 tip, that looks helpful
<naobsd> there are a lot of things to do for NetBSD/rk :(
<jmcneill> I'll help.
<jmcneill> What's done so far?
<ganbold_> I may need your help too, I'm not really peripheral guy, still learning
<naobsd> tokuda-san did few things, and no progress lately
<jmcneill> Sure, don't hesitate to ask.
<jmcneill> If only I had the board sooner, I start vacation today. If there is something to merge, I can do that in the meantime.
<naobsd> but very dirty, cannot merge yet ;)
<jmcneill> Bummer.
<ganbold_> oh, maybe I should have sent to you ifc6410 :)
<naobsd> tokuda-san and I are busy...
<jmcneill> I forgot about that one.
<jmcneill> naobsd, let me know when it is ready then. I still have some A80 stuff to do in the meantime
<naobsd> jmcneill: I see
<naobsd> I want to clean that code
<naobsd> I want to take video "fxos runs on RR" at first ;)
<jmcneill> I might suggest making obio look like awin_io.c
<jmcneill> Almost like it, anyway.
_andrew_ has quit [Quit: I'll be back]
<jmcneill> It's worked really well so far. The only thing I don't like is that the offsets are relative to core bsh.
<naobsd> I think tokuda-san re-used some other code as a base
<jmcneill> It worked fine for A20 and A31, but A80 is different.
<jmcneill> As long as other code isn't omap. arch/arm/omap is scary.
<naobsd> haha
<jmcneill> omap_obio.c obio_ohci.c omap_ohci.c
<jmcneill> made my head hurt
<ganbold_> jmcneill: I have extra ifc6410, do you want it?
<jmcneill> don't want to make too many commitments, ask me again when i get rk3188 working
<ganbold_> :)
<jmcneill> maybe ask nick?
<ganbold_> I see
<naobsd> jmcneill: http://androtab.info/rockchip/u-boot/ it may be better to use u-boot
<jmcneill> oh you don't use uboot?
cnxsoft has quit [Read error: Connection reset by peer]
<jmcneill> ok for development but not practical otherwise :)
<naobsd> u-boot for rk is currently very limited
<jmcneill> can't be worse than some of the sunxi stuff
<naobsd> no standard drivers such as mmc, ether, msdos, etc
<ganbold_> seems t-firefly has u-boot
cnxsoft has joined #linux-rockchip
<jmcneill> oh, msdos and sdhc would be nice
<naobsd> ganbold_: for rk3288, only u-boot is provided for consumer android products (there are some other bootloader for chrome os device)
<ganbold_> I see
<naobsd> jmcneill: RK u-boot uses own nand/sdmmc driver which only does raw access to load kernel/ramdisk etc
<naobsd> of course we can modify u-boot
<jmcneill> ah that's not too bad then
<jmcneill> as long as i can put a kernel on an sd card from osx i'm happy
<naobsd> jmcneill: then both proprietary bootloader and u-boot can be used for it
<jmcneill> giddyup
<naobsd> jmcneill: if you don't want to write kernel to sd so much, rkflashtool is handly
<jmcneill> i'm used to it
<jmcneill> i actually ordered another rk3188 earlier today, but i don't know if it has uart pins
<jmcneill> from a retailer here in canada, and it's already shipped
<ganbold_> naobsd: so does rkflashtool work for rk3288?
<naobsd> for RR lite, of course you need to put loader on sd at least
<jmcneill> minix neo x7
<naobsd> jmcneill: can I see photo?
<naobsd> ganbold_: rockusb protocol is same
<ganbold_> ok, how to stop at u-boot prompt?, it boots android
<naobsd> I'm not sure they didn't change board, generally board is changed very frequently for such a cheap products
<naobsd> and I don't recommend to non-open product, it's hard to get pin configuration etc without schematic/kernel source
<jmcneill> I may end up returning it.
<naobsd> ganbold_: probably recompile is required
<naobsd> ganbold_: and prompt should be useless for now
<naobsd> ganbold_: almost no driver
<ganbold_> ok, then maybe flash kernel using rkflashtool
<ganbold_> or does it boot from SD?
<naobsd> ganbold_: it seems latest u-boot for rk3288 (on emmc) can load kernel etc from sd
<naobsd> ganbold_: btw load kernel via otg with rkflashtool is not implemented on u-boot rk3288
<jmcneill> ganbold, any mali support in freebsd?
<ganbold_> naobsd: I may need your instruction/help later, when I have time to try
<ganbold_> jmcneill: no
<naobsd> ganbold_: "fastboot boot" can be used to load kernel without flashing
<naobsd> ganbold_: I see
<ganbold_> naobsd: oh, really
<jmcneill> i won't bother asking about sgx then :)
<naobsd> ganbold_: you can flash kernel with rkflashtool
<ganbold_> naobsd: that should be useful too, so I don't have to worry about bricking
<naobsd> "load kernel to RAM" is not implemented on u-boot rk3288
<naobsd> "load kernel to RAM" with rkflashtool is not implemented on u-boot rk3288
<naobsd> but "fastboot boot" does it
<ganbold_> ok, maybe I will try fastboot first
<ganbold_> naobsd: how does it go to fastboot mode?
<naobsd> oh
<naobsd> well
<naobsd> no standard way with shipped loader
<naobsd> you may need to modify u-boot to go fastboot mode with "recovery key" (it's for rockusb mode by default)
<ganbold_> maybe some jumper thing or maybe some buttons press?
<naobsd> jmcneill: no, it doesn't give any information for development
<naobsd> jmcneill: ah, please don't believe random blogs
<naobsd> well, it seems there is sdk for x7
<jmcneill> never lose hope :)
<naobsd> there are many blogs/forums about rockchip devices, but most of them are not so reliable
<naobsd> please ask me about rockchip dev thing
<naobsd> I cannot guarantee random blog is reliable
<naobsd> probably some(very few) might be reliable, but I don't know which one
<naobsd> oops
<naobsd> u-boot side is not on github yet :(
<naobsd> ganbold_: you can go fastboot via rockusb with modified rkflashtool/u-boot
<naobsd> but please wait for a moment, I'm not sure my u-boot bin on my site include that modification...
<ganbold_> naobsd: I will try later, so take your time :)
Tony_ has joined #linux-rockchip
<naobsd> this is only reliable info about x7 for now
<naobsd> please ask me about any rk thing
<naobsd> most articles on forums/blogs are unreliable, or just outdated
<naobsd> here is the reliable place ;)
<naobsd> please don't care about "linux-" part of community name ;)
<Tony_> naobsd, is it possible porting AP6330 to Ubuntu ?
<Tony_> naobsd, have you try it ?
<jmcneill> sdio on netbsd would be nice
<jmcneill> <-- not volunteering
<naobsd> Tony_: porting? why it doesn't work?
<naobsd> I think it just work
<Tony_> I think because of firmware or other case.
<naobsd> I guess sdio support is not maintained on NetBSD... I know kiyohara-san tried some long time ago...
<naobsd> Tony_: firmware should be needed, of couse
<jmcneill> All I saw was a bluetooth driver, not sure if it ever worked.
<naobsd> Tony_: please do same as Android
<jmcneill> I didn't spend much time with it but I couldn't make it detect anything on my A31 board.
<naobsd> jmcneill: I recommend allwinner board to kiyohara-san, he might have interest again ;)
<Tony_> naobsd, I think so too, but I know a little about WiFi driver on Android.
<Tony_> naobsd, ;(
<naobsd> I recommended
<jmcneill> That would be great
<naobsd> but lately he is busy too ;)
<naobsd> he married and had baby :)
<jmcneill> Didn't stop me (but it did slow me down)
<jmcneill> The only things missing from A20 are Mali and wifi/bt I think.
<jmcneill> oh and nand
<jmcneill> same story for A31 except s/Mali/SGX/
<jmcneill> and for some reason I can't figure out otg on my board
<naobsd> as host?
<jmcneill> yeah
<jmcneill> works on my cubie2, no device detected on merrii hummingbird a31
<jmcneill> i think just gpio setup -- like you say about unreliable info
<naobsd> stock fex .bin is sometimes wrong ;)
<jmcneill> i used the one from sunxi-boards, i've seen a lot of issues with them
<jmcneill> cubie2 one for the longest time (maybe it's fixed now?) had gmac pins setup as emac
<jmcneill> i wasted a good week trying to figure out why the emac driver couldn't detect a phy on my board
<naobsd> cb2 has only fast ethernet, so using emac is not "wrong"
<naobsd> as stock config
<jmcneill> it uses gmac with a 100mbit phy
<naobsd> I prefer to use gmac with fast ethernet phy
<naobsd> emac can be used too
<jmcneill> oh i didn't know that
<naobsd> A20 has both mac
<jmcneill> i knew that, wasn't aware that it was possible to use both on cb2
<jmcneill> i certainly got nowhere with emac on cb2
<naobsd> probably stock Android uses emac, only community driven u-boot/linux kernel uses gmac
<naobsd> anyway it's just matter of pin configuration
<Tony_> naobsd, miniroot's WiFi can works fine ?
<naobsd> well
levd has joined #linux-rockchip
<naobsd> well...
<naobsd> Tony_: my miniroot does nothing for wifi, but you may use wifi with my miniroot
levd1 has quit [Ping timeout: 245 seconds]
<Tony_> naobsd, than you. I will posting it on your miniroot at first.
<Tony_> ;)
<naobsd> miniroot is miniroot, not kernel nor driver nor firmware
<naobsd> it does nothing
<naobsd> _you_ need to do something for wifi
<naobsd> please do same as android
<naobsd> prepare firmware, load driver, run supplicant or something
<Tony_> naobsd, yep, I'm clear now. I figure it out on Android.
zhanzs has joined #linux-rockchip
<Tony_> at first.
zhanzs has quit [Ping timeout: 246 seconds]
<jmcneill> zzz
jmcneill has quit [Quit: Leaving]
<Tony_> jmcneill, what's "zzz" ?
<Tony_> jmcneill, sleep ?
<ganbold_> yes :)
<Tony_> ah, now here is noon.
AstralixNB1 has joined #linux-rockchip
AstralixNB has quit [Ping timeout: 250 seconds]
lerc has quit [Read error: Connection reset by peer]
levd has quit [Remote host closed the connection]
levd has joined #linux-rockchip
lerc has joined #linux-rockchip
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 244 seconds]
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 255 seconds]
levd has quit [Remote host closed the connection]
levd has joined #linux-rockchip
Danukeru has quit [Ping timeout: 250 seconds]
Danukeru has joined #linux-rockchip
<Tony_> naobsd, hi, the wifi ko is rkwifi.ko ?
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 250 seconds]
<Tony_> naobsd, after I install rkwifi.ko, there are some unknow log.
<Tony_> naobsd, with ifconfig -a, I can see the "wlan0".
<Tony_> naobsd, but I can run "ifconfig wlan0 up"
<Tony_> naobsd, it say that "SIOCSIFFLAGS: Operation not permitted"
levd has joined #linux-rockchip
<naobsd> Tony_: please check driver is correct, then please search how to use wifi on ubuntu
levd1 has quit [Ping timeout: 250 seconds]
<Tony_> naobsd, there are two things I can't ensure. ;) the ko is correct or not and how to use wifi on ubuntu.
<naobsd> sorry, I'm very busy now
<Tony_> naobsd, okay, I will try it myself. ;)
naobsd has quit [Ping timeout: 246 seconds]
Avagetto has joined #linux-rockchip
<Tony_> who can help me ?
<Tony_> always out put this info:
<Tony_> [ 128.101367] ANDROID-ERROR) wifi_set_power = 0
<Tony_> [ 128.308711] ANDROID-ERROR) wifi_set_power = 1
<Tony_> when I insmod rkwifi.ko.
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 250 seconds]
Avagetto1 has joined #linux-rockchip
Avagetto has quit [Read error: Connection reset by peer]
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 240 seconds]
Avagetto1 has left #linux-rockchip [#linux-rockchip]
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 240 seconds]
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 244 seconds]
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 256 seconds]
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 245 seconds]
arokux has quit [Remote host closed the connection]
antoinemaillard has joined #linux-rockchip
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 244 seconds]
dlezcano_ has quit [Ping timeout: 244 seconds]
cnxsoft1 has joined #linux-rockchip
cnxsoft has quit [Ping timeout: 240 seconds]
dlezcano_ has joined #linux-rockchip
dlezcano_ has quit [Ping timeout: 240 seconds]
dlezcano_ has joined #linux-rockchip
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 264 seconds]
dlezcano_ has quit [Ping timeout: 264 seconds]
dlezcano_ has joined #linux-rockchip
naobsd has joined #linux-rockchip
<naobsd> cnxsoft1: ping
<Tony_> naobsd, can you help me ? ;)
<Tony_> naobsd, about WiFi on Ubuntu.
<naobsd> Tony_: about driver/module for wifi, please use same one as Android on your board
<Tony_> naobsd, Yes, I'm sure I use the same module, but the case is not same. so I'm confused.
<naobsd> then I'm confused too...
<naobsd> I don't have your board, I don't know any detail :(
<Tony_> naobsd, there are diff file between android and ubuntu.
<Tony_> naobsd, I use the same module rkwifi.ko.
<Tony_> naobsd, I'm very confused. pls help me.
levd has quit [Remote host closed the connection]
levd has joined #linux-rockchip
Tony_ has quit [Remote host closed the connection]
<naobsd> Tony_: are you using same kernel for android and linux?
markm_ has quit [Ping timeout: 255 seconds]
levd has quit [Ping timeout: 272 seconds]
dlezcano_ has quit [Ping timeout: 244 seconds]
dlezcano_ has joined #linux-rockchip
<cnxsoft1> naobsd
BorgCuba has joined #linux-rockchip
<naobsd> cnxsoft1: it seems "sign-in with twitter" on chipspark.com is working now
<naobsd> cnxsoft1: and chipspark said that documents/source code for PopMetal will be provided soon
<BorgCuba> hi, I am looking into the usb-phy stuff for the rk3066 (maybe this applies to the other socs as well) and it looks like its a synopsys "nano-phy".
<BorgCuba> is there already some driver available for this ip in the kernel?
<cnxsoft1> Good.
sats861 has joined #linux-rockchip
<sats861> hi!
<sats861> who have kernek 3288.git
<sats861> ?
antoinemaillard has quit [Quit: antoinemaillard]
dlezcano_ has quit [Ping timeout: 250 seconds]
dlezcano_ has joined #linux-rockchip
markm_ has joined #linux-rockchip
<AstralixNB1> BorgCuba, I started to do the same, but I ignored a little cold that I had and it cam back and brought some friends... so the last two days wheren't so happy to me.
dlezcano_ has quit [Ping timeout: 272 seconds]
dlezcano_ has joined #linux-rockchip
naobsd has quit [Ping timeout: 246 seconds]
<BorgCuba> AstralixNB1, so you were looking into adding missing sub phy support? thats great! I am only starting and havent done something like this before. But I am pretty sure that its the designware/synopsys nanophy
cnxsoft1 has quit [Ping timeout: 265 seconds]
<AstralixNB1> There is a driver for 3288 proposed to mainline. And I guess the best is to use that one and extend it to 31/30
<AstralixNB1> I already dfownloaded these sources, but then got interrupted ...#
<BorgCuba> the block diagram for the phy from the rk30xx trm is the same like the one in this doc http://wenku.baidu.com/view/7f1aad6a58fafab069dc020d.html and in the description for GRF_UOC0_CON0:12 the term "USB 2.0 nanoPHY" is mentioned
<AstralixNB1> I do have all needed information for all the chip. But thanks
<BorgCuba> AstralixNB1, I installed that patch
<BorgCuba> although I haven't yet tested it
<AstralixNB1> Yes, RK reuses very much of their IPs. Why not, they have paid the license fees for usage and if they work...
<AstralixNB1> I am a bit locked at xmas preparations for the family, so I will not do much more nbefore tonight.
<BorgCuba> btw, maybe the exynos 4 also uses this phy (they are using dwc2 at least)
<BorgCuba> do your preparations and get rid of your cold! :)
<BorgCuba> I am already half prepared
<AstralixNB1> That is possible. but the last times I checked the drivers, the Exynos varied veery mauch from the RK part.
<BorgCuba> AstralixNB1, do you happen to have a copy of the rk3288 trm? I really wanted to have a look to compare it to the rk30xx trm
dlezcano_ has quit [Ping timeout: 256 seconds]
<AstralixNB1> Ah... These TRMs are bound to NDA, so you will not have very much success to get a complete one from an official source
<AstralixNB1> Let me check that for you later
<AstralixNB1> have to go now
naobsd has joined #linux-rockchip
dlezcano_ has joined #linux-rockchip
<naobsd> ganbold_: -kernel repo should be kernel subtree of full sdk tree
<naobsd> ganbold_: firefly-rk3288.dts is the right one
<BorgCuba> I am especially interested in "reg = <0x320>;" for rk3288
<AstralixNB1> BorgCuba, the comparision of RK30xxx and 32xx is very complicated as the manuals have grown... The RK30xx are some first trials to document something, while the 31xx is the first thing that you might call a TRM. However I'll try to line these addresses and bits up for all three of them as good as I can
<AstralixNB1> 0x320 is an offset?
<ganbold_> naobsd: yeah, still includes rk3288.dtsi
<naobsd> ganbold_: ah, yes
<naobsd> ganbold_: is your firefly stable now?
<AstralixNB1> at least, both, 30xx and 32xx have basic USB and USB PHY bits well spread around GRF registers
dlezcano_ has quit [Ping timeout: 245 seconds]
dlezcano_ has joined #linux-rockchip
<ganbold_> naobsd: it should be ok, with original power adapter boot didn't loop
<AstralixNB1> BorgCuba, in RK3288 this offset is GRF but in RK30xx it is not available. So there will be some remapping tables needed
<AstralixNB1> But I have to leave now. See you later
<BorgCuba> AstralixNB1, I think for rk30xx its 0x178
<BorgCuba> (bit 13 - siddq)
<BorgCuba> AstralixNB1, for the rk30xx we have GRF_UOC0_CON0..2 and GRF_UOC1_CON0..3 (0x17c .. 0x194)
<BorgCuba> well, and its not 0x178 but 0x17c (the grf reg offset)
dlezcano_ has quit [Ping timeout: 256 seconds]
dlezcano_ has joined #linux-rockchip
<rperier> you need to implement a devicetree variant for that, reuse the phy-usb driver for rockchip, refactorize it and then add a devicetree variant to support rk3066/r3188
jmcneill has joined #linux-rockchip
<AstralixNB1> hi reperier
<rperier> hi AstralixNB1
<AstralixNB1> rperier, do you have a already accepted example for this refactoring. So we can avoid style issues when implementing that.
dlezcano_ has quit [*.net *.split]
c0d3z3r0 has quit [*.net *.split]
eebrah has quit [*.net *.split]
akaizen_ has quit [*.net *.split]
mmind00 has quit [*.net *.split]
zombu2 has quit [*.net *.split]
ssvb has quit [*.net *.split]
leirbag has quit [*.net *.split]
else- has quit [*.net *.split]
honx has quit [*.net *.split]
lerc has quit [*.net *.split]
mrueg has quit [*.net *.split]
Luke-Jr has quit [*.net *.split]
Danukeru has quit [*.net *.split]
ChanServ has quit [*.net *.split]
RaYmAn has quit [*.net *.split]
mrcan has quit [*.net *.split]
phh has quit [*.net *.split]
FreezingCold has quit [*.net *.split]
hipboi has quit [*.net *.split]
FergusL has quit [*.net *.split]
ganbold_ has quit [*.net *.split]
nashpa has quit [*.net *.split]
dianders has quit [*.net *.split]
rperier has quit [*.net *.split]
killbit has quit [*.net *.split]
architekt has quit [*.net *.split]
khilman has quit [*.net *.split]
VargaD has quit [*.net *.split]
npcomp has quit [*.net *.split]
karlp has quit [*.net *.split]
maz has quit [*.net *.split]
naobsd has quit [*.net *.split]
sats861 has quit [*.net *.split]
BorgCuba has quit [*.net *.split]
AstralixNB1 has quit [*.net *.split]
libv has quit [*.net *.split]
strange has quit [*.net *.split]
ynezz has quit [*.net *.split]
amstan has quit [*.net *.split]
johnsu01 has quit [*.net *.split]
zoobab_ has quit [*.net *.split]
khilman has joined #linux-rockchip
RaYmAn has joined #linux-rockchip
ynezz has joined #linux-rockchip
architekt has joined #linux-rockchip
ChanServ has joined #linux-rockchip
dianders has joined #linux-rockchip
maz has joined #linux-rockchip
phh has joined #linux-rockchip
mrcan has joined #linux-rockchip
karlp has joined #linux-rockchip
strange has joined #linux-rockchip
rperier has joined #linux-rockchip
zoobab_ has joined #linux-rockchip
libv has joined #linux-rockchip
npcomp has joined #linux-rockchip
hipboi has joined #linux-rockchip
johnsu01 has joined #linux-rockchip
FergusL has joined #linux-rockchip
killbit has joined #linux-rockchip
nashpa has joined #linux-rockchip
Luke-Jr has joined #linux-rockchip
VargaD has joined #linux-rockchip
amstan has joined #linux-rockchip
ganbold_ has joined #linux-rockchip
FreezingCold has joined #linux-rockchip
AstralixNB1 has joined #linux-rockchip
Danukeru has joined #linux-rockchip
BorgCuba has joined #linux-rockchip
sats861 has joined #linux-rockchip
naobsd has joined #linux-rockchip
dlezcano_ has joined #linux-rockchip
c0d3z3r0 has joined #linux-rockchip
eebrah has joined #linux-rockchip
leirbag has joined #linux-rockchip
<BorgCuba> yes
cnxsoft has joined #linux-rockchip
lerc has joined #linux-rockchip
mrueg has joined #linux-rockchip
<BorgCuba> rperier, any idea?
<rperier> when dwc2 try to use/enable your phy usb... something goes wrong apparently... did you look at /home/jan/devel/rk30xx/linux-next-3.19.0-rc1-next-20141221/drivers/usb/dwc2/gadget.c:202 ?
<rperier> also try to find the point from where the message "insufficient fifo memory" is emitted, it might help
<BorgCuba> yes, its a WARN_ONCE
<naobsd> sleepy, restoring github repos will be done tomorrow...
<naobsd> I want to restore u-boot repo asap...zzz...
<BorgCuba> fetch yourself a coffee ;-)
<BorgCuba> okay, so the fifo size is taken from GHWCFG3 (+0x4c) (line 3067)
<BorgCuba> and the reset value according to the ds i 0x0
cnxsoft has quit [Ping timeout: 250 seconds]
cnxsoft has joined #linux-rockchip
cnxsoft has quit [Read error: Connection reset by peer]
cnxsoft has joined #linux-rockchip
<BorgCuba> rperier, why do you think this is related to the phy?
cnxsoft has quit [Read error: Connection reset by peer]
cnxsoft has joined #linux-rockchip
nighty^ has joined #linux-rockchip
cnxsoft has quit [Remote host closed the connection]
dlezcano_ has quit [Ping timeout: 244 seconds]
mrcan has quit [Ping timeout: 264 seconds]
dlezcano_ has joined #linux-rockchip
dlezcano_ has quit [Ping timeout: 252 seconds]
dlezcano_ has joined #linux-rockchip
<BorgCuba> okay, I strongly suspect that the code in "s3c_hsotg_init_fifo" is broken
antoinemaillard has joined #linux-rockchip
mrcan has joined #linux-rockchip
mrcan has quit [Changing host]
mrcan has joined #linux-rockchip
<BorgCuba> btw, if somebody wants to try out the rk3288 phy for rk3066 or rk3188 just apply these patches: https://patchwork.kernel.org/patch/5482861,5482881,5482901,5482931.2991 and modify the dts(i) files for your device accordingly + enable the driver in .config
AstralixNB1 has quit [Remote host closed the connection]
<BorgCuba> ohh, the reg values are 0x17c for phy0 and 0x188 for phy1 (otg)
<BorgCuba> for rk3066
dlezcano_ has quit [Ping timeout: 250 seconds]
dlezcano_ has joined #linux-rockchip
dlezcano_ has quit [Ping timeout: 252 seconds]
dlezcano_ has joined #linux-rockchip
sats861 has quit [Ping timeout: 246 seconds]
<mmind00> BorgCuba: I see the pll locking issue now too on my marsboard ... the pll-init code itself is most likely innocent, but exposes a problem of the pll code
<mmind00> BorgCuba: I'll try to hunt this down
dlezcano_ has quit [Ping timeout: 264 seconds]
dlezcano_ has joined #linux-rockchip
_andrew_ has joined #linux-rockchip
mrcan has quit [Ping timeout: 244 seconds]
field^Mop has joined #linux-rockchip
mrcan has joined #linux-rockchip
mrcan has quit [Changing host]
mrcan has joined #linux-rockchip
field^Mop has quit [Ping timeout: 256 seconds]
<BorgCuba> mmind00, thank you for taking a look at the pll issue
<BorgCuba> mmind00, the dwc2 gadget seems to have some problems. But as you said this is probably wip and I already saw someone on the mailing list reported something similar (http://www.kernelhub.org/?msg=652138&p=2)
<BorgCuba> mmind00, if you are interested in enabling the usb2 phy driver for your marsboard I could prepare something for you?
paowz has joined #linux-rockchip
<mmind00> BorgCuba: as rperier already said, you should extend the proposed rk3288 phy driver with support for the older variants ... the dw-nano-phy doesn't count here, as the access to the phys on all socs is done via the GRF registers
<BorgCuba> I think it is working?
<BorgCuba> I mean I can see on the pc that it tries to enumerate and something inside the gadget driver seems to fail
<BorgCuba> mmind00, let me post a boot log
<BorgCuba> here it is: http://pastebin.com/5pf3rwPB
<BorgCuba> I build the dwc2 with all debugging message options activated
JohnDoe_71Rus has joined #linux-rockchip
<BorgCuba> mmind00, basically the driver is very simple, it only turns on the phy (bit 13 of GRF_UOC0_CON0). So I didnt even have to change anything in the driver, I only had to plug in the correct register offset in the dts file (0x17c and 0x188 for rk30xx)
<BorgCuba> what makes you guys think that the issue I am facing is related to the phy driver?
<BorgCuba> I mean its possible, but I dont see this at the moment.
PaowZ_ has joined #linux-rockchip
paowz has quit [Ping timeout: 252 seconds]
<mmind00> BorgCuba: I haven't had to much contact with the dwc2 itself except following patches for it a bit ... so I've also only skimmed through the stuff you talked with rperier(?) and Astraix(?) about
<mmind00> BorgCuba: so I'm probably not the best person to talk to about dwc2 issues
<BorgCuba> btw, I think Ive never seen a rk3xxx kernel with working usb gadget driver. I only have some uboot code for rk30xxx that I have tested and that works
PaowZ__ has joined #linux-rockchip
PaowZ_ has quit [Ping timeout: 244 seconds]
paowz has joined #linux-rockchip
antoinemaillard has quit [Quit: antoinemaillard]
PaowZ_ has joined #linux-rockchip
PaowZ__ has quit [Ping timeout: 255 seconds]
antoinemaillard has joined #linux-rockchip
antoinemaillard has quit [Client Quit]
paowz has quit [Ping timeout: 264 seconds]
dlezcano_ has quit [Ping timeout: 264 seconds]
<rperier> dwc2 is buggy with recent changes on some stuffs, I can confirm that
dlezcano_ has joined #linux-rockchip
antoinemaillard has joined #linux-rockchip
paowz has joined #linux-rockchip
<BorgCuba> rperier, have you already tested the phy???
dlezcano_ has quit [Ping timeout: 240 seconds]
dlezcano_ has joined #linux-rockchip
<BorgCuba> I think it works, but its always good to have someone else to confirm/deny
PaowZ_ has quit [Ping timeout: 240 seconds]
antoinemaillard has quit [Ping timeout: 245 seconds]
dlezcano_ has quit [Ping timeout: 245 seconds]
dlezcano_ has joined #linux-rockchip
<rperier> BorgCuba: no, however I already tested and fixed some things dwc2, and I found that it was buggy since 3.18 (I use 3.19-rc1 here, same issues with linux-next)
<rperier> mhhh... interesting... with the usb ttl converter from radxa (the green one) my uart debug is very stable
<BorgCuba> too bad, I am using 3.19.0-rc1-next-20141221 (only the gadget part)
<rperier> so it has really to do with the usb ttl converter...
<rperier> (sorry, it's another issue I had early)
<rperier> :)
<BorgCuba> rperier, so you also have uart problems?
<rperier> I had uart issues on my radxa rock pro
<rperier> which I did not have with my radxa rock first edition
<rperier> but with the good usb ttl converter, it seems to be solved
<rperier> so good news
<BorgCuba> I have problems with my rk3188 and rk3188t boxes
<rperier> with uart2 ?
<BorgCuba> with the default debug uart
<BorgCuba> i.e. the one also used by the rock-loader
<BorgCuba> and the ddr init
<BorgCuba> I measured the voltage level on one board and it was like approx 3V while my ft232 also pulls the rx line up to 3v3
<BorgCuba> I think next time I will build a little opamp buffer maybe a use a fast opto (but I'll have to look at the ds before - how many mA the rk-tx pin can drive)
paowz has quit [Ping timeout: 264 seconds]
paowz has joined #linux-rockchip
dlezcano_ has quit [Ping timeout: 250 seconds]
dlezcano_ has joined #linux-rockchip
paowz has quit [Ping timeout: 250 seconds]
akaizen has joined #linux-rockchip
RayFlower has joined #linux-rockchip
JohnDoe_71Rus has quit [Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/]
dlezcano_ has quit [Ping timeout: 264 seconds]
dlezcano_ has joined #linux-rockchip
akaizen_ has joined #linux-rockchip
akaizen has quit [Ping timeout: 244 seconds]
dlezcano_ has quit [Ping timeout: 272 seconds]
dlezcano_ has joined #linux-rockchip
nighty^ has quit [Read error: Connection reset by peer]
nighty^ has joined #linux-rockchip
nighty^ has quit [Read error: Connection reset by peer]
nighty^ has joined #linux-rockchip
bengal has joined #linux-rockchip
naobsd has quit [Quit: Page closed]
mrueg has quit [Read error: Connection reset by peer]
mrueg has joined #linux-rockchip
bengal has quit [Ping timeout: 252 seconds]