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
abdul_pt_ has left #linux-rockchip [#linux-rockchip]
levd has joined #linux-rockchip
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 244 seconds]
markm_ has quit [Read error: Connection reset by peer]
levd1 has quit [Remote host closed the connection]
levd has joined #linux-rockchip
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 256 seconds]
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 264 seconds]
akaizen has quit [Remote host closed the connection]
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 264 seconds]
nighty^ has quit [Quit: Disappears in a puff of smoke]
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 264 seconds]
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 256 seconds]
cnxsoft has joined #linux-rockchip
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 264 seconds]
field^Mop has joined #linux-rockchip
field^Mop has quit [Ping timeout: 256 seconds]
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 245 seconds]
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 244 seconds]
RayFlower_ has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 252 seconds]
levd1 has quit [Quit: levd1]
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
naobsd has quit [Quit: naobsd]
libv has quit [Ping timeout: 240 seconds]
libv has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
naobsd has joined #linux-rockchip
ferric has quit [Ping timeout: 245 seconds]
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
dlezcano has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
dlezcano has quit [Ping timeout: 255 seconds]
dlezcano has joined #linux-rockchip
ferric has joined #linux-rockchip
ferric has quit [Ping timeout: 265 seconds]
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
c0d3z3r0 has quit [Ping timeout: 255 seconds]
jas-hacks has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
ferric has joined #linux-rockchip
ferric has quit [Ping timeout: 245 seconds]
naobsd has quit [Quit: naobsd]
cnxsoft1 has joined #linux-rockchip
cnxsoft has quit [Ping timeout: 256 seconds]
AstralixNB has joined #linux-rockchip
Astralix has joined #linux-rockchip
dlezcano has quit [Ping timeout: 255 seconds]
dlezcano has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
dlezcano has quit [Ping timeout: 264 seconds]
dlezcano has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
dlezcano has quit [Ping timeout: 255 seconds]
dlezcano_ has joined #linux-rockchip
dlezcano_ has quit [Ping timeout: 264 seconds]
dlezcano_ has joined #linux-rockchip
dlezcano_ has quit [Ping timeout: 265 seconds]
dlezcano_ has joined #linux-rockchip
c0d3z3r0 has joined #linux-rockchip
npcomp has quit [Ping timeout: 244 seconds]
npcomp has joined #linux-rockchip
dlezcano_ has quit [Ping timeout: 245 seconds]
dlezcano_ has joined #linux-rockchip
dlezcano_ has quit [Ping timeout: 244 seconds]
BorgCuba has joined #linux-rockchip
<BorgCuba> is there some echo "1" > proc ??? command to enable the framebuffer (on hdmi)
dlezcano_ has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
cnxsoft1 has quit [Quit: cnxsoft1]
naobsd has joined #linux-rockchip
jas-hacks has left #linux-rockchip [#linux-rockchip]
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
<rperier> AstralixNB: around ? what partition did you flash on the firefly with mainline kernel ?
libv has quit [Ping timeout: 240 seconds]
libv has joined #linux-rockchip
<rperier> AstralixNB: I found it myself, I activated console in uboot then I flashed kernel.img and finally I typed "bootrk kernel" which works fine ;)
<rperier> it is almost the same thing than on the rock with uboot, I just use "booti kernel" instead of "bootrk kernel" :)
<BorgCuba> rperier, have you tested the phy driver?
<BorgCuba> and maybe the otg (in device mode)
ferric has joined #linux-rockchip
dlezcano_ has quit [Quit: Leaving]
ferric has quit [Ping timeout: 264 seconds]
<rperier> BorgCuba: yes, I would like to ask you, how did you deal with the fifo allocation issue ?
<rperier> BorgCuba: normally it is read in the hw configuration
<rperier> I played a bit with phy usb on the rock and now I am playing with my firefly which I did not test yet until today :)
<BorgCuba> rperier, I have no answer. I tried some patches from the linux-usb mailing list, but this did not solve the issue
<BorgCuba> but there is a new patch series which is based on some other usb repo, I havent tried that
<rperier> Ok, I will investigate. Perhaps it is a bug in the usb driver (I already fixed one recently)
<BorgCuba> that would be really cool!
<rperier> I don't think that it is something really serious
<BorgCuba> If I can help you I will
<BorgCuba> I could provide you with the patch files
<rperier> what I found is that when the fifo size is changed in the hw configuration it is not really accepted and applied, because when I get the size after the allocation is seems to be equal to zero
<rperier> s/is seems/it seems/
<BorgCuba> from this cfg register? what was it cfg3?
<BorgCuba> btw, this is the first patch series: http://www.spinics.net/lists/linux-usb/index.html#118894
<BorgCuba> this allows to specify the fifo size in the dts
<rperier> so perhaps the driver is not 100% working with the usb variant on rockchip or it is just a bug not known yet...
<BorgCuba> and this is the second one: http://www.spinics.net/lists/linux-usb/index.html#119481
<BorgCuba> there is one patch for fifo allocation
<BorgCuba> maybe this one is interesting: http://www.spinics.net/lists/linux-usb/msg119505.html
<rperier> did you post all of these patches ? :O
<BorgCuba> no
<rperier> good to know anyway, thanks for these info. I will follow this ML I think
<BorgCuba> I think the guy who posted them is working for samsung and probably testing it on some exynos variant
<BorgCuba> btw, I got the otg driver for the old 3.0.36 kernel running in device more (tested with serial and ethernet gadget)
<BorgCuba> mode
<rperier> and it is working ? feel free to post a patch for rk3066a.dtsi and for your board if it is supported on mainline
<rperier> nice
<rperier> oh for 3.0.36, ignore my comment I did read too quickly ^^
<rperier> (I am reading several irc chans in the same time, does not help :p)
<naobsd> updating firefly dts for mainline...
<BorgCuba> np, btw, are you interested to test some buildroot patches for rk3188 with mali400 framebuffer support later?
<BorgCuba> I am till testing and I am using the old 3.0.36 kernel for this
<naobsd> what's mali400 framebuffer?
<BorgCuba> its the mali400 gpu (with OpenGL ES 1.1 and 2.0 drivers) without x11
<BorgCuba> the drivers come from here: https://github.com/linux-sunxi/sunxi-mali-proprietary
<BorgCuba> but there are also binaries for x11
<BorgCuba> seems to be working: pastebin.com/hP74KFER (but I havent yet connected a display, to see if it is really working)
<naobsd> ah, libmali for framebuffer, I see...
<BorgCuba> naobsd, btw I am using the kernel driver from your page for this: http://androtab.info/radxa_rock/mali/
<naobsd> it will be nice if rockchip releases libmali for fb/x11 for mali r4 kernel driver...
<BorgCuba> well, these binaries from linux-sunxi should work
<BorgCuba> the malitest and maliver programs do work
<naobsd> I just talked about r4
<BorgCuba> and xbmc doesnt give any errors
<BorgCuba> ahh, okay
<BorgCuba> btw, I have some problems with my hdmi->vga adapter (it does not work)
<BorgCuba> and I noticed that out of tree building does not work for the 3.0.36 kernel
<naobsd> some Makefile need to be fixed for out of tree build
<naobsd> few lines in mack-rk3* and somewhere for wifi
<rperier> naobsd: you seem to have worked on rk3288-firefly.dts, do you plan to send a patch for review ?
<naobsd> I'll send it after this update
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
ganbold_ has quit [Ping timeout: 255 seconds]
jas-hacks has joined #linux-rockchip
<jas-hacks> mmind00: do you know about 'pm_domian.c'? I'm trying to figure out how it decides to power down/up a domain.
<mmind00> jas-hacks: power domains are normally bound to devices and if I remember the runtime-pm subsystem. So when the driver does runtime_pm_get the power domain gets enabled and after the last runtime_pm_put (when refcount 0) it gets disabled again
<mmind00> jas-hacks: all powerdomains start as active on boot, so it's more a matter of reducing power consumption by turning off unused domains
<BorgCuba> mmind00, is your pll patch already in the current linux-next?
<mmind00> BorgCuba: which pll patch ... the rk3066 fix? ... my pull request for the clock tree is still pending
<BorgCuba> yes, that one. but okay, so its not.
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
<jas-hacks> mmind00: Trying to workout what would keep the VOP domain from powering down
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
field^Mop has joined #linux-rockchip
<mmind00> jas-hacks: in current mainline, nothing should currently touch the powerdomains at all ... what makes you think they are "powering-down"?
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
<jas-hacks> mmind00: Not mainline, I'm debugging the chromeos kernel (3.14)
<mmind00> jas-hacks: ah ok ... you had me worried here :-)
<BorgCuba> what does this mean: [ 40.724131] HDCP: hdcp_irq_cb 0x00 0x00
<BorgCuba> [ 41.224074] HDCP: HDCP: Error reg 0x65 = 0x00
<jas-hacks> mmind00: ... trying to get drm to output to hdmi
field^Mop has quit [Ping timeout: 240 seconds]
<jas-hacks> mmind00: yay .... finally screen output with drm http://postimg.org/image/r8pw39o6r/
<mmind00> jas-hacks: \o/
<mmind00> jas-hacks: any interesting findings on how you got it working?
<jas-hacks> mmind00: I've ending up using the Android act8846 code initially get had going.
<jas-hacks> mmind00: After that spent weeks trying to work why no screen output, it turns the VOP domain is power domain for some reason (not sure why yet). So I patched it out of the dtsi as a hack.
<jas-hacks> mmind00: no that makes sense ... lets try again
<jas-hacks> I've ending up using the Android act8846 code initially to get going.
<jas-hacks> After that spent weeks trying to work why no screen output, it turns out the VOP domain is powering domain for some reason (not sure why yet). So I patched it out of the dtsi as a hack.
<rperier> why do rockchip introduce "phy_regulator" in the gmac node ... ? we don't have a standard property for that ?
<mmind00> rperier: yep this phy_regulator voilates quite some expectations
<mmind00> rperier: it should be phy-supply and actually a reference to the regulator and not referenced by name
<rperier> I totally agree
<rperier> it should reference a device_node
<rperier> and use the corresponding API from code
<rperier> (there is an of api for phy)
<rperier> I try to enable gmac on the firefly, this is why I have just saw it
<mmind00> rperier: the whole series went into http://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/log/?qt=grep&q=rockchip, so if you got it running, you try to refactor this :-)
<mmind00> rperier: as it just went in, changing this now would be the easiest way - before it gets actually released
<rperier> yes, indeed, I will have a look at it and update it if things are wrong
<rperier> and phy_power_on should not set the voltage directly right (regulator_set_voltage at 3v3) ? I mean depending on the board the regulator might be fixed or not it might be also handled by a pmic
<rperier> I mean, it can be directly put in the dts
<naobsd> hmm, vccio_sd need to be always-on for firefly, otherwise some i2c unit seems dead :(
<naobsd> rperier: gmac is working here, updated dts will be pushed soon...
<rperier> oh already working ?
<rperier> nice
<rperier> so I will work on refactoring dwmmac_rk a bit directly in this case
<naobsd> any idea about "thermal thermal_zone1: failed to read out thermal zone 1"? (same for zone2)
<naobsd> about gmac, it seems realtek phy driver cannot be used...
<naobsd> stmmac driver have own phy driver?
<BorgCuba> can this work: ccflags-$(CONFIG_RK_HDMI_DEBUG) = -DDEBUG -DHDMI_DEBUG
<BorgCuba> ?
<naobsd> I'll split some lines for firefly-beta into another dts
<naobsd> then I'll send patch to ML
<rperier> ok cool
<naobsd> I want to fix arc emac issue too
<naobsd> if there is any easy reproduce procedure, please tell me... setting up NFS is not so handy for me now ;)
<rperier> you can get a defconfig for NFS in meta-rockchip (under recipes-kernel/linux), you need to start a dhcp server and a nfs server on your machine, directly connected to your board throught a ethernet cable, both machine must to be in the same network
<naobsd> I know very well about how to setup NFS server...
<rperier> from a boot to another you should reproduce problems easily, sometimes connection timeouts with the server
<naobsd> I'm just lazy...
<rperier> yes, but as I do all my contributions in my free time, I did not had time to fix it. but yeah it's boring
<rperier> ssh might help too
<rperier> issues I had were with nfs and ssh
<naobsd> I see
<naobsd> hmmmm I should disable tsadc on firefly for now
ganbold_ has joined #linux-rockchip
jas-hacks has left #linux-rockchip [#linux-rockchip]
<naobsd> if my memory is correct, dwc hdmi for rk3288 is merged, right?
<naobsd> and drm part was already merged too
<naobsd> then we can use hdmi out
<naobsd> right?
<naobsd> sleeeepy
<naobsd> good night
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
<mmind00> naobsd: drm is in the current -rc kernels and dw_hdmi will most likely be part of 3.20
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
RayFlower_ has quit [Client Quit]
ferric has joined #linux-rockchip
ferric has quit [Ping timeout: 245 seconds]
BorgCuba has quit [Quit: leaving]
FreezingCold has quit [Quit: Out]
paowz has joined #linux-rockchip
ferric has joined #linux-rockchip
ferric has quit [Ping timeout: 256 seconds]
Danukeru has quit [Remote host closed the connection]
Danukeru has joined #linux-rockchip