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
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
levd has joined #linux-rockchip
Tony_ has joined #linux-rockchip
benja` has quit [Ping timeout: 256 seconds]
benja` has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
naosd has quit [Quit: Page closed]
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 244 seconds]
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 264 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
levd1 has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
levd has quit [Ping timeout: 265 seconds]
naobsd has joined #linux-rockchip
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 255 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 244 seconds]
Bludot has joined #linux-rockchip
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 244 seconds]
<Tony_> the windows OS can run on rk3188 ?
<Tony_> I think the advertisements is lying.
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 265 seconds]
<naobsd> advertisement?
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 240 seconds]
<Tony_> Yes, an android Big screen(21'') table based rk3188 company said.
<Tony_> I don't know anything about windows 0S on rk3188. so I think they lied.
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 245 seconds]
naobsd has quit [Ping timeout: 246 seconds]
naobsd has joined #linux-rockchip
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 240 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 264 seconds]
Astralix1 has joined #linux-rockchip
Astralix has quit [Ping timeout: 250 seconds]
GriefNorth has joined #linux-rockchip
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 265 seconds]
ildar has joined #linux-rockchip
ildar has quit [Client Quit]
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 272 seconds]
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 240 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
Bludot has quit [Quit: Connection closed for inactivity]
dlezcano has joined #linux-rockchip
levd1 has joined #linux-rockchip
hipboi_ has joined #linux-rockchip
levd has quit [Ping timeout: 258 seconds]
hipboi has quit [Ping timeout: 250 seconds]
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 255 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
levd1 has joined #linux-rockchip
AstralixNB has joined #linux-rockchip
levd has quit [Ping timeout: 240 seconds]
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 244 seconds]
dlezcano has quit [Ping timeout: 255 seconds]
dlezcano has joined #linux-rockchip
antoinemaillard has joined #linux-rockchip
dlezcano has quit [Ping timeout: 250 seconds]
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 250 seconds]
<LinuxBot_> hi all
dlezcano has joined #linux-rockchip
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 264 seconds]
<rperier> hi all
antoinemaillard_ has joined #linux-rockchip
antoinemaillard has quit [Ping timeout: 264 seconds]
antoinemaillard_ is now known as antoinemaillard
dlezcano has quit [Quit: Leaving]
dlezcano has joined #linux-rockchip
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 264 seconds]
<Tony_> Hi all.
<Tony_> an question about HDMI. what's the useful of 11 pin.
<Tony_> TMDS Clock Shield
<Tony_> It connect nothing.
<Valduare> speaking of hdmi - are devices working with hdmi-cec yet
<Valduare> my mk808 devices dont
levd has joined #linux-rockchip
ildar has joined #linux-rockchip
levd1 has quit [Ping timeout: 255 seconds]
<Tony_> oh, my board used the rk616.
<Tony_> It works fine.
<Valduare> whats your bord
<naobsd> oh, rk616 supports cec? interesting. it66121 also has some support for cec, but document/driver is almost useless ;)
<Tony_> sorry, my CEC(13) is connected with GND.
levd1 has joined #linux-rockchip
<Tony_> naobsd, can you tell me what's the useful of (11 TMDS Clock Shield).
levd has quit [Ping timeout: 265 seconds]
wildea01 has joined #linux-rockchip
<naobsd> gpio?
<naobsd> ^gnd? gpio?
<naobsd> and no idea about tmds, sorry
<Tony_> <Valduare> my board is RK official board.
<Valduare> ah
<Tony_> okay, how about SCL AND SDA of HDMI.
<Valduare> im looking at a cheap chinese tablet with rk chip in it - wonder if it supports cec
levd1 has quit [Ping timeout: 250 seconds]
<Tony_> I can't get any signal from I2C of HDMI.
<Tony_> <Valduare> If I fond the one , I will tell you immediately. :)
<karlp> cec sounds like it failed completly,
<Tony_> really ?
<Tony_> I don't think so.
<Tony_> And actually, I want to know about DDC of HDMI.
<Tony_> I can't get any signor from OSC.
<Tony_> <naobsd> the DDC document/driver is almost useless too?
Valduare has quit [Quit: Valduare]
Tony_ has quit [Remote host closed the connection]
ildar has quit [Quit: Leaving.]
nighty-_ has joined #linux-rockchip
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
Tony_ has joined #linux-rockchip
Tony_ has quit [Remote host closed the connection]
dlan has quit [Ping timeout: 272 seconds]
dlan has joined #linux-rockchip
dlan has quit [Ping timeout: 244 seconds]
dlan has joined #linux-rockchip
dlan has quit [Ping timeout: 240 seconds]
dlan has joined #linux-rockchip
dlan has quit [Ping timeout: 255 seconds]
antoinemaillard has quit [Quit: antoinemaillard]
dlan has joined #linux-rockchip
mrcan has quit [Quit: pai]
bengal has joined #linux-rockchip
antoinemaillard has joined #linux-rockchip
dlan has quit [Ping timeout: 250 seconds]
dlan has joined #linux-rockchip
bengal has quit [Ping timeout: 240 seconds]
mrcan has joined #linux-rockchip
dlan has quit [Ping timeout: 244 seconds]
Guest89001 has joined #linux-rockchip
naobsd has quit [Quit: Page closed]
Guest89001 has quit [Remote host closed the connection]
dlan_ has joined #linux-rockchip
dlan_ has joined #linux-rockchip
dlan_ has quit [Changing host]
dlan_ has quit [Remote host closed the connection]
dlan_ has joined #linux-rockchip
dlan_ has quit [Ping timeout: 245 seconds]
dlan_ has joined #linux-rockchip
Tony__ has joined #linux-rockchip
hipboi_ has quit [Quit: Leaving]
GriefNorth has quit [Quit: WeeChat 1.0.1]
dlan_ is now known as dlan
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
Qi999 has joined #linux-rockchip
amstan has quit [Ping timeout: 240 seconds]
amstan has joined #linux-rockchip
Tony__ has quit [Remote host closed the connection]
mrcan has quit [Ping timeout: 264 seconds]
mrcan has joined #linux-rockchip
mrcan has joined #linux-rockchip
AstralixNB has quit [Ping timeout: 250 seconds]
RayFlower has joined #linux-rockchip
ZZambia has quit [Remote host closed the connection]
antoinemaillard has quit [Ping timeout: 250 seconds]
dlan has quit [Ping timeout: 264 seconds]
dlan has joined #linux-rockchip
dlan has quit [Ping timeout: 250 seconds]
dlan has joined #linux-rockchip
dlan has quit [Ping timeout: 272 seconds]
dlan has joined #linux-rockchip
Valduare has joined #linux-rockchip
wildea01 has quit [Quit: leaving]
ildar 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
bengal has joined #linux-rockchip
dlezcano has quit [Ping timeout: 255 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
cosm has joined #linux-rockchip
Valduare has quit [Quit: Valduare]
<amstan> is there a way i can get the name of the clock somehow?
ildar has left #linux-rockchip ["PING 1415994297"]
Valduare has joined #linux-rockchip
ildar has joined #linux-rockchip
ildar has left #linux-rockchip [#linux-rockchip]
Qi999 has quit [Ping timeout: 240 seconds]
<mmind00> amstan: __clk_get_name(hw->clk) should work
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
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
<amstan> mmind00: cool, it works, thanks!
FreezingCold has quit [Ping timeout: 265 seconds]
<amstan> mmind00: i'm about to post it to the mailing list
<amstan> mmind00: mind if i add you as a suggested-by? doug said you're the one that came with the idea
<mmind00> amstan: sure :-)
<mmind00> amstan: do you know how far the integration into the mmc driver has progressed?
<amstan> mmind00: well, that series i have on gerrit works pretty well(except the one card, which addy has hack commits for)
<amstan> doug suggests we move that to dw_mmc.c so it's common code
<amstan> i still need to add hooks for the dts properties, right now everything's just hardcoded
<mmind00> amstan: I'm just trying to determine if we need the new clock-ids (dt-bindings/...) to be separate
<amstan> as a dependency to this patch?
<mmind00> amstan: i.e. when both the clock declarations and the driver + dts changes make it into the 3.19 code we'll need a shared branch for the clock-ids that gets merged into both the clock-branch and the dts-branch
<mmind00> amstan: it would be a series ... patch1 add the clock-ids to the binding-header, patch2 add the clk code
<amstan> patch1 will surely be pretty small and useless by itself
<amstan> i don't really like the idea, but if that's what needs to be done, i can split it up if you want
<mmind00> amstan: yep, but you would need the clock-id in both the clock-code (v3.19-clk/next) as well as in the devicetree stuff (v3.19-armsoc/dts)
<mmind00> amstan: that was the reason for my asking ... if the devicetree + mmc driver stuff is not expected to be accepted in time, we can skip this split
<mmind00> amstan: just as an example ... we had a similar situation for the armclk in 3.18: https://git.kernel.org/cgit/linux/kernel/git/mmind/linux-rockchip.git/commit/?h=v3.18-next/dts&id=4d742e6230b5ff157422d91d6ae8d2fc1303eb28
<mmind00> amstan: which then needed to get merged into two different branches: https://git.kernel.org/cgit/linux/kernel/git/mmind/linux-rockchip.git/commit/?h=v3.18-next/dts&id=c2cb11e6e586c935362c8f03ab4f464fe06d0c78 and https://git.kernel.org/cgit/linux/kernel/git/mmind/linux-rockchip.git/commit/?h=v3.18-next/cpuclk&id=f79c3c015485374b4f453932c45fbcb80a75a1a9
<amstan> mmind00: hmm, alright, i get it
<amstan> mmind00: so the idea is that i'll send https://chromium-review.googlesource.com/#/c/229387 soon upstream as well, and they won't really care if i drivers/clk/rockchip/clk-mmc-phase.c because all that dtsi needs is just the change in include/dt-bindings/clock/rk3288-cru.h
<mmind00> amstan: correct, the mmc code does not care how you create the target phase and the clock stuff does not care what you do with it ;-)
<mmind00> amstan: but of course it might be nice to link both together in cover-letters :-)
<amstan> assuming i know how to use patman... lol
<mmind00> :-D ... most of the time I only use git format-patch and git send-email (for bigger series) or my general mailclient (single patches or so)
dlezcano has quit [Ping timeout: 265 seconds]
<amstan> mmind00: do you just copy+paste git diffs to emails? for single patches?
dlezcano has joined #linux-rockchip
<mmind00> amstan: yep for single patches ... i.e. git format-patch and just subject line into the mail subject and the diff + commit message into the mail body ... of course the mailer should not line-wrap nor do html-crazyness ;-)
<amstan> mmind00: yeah, i don't trust gmail to not do that
<amstan> and apparently inbox.google.com always sends html stuff
<mmind00> amstan: gmail can do imap + smtp so you can use a sane mail client ;-)
bengal has quit [Quit: Leaving]
<amstan> yeah, but i like the gmail ui
<amstan> so far..
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
ildar has joined #linux-rockchip
dlezcano has quit [Remote host closed the connection]
<amstan> mmind00: alright! sent!
<amstan> darn, patman didn't unionize the addresses, so only 2/2 got to patchwork(linux-rockchip@lists.infradead.org)
FreezingCold has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
FreezingCold has quit [Ping timeout: 244 seconds]
<karlp> just for my own curiosity, why do you need to adjust phase of sdmcc clock? is to work around what? bad cards? do you need to change this often?
<karlp> or is this badly laid boards with connectors that are introducing unexpected phase shifts?
<karlp> s/badly//g no need to blame the hw dudes
<amstan> karlp: at 200MHz bad stuff happens
<karlp> right, but pushing the phase, this is board layout related right?
<amstan> probably
<amstan> but there might be variations in the chip
<karlp> is this sdxc only I presume?
<amstan> whatever runs at a fast clock speed(above 50MHz?)
<karlp> huh, I didn't know SDIO was open collector
<amstan> i don't think it is
<amstan> there might be mild pullups just to keep the lines from floating, but i'm sure they driven from both sides
<karlp> oh, seems to be in init mode
<karlp> due to the legacy idea of "yeah, let's put 30 mmc cards on the same bus"
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
<amstan> mmind00: nooo! how could i have left that there? lol
<mmind00> amstan: hehe ... happens to everyone occasionally :-D
<amstan> alright, respinning
<amstan> and sending it to all the people now
<karlp> amstan: but this phase setting is definitely something that you expect to be completely ignored by most people right? you only use this at all if you'r eboard is exhibiting reliability problems with sd cards?
<amstan> karlp: i don't think the users will ever have to do this
<amstan> karlp: i'm going to follow my patch with some tuning code, so every time you plug in the card it'll try a bunch of angles and pick the middle/safest one
<amstan> it's pretty much instant
<karlp> ok, you're doing it for every card?
<karlp> that's what I was curious about, I thought I saw that there were dt bindings for this, so I assumed this was for the layout of an sd connector, but doint it for every card is a different game altogether
<karlp> how do you decide what the "safest/middle" on is?
<amstan> try 45 degree increments
<amstan> and you should see something like [ 1021.070009] candidates=0xfe ranges: 0 45* 90* 135* 180* 225* 270* 315* 1 good ranges found:45-315(7) best:45-315(7) middle=180
<amstan> the * are the angles that work
<amstan> then you pick an angle as far away as possible from the angles that don't work
<karlp> is this common? I'm not deep in sdmmc code, but I wouldn't have thought you'd need to adjust the _phase_ so much _per card_
<amstan> exynos does the same thing
<amstan> grep for execute_tuning
<karlp> exynos does lots of things, not entirely sure all of them ar egood ideas :)
<karlp> but again, not my field :)