ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion
hipboi has quit [Ping timeout: 276 seconds]
hipboi has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
hipboi has quit [Ping timeout: 255 seconds]
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 256 seconds]
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 255 seconds]
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 276 seconds]
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 256 seconds]
hipboi has joined #linux-rockchip
archetyp has quit [Remote host closed the connection]
hipboi has quit [Ping timeout: 255 seconds]
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 256 seconds]
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 272 seconds]
<macromorgan>
anyone on here have any familiarity with a fuel gauge for a battery?
<macromorgan>
trying to determine the minimum I need to present to Linux (like POWER_SUPPLY_PROP_CHARGE_NOW, etc)
hipboi has joined #linux-rockchip
lurchi__ has quit [Quit: Konversation terminated!]
lurchi__ has joined #linux-rockchip
hipboi has quit [Ping timeout: 255 seconds]
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 276 seconds]
lurchi_ has joined #linux-rockchip
lurchi__ has quit [Ping timeout: 255 seconds]
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 256 seconds]
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 272 seconds]
hipboi has joined #linux-rockchip
hipboi has quit [Remote host closed the connection]
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 276 seconds]
hipboi has joined #linux-rockchip
vagrantc has quit [Quit: leaving]
warpme_ has joined #linux-rockchip
hipboi has quit [Remote host closed the connection]
hipboi has joined #linux-rockchip
hipboi has quit [Remote host closed the connection]
hipboi has joined #linux-rockchip
levd has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
matthias_bgg has quit [Ping timeout: 256 seconds]
matthias_bgg has joined #linux-rockchip
stikonas has joined #linux-rockchip
<mriesch>
mmind00: ping
<mmind00>
mriesch: pong ;-)
<mriesch>
mmind00: hey, thanks for your prompt response. some discussions tend to revive every five years or so
<mmind00>
mriesch: hehe yeah ... when reading your mail I simply did remember that discussion and thought it wise to point to it as a starting point, so that we might continue the way without walking the beginnings again ;-)
<mriesch>
after debugging the hdmi tx driver for a day and then realizing that the power supplies were not enabled i thought that there could be a better way without this trapdoor :-)
<mriesch>
i believe there is already a phy property, presumably to point to an external phy.
<mriesch>
then it would be logical to define an internal phy that consumes those two supplies.
archetyp has joined #linux-rockchip
<mmind00>
mriesch: my memory stopped at "dw-hdmi + supplies ... there was a discussion years back" ;-)
<mriesch>
mmind00: i have no memory of this beaver?
<mmind00>
mriesch: exactly :-D
warpme_ has quit [Quit: Connection closed for inactivity]
<mriesch>
mmind00: :-) well some time *has* passed. but there does not seem to be any rk3288 specific solution, so i take it that you simply always turned on the power supplies?
<mmind00>
mriesch: correct ... and I guess all further Rockchip boards simply did the same
<mmind00>
mriesch: i.e. the basic stuff to do is actually to find out if this is a phy supply or a supply for the dw-hdmi block first ... without us having first-hand documentation
<mriesch>
mmind00: yes, at least for the rk3568 evb1 this holds. i'll check the trm once again, but i doubt there is any mention of those supplies
<mmind00>
mriesch: at least the rk3328 TRM is a bit more talkative ... hdmi_avdd_1v0 and _1v8 -> hdmi phy analog power
hipboi has quit [Remote host closed the connection]
<mmind00>
mriesch: which showed me that I should look into adding support for that into the inno-hdmiphy driver ;-)
hipboi has joined #linux-rockchip
<mriesch>
mmind00: is the inno-hdmi used in (or together with?) the rk3328?
<mmind00>
mriesch: correct
<mmind00>
rk3328 and rk3228 use the innosilicon hdmiphy
hipboi has quit [Ping timeout: 255 seconds]
levd has quit [Ping timeout: 246 seconds]
<macc24>
mmind00: rk3228?
<mmind00>
macc24: some arm32 thingy (rk3228/rk3229)
<mmind00>
somewhat dated already as well ;-)
<macc24>
huh
<macc24>
never heard of it
<mriesch>
mmind00: the rk3568 doesn't seem to mention the supplies, but in the datasheet they are defined as "HDMI PHY analog power", similar to what you found (here, the voltages are 0V9 and 1V8, though)
<mmind00>
mriesch: probably a property of the internal phy ... i.e. the rk3399 also specifies 0.9 and 1.8V for its internal phy
mps has quit [Ping timeout: 258 seconds]
mps has joined #linux-rockchip
hipboi has joined #linux-rockchip
hipboi has quit [Remote host closed the connection]
hipboi has joined #linux-rockchip
hipboi has quit [Remote host closed the connection]
hipboi has joined #linux-rockchip
warpme_ has joined #linux-rockchip
<mriesch>
mmind00: since the trm of the rk3568 contains a picture with the label "RK3399", the two models seem to resemble each other.
<mmind00>
mriesch: probably :-D
<mmind00>
mriesch: I think only the rk3228/rk3328 use the (probably cheaper) Innosilicon phy
<mriesch>
mmind00: i'll wait a bit for Benjamin's response and reply on the list. let's see if we can find a nice solution here.
<mriesch>
mmind00: the other annoying issue i have encountered recently is that the gpu in the rk3568 won't probe. it seems that the first access to the gpu registers causes an exception. any pointers what the reason could be?
<mmind00>
supply regulator? power-domain?
<mriesch>
this time i checked the power supply, gpu voltage is turned on
<mmind00>
clocks
<mmind00>
mriesch: though I think I remember ezequiel already having it probing before
<mmind00>
on a rk3566
<mriesch>
mmind00: yes, it should be feasible, i am pretty sure it is just some dumb mistake of mine. so power, clocks, possibly interrupts -- the usual suspects.
<mriesch>
hm.. are rk3568 power domains in 5.14-rc1 already?
mps has quit [Ping timeout: 255 seconds]
hipboi has quit [Remote host closed the connection]
hipboi has joined #linux-rockchip
mps has joined #linux-rockchip
hipboi has quit [Ping timeout: 272 seconds]
hipboi has joined #linux-rockchip
hipboi has quit [Remote host closed the connection]
hipboi has joined #linux-rockchip
archetyp has quit [Remote host closed the connection]
hipboi has quit [Remote host closed the connection]
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 255 seconds]
LinuxHackerman has quit [*.net *.split]
samueldr has quit [*.net *.split]
hipboi has joined #linux-rockchip
stormyknight3000 has joined #linux-rockchip
<stormyknight3000>
Hello, I have been trying to get my RockPro64 (using an rk3399 SoC) to output properly to a 1900x600 screen
<stormyknight3000>
the only resolution it seems capable of rendering at is 1080p
<stormyknight3000>
I have also tried hooking it up to a 1360x760 monitor and it still put out a 1080p signal
<robmur01>
yup, the HDMI driver is rather fussy about what it supports, primarily due to pixel clock restrictions in its phy configuration.
<robmur01>
if your mode requires a clock which doesn't happen to match a common TV resolution, you're probably out of luck
<stormyknight3000>
ah, well that is rather unfortunate :/
<robmur01>
there have been a few attempts to improve the situation, but nothing's ever been fully resolved
<stormyknight3000>
makes me wish I had some practical systems programming experience and an in-depth knowledge of the hardware :/
<robmur01>
e.g. I've tried hacking in a 154MHz setting for my 1920x1200 monitor which works fine on my RK3399, but then turns out to be glitchy and unstable as heck on my RK3288 :(
<robmur01>
I recall ChromeOS downstream doing some pretty gnarly things with the clocks to try to support more stable rates on RK3288
hipboi has quit [Ping timeout: 272 seconds]
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 265 seconds]
matthias_bgg has quit [Ping timeout: 272 seconds]
matthias_bgg has joined #linux-rockchip
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 256 seconds]
hipboi has joined #linux-rockchip
stormyknight3000 has quit [Quit: Leaving]
archetyp has joined #linux-rockchip
matthias_bgg has quit [Quit: Leaving]
hipboi has quit [Ping timeout: 245 seconds]
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 256 seconds]
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 276 seconds]
tlwoerner has quit [Ping timeout: 252 seconds]
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 255 seconds]
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 245 seconds]
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 276 seconds]
hipboi has joined #linux-rockchip
warpme_ has quit [Quit: Connection closed for inactivity]
hipboi has quit [Ping timeout: 256 seconds]
MatrixTravelerbo has quit [Read error: Connection reset by peer]
psydroid has quit [Read error: Connection reset by peer]
akanouras has quit [Remote host closed the connection]
amstan has quit [Remote host closed the connection]
ServerStatsDisco has quit [Read error: Connection reset by peer]
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 272 seconds]
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 246 seconds]
tlwoerner has joined #linux-rockchip
hipboi has joined #linux-rockchip
psydroid has joined #linux-rockchip
amstan has joined #linux-rockchip
akanouras has joined #linux-rockchip
samueldr has joined #linux-rockchip
MatrixTravelerbo has joined #linux-rockchip
LinuxHackerman has joined #linux-rockchip
ServerStatsDisco has joined #linux-rockchip
hipboi has quit [Ping timeout: 268 seconds]
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 252 seconds]
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 255 seconds]
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 252 seconds]
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 272 seconds]
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 255 seconds]
archetyp has quit [Remote host closed the connection]