ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion | Wiki at | Logs at
zombu2 has joined #linux-rockchip
hipboi has quit [Read error: Connection reset by peer]
nick___ has joined #linux-rockchip
nick___ has quit [Client Quit]
hipboi has joined #linux-rockchip
naobsd has quit [Quit: Page closed]
rokite has joined #linux-rockchip
GriefNorth has joined #linux-rockchip
naobsd has joined #linux-rockchip
rokite has left #linux-rockchip ["Leaving"]
<rperier> hi all
<rperier> Arf.... David did not apply the right patch to his repo o.O (v6 instead of v7)
FergusL has quit [Ping timeout: 272 seconds]
dlezcano has quit [Quit: Leaving]
hipboi has quit [Ping timeout: 264 seconds]
hipboi has joined #linux-rockchip
dlezcano has joined #linux-rockchip
FergusL has joined #linux-rockchip
ssvb has quit [Remote host closed the connection]
<naobsd> trying USB on rk3288... root hub found, on-board uhub found, but no device detected under on-board hub...
<naobsd> all 3 ports are under on-board hub...
<naobsd> guess: power?
<naobsd> correct
<naobsd> where is uhub power...
<naobsd> brute force /sys/class/gpio/*?
<naobsd> (I tried some unknown gpio config in original dts)
hipboi_ has joined #linux-rockchip
hipboi has quit [Read error: Connection reset by peer]
nighty^ has joined #linux-rockchip
<naobsd> rk3288 smp patch, great
<naobsd> "rk3288 is dual-core CPU Soc" oh ;)
<naobsd> ah, I understand vbus gpio control... now I can see device under hub
<rperier> naobsd: how did you get a rk3288 board ? throught your work or you just asked to contact@rockchip ?
<naobsd> rperier: I bought consumer STB named CS819II from online shop
<naobsd> mmind00: currently no way to toggle vbus gpio, right? output-high in pinctrl seems not work :(
<naobsd> I confirmed comment out gpio/pinctrl lines in dts, then export /sys/class/gpio/gpioX and set out/1, then I can see devices under hub
<naobsd> rperier: HTC-T031-V0.2 seems almost same as Rockchip's reference (RBOX), firefly's RBOX SDK can be used
<naobsd> rperier: I modified very few lines
<mmind00> naobsd: which gpio is it? gpio0-14?
<naobsd> mmind00: gpio0 14 for host, gpio0 12 for otg
<naobsd> vcc_host: vcc-host-regulator { compatible = "regulator-fixed"; gpio = <&gpio0 14 0>; pinctrl-names = "default"; pinctrl-0 = <&host_vbus_drv>; regulator-name = "vcc_host"; regulator-min-microvolt = <5000000>; regulator-max-microvolt = <5000000>; regulator-always-on; regulator-b
<naobsd> oops
<naobsd> vcc_host: vcc-host-regulator {
<naobsd> compatible = "regulator-fixed";
<naobsd> gpio = <&gpio0 14 0>;
<naobsd> pinctrl-names = "default";
<naobsd> pinctrl-0 = <&host_vbus_drv>;
<naobsd> (snip)
<naobsd> regulator-always-on;
<naobsd> regulator-boot-on;
<naobsd> };
<naobsd> and
<naobsd> pcfg_output_high: pcfg-output-high {
<naobsd> output-high;
<naobsd> (snip)
<naobsd> host_vbus_drv: host-vbus-drv {
<naobsd> rockchip,pins = <0 14 RK_FUNC_GPIO &pcfg_output_high>;
bengal has joined #linux-rockchip
<naobsd> this is current dts, not working :(
<naobsd> I'm sure "echo 1 > /sys/class/gpio/gpio14/value" work (w/o above lines in dts)
<mmind00> it should be pcfg_pull none ... as the regulator-always-on and regulator-boot-on should already make sure that the regulator is active
<mmind00> and your vcc_host needs a "enable-active-high;" property
<naobsd> ah
<naobsd> I see
<naobsd> in RK's original dts for android
<naobsd> host_drv_gpio = <&gpio0 GPIO_B6 GPIO_ACTIVE_LOW>;
<naobsd> are defined, so I removed enable-active-high; :(
<naobsd> I should read docs, sorry ;)
<mmind00> :-D
<naobsd> I don't understand pcfg_pull_* yet :(
<naobsd> probably none should be used for output
<naobsd> up/down depends active_low/high input
<naobsd> works now
<naobsd> mmind00: really thanks!
<naobsd> I'll send some dts to ml
<naobsd> and rk30/31 and rk3288 defconfig updates to github :)
<naobsd> ah otg port cannot be used as host port yet, right?
<naobsd> (it's ok for now)
<naobsd> btw, on 3.10 kernel, I tried "openssl speed -multi 4" and some few benchmark
<naobsd> I saw 93 degree C from tsadc ;)
<naobsd> (with heatsink)
bengal has quit [Ping timeout: 245 seconds]
<naobsd> I guess, 4core full load + GPU load will go 100- degree C ;)
<rperier> naobsd: looking thanks
<naobsd> rperier: I bought it from dealsprime. that shop says it's "in stock" but actually it wasn't. I needed to wait 1.5month to ship
<rperier> in the worth case I can wait for the firefly dev board
<naobsd> any RK3288 box was not ready, of course :)
<naobsd> yes, I recommend firefly and rock2
<rperier> firefly would be an open hardware, so firefly I think
<mmind00> rperier: I think that would be the best option ... you don't get schematics/docs for these android boxes and while all use somehow similar layouts, the small differences are hard to get without schematics
<rperier> I agree
<rperier> that's why I don't want to buy rk3288 box or tablets
<naobsd> I agree too
akaizen has quit [Ping timeout: 272 seconds]
<naobsd> this is first and last buy of non-dev rk3288 product ;)
<naobsd> I just wanted to know what I can do w/o information ;)
<naobsd> or should I try to contact Hotack to get information? :)
<naobsd> I like their boards (HTC-Txxx)
<rperier> mmind00: are there critical tasks for RK3188 SoCs or I can work on adding shutdown support to act8865 (including the mail to devicetree ML about unifying the property) ?
<naobsd> on my rk3288 board, there are 3 LEDs, all of them are same "blue" color, and not blinking.
<naobsd> just a shiny light...
<mmind00> rperier: not sure, there isn't much hardware left :-D ... a big task might be the rk1000 (av-out, audio) ... taking the rockchip driver and cleaning it up so that it could go mainline
<mmind00> otherwise the shutdown issue, is a bit easier to handle I guess [less code, more politics so to speak ;-) ]
<rperier> I am not convinced about rk1000... well for now I can work the shutdown issue. and then, what about the usb driver ? does it work fine ?
<naobsd> I bought RGB->VGA converter for Radxa Rock, I want to try it :)
<naobsd> probably it's same as firefly's VGA
benja` has quit [Ping timeout: 250 seconds]
benja` has joined #linux-rockchip
<mmind00> rperier: basic usb itself works fine, as the usb-phys seem to be in a sane state on bringup, but nevertheless correct usb-phy-drivers would be nice [only warning: it looks like the register layout of the usb-phys in the GRF is somehow different on each soc]
<rperier> which part would need to be fixed exactly ? (you said "correct the usb-phy-drivers")
<mmind00> no "correct usb-phy drivers" ... drivers/phy/*
<mmind00> i.e. there currently are none for the Rockchip phys ... it works without for the moment, but for example the phy driver should handle the regulator supplies when it gets turned on/off ... not how we enable them all the time currently
<mmind00> in my devel/workbench branch is a stub sitting (drivers/phy/phy-rk3066-usb.c) that at least contains the register map for rk3066 and rk3188
akaizen has joined #linux-rockchip
<rperier> ohhh, it would be an interesting contribution indeed (after shutdown in pmic)
<rperier> I add it to my todolist :)
hipboi_ has quit [Ping timeout: 245 seconds]
GriefNorth has quit [Ping timeout: 240 seconds]
hipboi_ has joined #linux-rockchip
viric_ has joined #linux-rockchip
viric has quit [Ping timeout: 252 seconds]
viric_ is now known as viric
viric has quit [Ping timeout: 245 seconds]
viric has joined #linux-rockchip
naobsd has quit [Quit: Page closed]
benja` is now known as benja
naobsd has joined #linux-rockchip
naobsd has quit [Quit: Page closed]
naobsd has joined #linux-rockchip
mrueg has quit [Remote host closed the connection]
mrueg has joined #linux-rockchip
viric has quit [Ping timeout: 268 seconds]
viric has joined #linux-rockchip
ssvb has joined #linux-rockchip
Raen has joined #linux-rockchip
<Raen> Hi guys
<Raen> mind if I ask you some questions?)
<karlp> always best to just ask
<Raen> sry, first time here, don't know your ground rules.. So here is the question: I'm trying to compile 3.0.36 kernel for rk3066 tablet with rk610 chip. Everything's fine, kernel boots, dmesg good, backlight and panels lights up, but everything i get is just black screen.
<Raen> Lo there is some problem in feeding rk610 with data from lcdc, i suppose
<Raen> So what can I do with this? I've seen that rk610 driver has some changes between different sources, maybe it's broken in latest rk3188 4.4.2 box?
cedinu has quit [Ping timeout: 246 seconds]
<naobsd> primary LCDC is selected properly? (I don't know about RK610)
<Raen> afaik yes. It's defined in board.c, right? But here's some strange finding - I've have working self-compiled 3.0.8 kernel, where lcdc0 set as primary, but in rk610 chineese manual (judging only by pictures) rk610 is using lcdc0 for hdmi output, and 1 for lvds
<Raen> and strange fact 2 - even though it has lvds output the panel selected in 8 kernel is rgb type
<Raen> so can it be, that easipix sourcel are heavily modified in some wierd way, where lcdc are switched and panel selection are hardcoded somewhere?
<naobsd> no idea, sorry
<naobsd> which 3.0.36 kernel are you using?
<Raen> well, i've tried rk3188 4.4.2 basic, modified from your git repo (stable branch) and old ones from rk3188 (4.2I suppose). bq curie are hard to use, since they are too different, so i decided not to adapt to them at this point
<Raen> in theory - if i pull everything from 3.0.8 regarding video drivers (except rk_fb) - will it work (I mean kernel in general, not in my case)? And since I want it for kitkat, that fb changes are made in generic fb, or rk_fb?
GriefNorth has joined #linux-rockchip
<Raen> Oh, GriefNorth. I've been using your surf1011 repo at the beggining. Do you know anything abour rk610 in rk3066?
bengal has joined #linux-rockchip
nighty^ has quit [Quit: Disappears in a puff of smoke]
Raen has quit [Quit: Page closed]
akaizen has quit [Read error: Connection reset by peer]
akaizen has joined #linux-rockchip
npcomp has quit [Ping timeout: 246 seconds]
npcomp has joined #linux-rockchip
npcomp has quit [Ping timeout: 245 seconds]
npcomp has joined #linux-rockchip
GriefNorth has quit [Read error: Connection reset by peer]
npcomp has quit [Ping timeout: 240 seconds]
npcomp has joined #linux-rockchip
benja has quit [Ping timeout: 252 seconds]
benja has joined #linux-rockchip
bengal has quit [Ping timeout: 255 seconds]
_whitelogger has joined #linux-rockchip
_whitelogger has joined #linux-rockchip