svarbanov has quit [Read error: Connection reset by peer]
jhovold has joined #linux-msm
svarbanov_ has quit [Ping timeout: 480 seconds]
svarbanov has joined #linux-msm
svarbanov has quit [Ping timeout: 480 seconds]
svarbanov has joined #linux-msm
sricharan has quit [Remote host closed the connection]
jhovold has quit [Quit: WeeChat 3.8]
<Degdag_Med[m]>
lumag: I've been trying to get my panel driver to work on sm8150 , it's a non-DSC cmd mode panel on xiaomi k20 pro . I used last longbios branch . panel seem to initialize fine but it doesn't display anything only showing the early dmesg on the screen than it hang there without any refresh .
<aka_[m]>
clk_core_reparent_orphans_nolock+0x88/0xc4 me not into stuff
<lumag>
Degdag_Med[m], just for my understanding, is ther a splash from the bootloader, or there is none?
<lumag>
also, at which point does -next kernel stop?
<Degdag_Med[m]>
lumag: I'm using mu-sm8150 uefi bootloader for booting . no splash screen .
<Degdag_Med[m]>
Let me take a video for you
<lumag>
I see.
<aka_[m]>
lumag: is there chance some power gets cut off so he can no longer access phy and it shows timedout on read?
<lumag>
So, I'd not bother with -rc1, Marijn[m]'s rework of TE handling is only in linux-next, landing for 6.5
<lumag>
Also let me sketch a patch which should at least attempt to fix the VCO
<aka_[m]>
lumag: i was wondering, what do you think about cosmetic changes in gcc drivers?
<aka_[m]>
i noticed some gcc drivers have clocks names like gpllX_early/aux/main yet enable mask does not align with these
<lumag>
aka_[m], which changes?
<aka_[m]>
on msm8953 there is gpll0_early which have BIT(0) enabled
<aka_[m]>
its MAIN output
<aka_[m]>
this layout appears to be common on these older alphas and non-alphas(8976/8916)
<aka_[m]>
i was trying to craft backport for msm-4.19 and got lost with names when tried to find same names in ds drivers and found there was not even single mention of _early
<aka_[m]>
also based on some looking in other socs _early output is not affected by POST_DIV
<aka_[m]>
sadly no docs so cannot be fully sure
<aka_[m]>
there is PRE_DIV_RATIO which i have no idea what is exactly changing
<Degdag_Med[m]>
Degdag_Med[m]: The framebuffer here is from the DRM driver not any kind of simple or efi frambuffer
<aka_[m]>
ok i see some diagram about starFive and on them pre-divider is placed inbetween source and transform block
<aka_[m]>
so pre-divider might be one to modify reference frequency
<lumag>
aka_[m], I'm not sure about backporting to msm-4.19
<lumag>
Anyway, I took a glance at 3.18 vs mainline.
<lumag>
Speaking in 3.18 terms: gpll0_main_div2_mm is 400 MHz, gpll0 is 800 MHz
<lumag>
gpll0_clk_src is also set at 800 MHz
<lumag>
Speaking about the mainline, it seems that gpll0_early rate is read from the hardare
<aka_[m]>
lumag: could be some divider in between block input
<lumag>
What is the rate of that clock?
<aka_[m]>
lumag: my limited understanding is that it could either be other output of gpll0(there are few) or there is static divider between these multimedia rcgs
<lumag>
If I understand correctly, from the mainline perspective, the gpll0_early_div is clocked at 400 MHz, while gpll0 is clocked at 800.
<aka_[m]>
On 8937 register config have hardcoded divider for one of gpu gplls
<aka_[m]>
And they model it as clk_fixed
<aka_[m]>
It would be weird to have early on lower clock
<aka_[m]>
Because early might be rate pre dividers
<aka_[m]>
Main is for sure affected by post div
<aka_[m]>
You can check cpu 8976 driver
<aka_[m]>
It has early at programmed pll rate and main on /2
<aka_[m]>
And config does write post_div value
<aka_[m]>
On 8953 mainline it would be gpll0 is 800 early_div is 400 and gpll0 is 800 but read-only
<aka_[m]>
And consumers only depends on read-only gpll0
<aka_[m]>
Still early there is wrong because it's main output
<lumag>
aka_[m], and gpll0_early is also 800?
<aka_[m]>
If it was used and enabled it could be
<aka_[m]>
If bit(3) of user register is not set then early output is disabled
<aka_[m]>
But if we have main output enabled at 800mhz then I doubt we can achieve 400 MHz on any other output
<aka_[m]>
Like aux/aux2
<aka_[m]>
If we had main and early enabled And post_div was set I would believe it can do 800 on early and 400 on main
<aka_[m]>
Sdw429 driver in 4.19 have names much cleaner
<aka_[m]>
lumag: user register appears to be quite high level control register And layout of it is very similar regardless of generation
<aka_[m]>
Config one is worse
<aka_[m]>
Well even if some calls early main And set bit in reality it doesn't matter
<aka_[m]>
Because these are only used to build final enable value inside clk framework
<lumag>
aka_[m], ok. If that helps. for 8909 there is a pre-divider of 2. On the other hand, 8909 driver doesn't pay attention to early vs main outputs to be used as a source.
<lumag>
Also, we mostly treat user register as read-only / static, there is no driver control over main / early / etc. being enabled or not
<aka_[m]>
In few hours I'm going to check sm6115 sheet