ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion | IRC log | Community GH | Rockchip GH | ML
anarsoul|2 has quit [Remote host closed the connection]
anarsoul|2 has joined #linux-rockchip
vicencb has quit [Quit: Leaving.]
vagrantc has quit [Quit: leaving]
anarsoul|2 has quit [Ping timeout: 240 seconds]
vstehle has quit [Ping timeout: 264 seconds]
field^Mop has joined #linux-rockchip
field^Zzz4 has quit [Ping timeout: 245 seconds]
BenG83 has quit [Ping timeout: 250 seconds]
vstehle has joined #linux-rockchip
somy has quit [Ping timeout: 260 seconds]
somy has joined #linux-rockchip
<tomeu> mmind00, beeble: I was using bootm
<tomeu> just saw a message from ezequiel mentioning that he uses booti, and with that it's starting to boot
<tomeu> so thanks!
<mmind00> tomeu: great to hear that
<tomeu> mmind00: now that I have your attention, what's the best to upstream this? the DTs I'm using are from downstream linux-4.4 and rkboot, without any significant changes so far
<tomeu> the nanop[ic] *4 boards all share a common base DT
<mmind00> tomeu: are they actually different?
<tomeu> mmind00: the nanopc-T4 I have doesn't have any changes other than the name board, but the others do have changes
<mmind00> tomeu: i.e. the base-dtsi approach is somewhat common, see vamrs,ficus + rock960
<mmind00> tomeu: but it's interesting to find out beforehand if that are all real products ... like we don't add all CrOS board revisions, but only those that actually shipped
<tomeu> I think they are, let me check
<tomeu> not sure why downstream calls them rev00, rev01 and rev04 though
<tomeu> as they look more like variants than revisions
<mmind00> tomeu: yep, like 3 boards and at least the compatibles match the products
<mmind00> tomeu: so I guess for mainlining ... drop the vendor properties "mach", "rk_wlan" + bluetooth ... check for properties we have in rk3399.dtsi already (I noticed #sound-dai-cells) ... and ideally invert the delete-property things
<mmind00> tomeu: i.e. they define mmc-hs400-1_8v in the nanopi.dtsi only to delete it again in 2 boards, so that should simply only be defined in the one board using it
<tomeu> cool, sounds like a start
<mmind00> tomeu: other than that I guess it would be cool to also keep that separation ... with it being 3 boards ... don't forget to add entries to Documentation/devicetree/bindings/arm/rockchip.txt
<mmind00> tomeu: when inverting the mmc stuff, I think the "mmc-hs200-1_8v;" can also just stay, as it only declares a supported mode
<tomeu> ack
nsaenz has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
<somy> hi, any mpp "experts"? I'd like to know what need to be resetted between two decode "sessions" like a jump in a movie or a restart of the movie?
vicencb has joined #linux-rockchip
ldevulder has quit [Quit: Leaving]
ldevulder has joined #linux-rockchip
vicencb has quit [Quit: Leaving.]
mrueg has quit [Quit: - Chat comfortably. Anywhere.]
mrueg has joined #linux-rockchip
ldevulder has quit [Ping timeout: 244 seconds]
ldevulder has joined #linux-rockchip
lkcl has quit [Ping timeout: 252 seconds]
lkcl has joined #linux-rockchip
adjtm_ has quit [Remote host closed the connection]
BenG83 has joined #linux-rockchip
aalm has quit [Ping timeout: 244 seconds]
afaerber has joined #linux-rockchip
vicencb has joined #linux-rockchip
<tomeu> any ideas about this one?
<tomeu> [ 2.694961] dwc3 fe800000.dwc3: Failed to get clk 'ref': -2
<tomeu> [ 2.695736] dwc3 fe800000.dwc3: failed to initialize core
<Esmil> tomeu: when i looked at it, i concluded that the "failed to get clk 'ref'" is because the dwc3 core uses clk_bulk_get to request some of the same clocks as the rockchip wrapper already takes care of
<Esmil> harmless from a functional standpoint
<Esmil> ..and the 'failed to initialize core' is usually just -EPROBE so it will try again later
<tomeu> yep, just read it :
<tomeu> * Clocks are optional, but new DT platforms should support all
<tomeu> * clocks as required by the DT-binding.
<tomeu> still have fe800000.dwc3 in /sys/kernel/debug/devices_deferred though
<tomeu> so something else is going on
<Esmil> Yeah, sometimes it fails to initialize the phy, and then you don't have usb3
<Esmil> ..but that happens maybe 1/10 boots for me
<Esmil> (for me this is the same on both 4.19 and 4.20)
<tomeu> ok, have switched to see why cdn_dp fails to probe
<tomeu> the probe is deferred because extcon_get_edev_by_phandle returned EPROBE_DEFER
<tomeu> but I know that the extcon specified in the DT has probed successfully
<tomeu> so not sure what could be going on
JohnDoe_71Rus has joined #linux-rockchip
vicencb has quit [Quit: Leaving.]
aalm has joined #linux-rockchip
lerc_ has joined #linux-rockchip
lerc has quit [Ping timeout: 245 seconds]
adjtm has joined #linux-rockchip
aalm has quit [Read error: Connection reset by peer]
<mmind00> tomeu: the whole typec + dp stuff only really works on CrOS devices right now
<mmind00> tomeu: architectural difference: all non-cros devices use a fusb302 connected to one of the i2c hosts, which in turn should use the kernels typec framework to negotiate modes like gadget / dp
<mmind00> tomeu: on cros devices the ec hides all of that and simply emits an extcon with the negotiated states
<mmind00> tomeu: in the vendor kernel they hacked that extcon into the fusb302 driver
<mmind00> tomeu: everything should be converted to use the type-c framework of the kernel, but while I talked to Guenter Roeck about converting cros-ed-extcon + pd to somehow integrate into the typec framework ... this is probably quite a while away
<mmind00> tomeu: thanks to a patch from eballetbo we at least default now host-only usb3 on non-cros devices
<mmind00> tomeu: just checked the nanopi4 dtsi ... and as expected ... the fusb302 cannot provide that extcon, simply because that is a vendor-specific hack
Moiman has quit [Remote host closed the connection]
Kwiboo has quit [Quit: .]
Kwiboo has joined #linux-rockchip
anarsoul|2 has joined #linux-rockchip
nsaenz has quit [Remote host closed the connection]
matthias_bgg has quit [Ping timeout: 260 seconds]
afaerber has quit [Quit: Leaving]
aalm has joined #linux-rockchip
akaizen has joined #linux-rockchip
paulk-leonov has quit [Quit: Leaving]
paulk-leonov has joined #linux-rockchip
paulk-leonov has quit [Max SendQ exceeded]
JohnDoe_71Rus has quit [Quit: KVIrc 5.0.0 Aria]
paulk-leonov has joined #linux-rockchip
Subs has joined #linux-rockchip
indy has quit [Read error: Connection reset by peer]
indy has joined #linux-rockchip
Subs has quit [Quit: Leaving]