<amstan>
so the clock comes from the rtl(clk125) and goes to gpio4_3
<amstan>
which is already pinmuxed to 3 in rk3288.dtsi
<naobsd>
clock comes from rtl(clk125) is for mac
<naobsd>
25MHz clock is for phy
<amstan>
ah
<amstan>
ok, i could check both
<naobsd>
is 25MHz clock fine? (it should, otherwise 125mhz for mac shouldn't be supplied...)
<naobsd>
I have no idea for now...
<amstan>
25MHz looks ok
<amstan>
125 i can't really measure without getting a pretty waveform
<naobsd>
can you try to specify "snps,phy-addr" ?
<naobsd>
I never tried that property so I'm not sure it works...
<amstan>
naobsd: does this work on firefly already?
<amstan>
should i just make snps,phy-addr 0?
<naobsd>
I don't use "snps,phy-addr" in firefly.dts for linux-next
<naobsd>
gmac is working without it
<naobsd>
0 or 1 or something, it depends on board configuration
<naobsd>
debug prints might be needed for mac-phy communication
<naobsd>
I have no idea anymore, please try to see what happen...
eebrah has quit [Quit: Lost terminal]
eebrah has joined #linux-rockchip
<naobsd>
stmmac_mdio_(read|write)
<naobsd>
probably "snps,phy-addr" will not help...
<amstan>
[ 12.557996] eth1: device MAC address 4a:f4:9b:a6:50:ef
<amstan>
[ 12.563150] stmmac_init_phy: trying to attach to stmmac-0:ffffffff
<amstan>
well that's encouraging
<amstan>
it got a mac
<naobsd>
phy addr ffffffff should be -1...
markm has quit [Ping timeout: 252 seconds]
GriefNorth has joined #linux-rockchip
Astralix` has joined #linux-rockchip
Astralix|away has quit [Ping timeout: 264 seconds]
GriefNorth has quit [Remote host closed the connection]
selfbg has joined #linux-rockchip
GriefNorth has joined #linux-rockchip
ttyman has joined #linux-rockchip
<ttyman>
hello to all
<ttyman>
any1 tried to build a Linaro version for Teclast P90HD?
naobsd has quit [Quit: naobsd]
naobsd has joined #linux-rockchip
nighty-_ has joined #linux-rockchip
cnxsoft1 has joined #linux-rockchip
cnxsoft has quit [Ping timeout: 250 seconds]
markm has joined #linux-rockchip
wildea01 has joined #linux-rockchip
naobsd1 has joined #linux-rockchip
naobsd has quit [Ping timeout: 240 seconds]
naobsd has joined #linux-rockchip
naobsd1 has quit [Ping timeout: 265 seconds]
naobsd has quit [Quit: naobsd]
PaowZ_ has quit [Remote host closed the connection]
field^Mop has joined #linux-rockchip
zombu2 has quit [Read error: Connection reset by peer]
zombu2 has joined #linux-rockchip
naobsd has joined #linux-rockchip
field^Mop has quit [Ping timeout: 250 seconds]
* libv
has a date with some pencil pushers at the opposite end of town, so he can go pay some petty amount of taxes
<libv>
but i should return with a 4GB firefly :)
<naobsd>
libv: :)
Omegamoon has joined #linux-rockchip
<naobsd>
hm, stmmac phy regulator fix is not merged to linux-next yet...
cnxsoft1 has quit [Ping timeout: 245 seconds]
<Omegamoon>
hi there, finally found some time to try linux-next
<Omegamoon>
still breaking my head over the device tree... steep learning curve ;-)
ssvb has quit [Ping timeout: 250 seconds]
<Omegamoon>
using the Radxa for now
<Omegamoon>
@naobsd: do you know if USB should work on radxa? I mean, no device is recognized when I plug it in
<rperier>
Omegamoon: if you build your kernel with Dual Role support for USB , as there are no phy-usb for rk3188 the driver won't be initialized. You should configure your kernel to use only the mode "Host" for now
<rperier>
check your kernel logs in case (dmesg)
<rperier>
the host mode works fine
<Omegamoon>
rperier: ah, thanks, I'll try that right away!
<rperier>
could you check your kernel logs about dwc2 driver
<rperier>
please
<rperier>
that's just an idea, perhaps your problem is another thing
<Omegamoon>
sure I will
<Omegamoon>
I think I used host mode before, and switched to dual mode later since no device was recognized
<Omegamoon>
but let me have a look
<mmind00>
Omegamoon: also there is a strange usb-whitelist option, which I had active (for unknown reasons) in the beginning and was then wondering why nothing was recognized :-)
<Omegamoon>
host mode seems to make no difference...
<Omegamoon>
mmind00: what usb-whitelist option are you referring to, do you remember?
<mmind00>
Omegamoon: I think it was USB_OTG_WHITELIST
<mmind00>
Omegamoon: but in your log ... you can already see "platform 101c0000.usb: Driver dwc2 requests probe deferral" and friends
<mmind00>
Omegamoon: but as the "no platform data or transceiver defined" is part of the gadget portion, the log for a host-only compile should look a bit differently
cnxsoft has joined #linux-rockchip
cnxsoft has quit [Remote host closed the connection]
cnxsoft has joined #linux-rockchip
<Omegamoon>
the Host-only log (with verbose debugging) looks very different indeed. see here: http://pastebin.com/c7FtQ9AQ
<Omegamoon>
I'll try the USB_OTG_WHITELIST option now to see if that helps, thanks for that one :-)
<mmind00>
Omegamoon: it should be off :-)
cnxsoft has quit [Quit: cnxsoft]
selfbg has quit [Quit: Leaving]
ssvb has joined #linux-rockchip
<Omegamoon>
mmind00: it was off already :-)
<Omegamoon>
is it a known error that the console is flooded with errors like...
<Omegamoon>
"rtc-hym8563 1-0051: no valid clock/calendar values available"
<Omegamoon>
?
<naobsd>
linux-next works fine for me. I don't have a time to try -stable
<naobsd>
mmind00: do you know what needs to be fixed for "clk: Add rate constraints to clocks" issue?
<naobsd>
that commit is not reverted, I guess SoC specific implementation need to be updated...
<naobsd>
probably I don't understand issue properly :(
<mmind00>
Omegamoon: because your system is trying to read the rtc-time, without the rtc having any valid time information at all
<mmind00>
naobsd: not sure which change you mean, but I guess something from linux-next?
Luke-Jr has quit [Excess Flood]
<mmind00>
naobsd: juding by there not being a clk pull request for 3.20 yet, I guess they're having problems with this already
Luke-Jr has joined #linux-rockchip
<naobsd>
mmind00: yes, clk related change in linux-next
GriefNorth has joined #linux-rockchip
<Omegamoon>
switching from stable to linux-next now, to see if that resolves the USB problems "automagically" ;-)
nighty-_ has quit [Ping timeout: 246 seconds]
nighty-_ has joined #linux-rockchip
Omegamoon has left #linux-rockchip [#linux-rockchip]
ttyman has quit [Quit: Page closed]
bengal has joined #linux-rockchip
nighty^ has quit [Remote host closed the connection]
Astralix` is now known as Astralix|away
sunilmohan has quit [Ping timeout: 250 seconds]
bengal has quit [Ping timeout: 250 seconds]
wildea01 has quit [Quit: leaving]
GriefNorth has quit [Ping timeout: 246 seconds]
VargaD_ has joined #linux-rockchip
VargaD has quit [Ping timeout: 245 seconds]
VargaD_ is now known as VargaD
Luke-Jr has quit [Read error: Connection reset by peer]
Luke-Jr has joined #linux-rockchip
nighty^ has joined #linux-rockchip
field^Mop has joined #linux-rockchip
field^Mop has quit [Ping timeout: 244 seconds]
<amstan>
naobsd: have you ever tried doing rmmod stmmac; modprobe stmmac?
<amstan>
it crashes nicely for me, even though the implicit modprobe at boot works
<mmind00>
amstan: oh great ;-(
<amstan>
mmind00: yeah, see my issue for more details
<amstan>
hmm... firefly has schematics doesn't it?