narmstrong changed the topic of #linux-amlogic to: Amlogic mainline kernel development discussion - our wiki http://linux-meson.com/ - ml linux-amlogic@lists.infradead.org - official channel moved from Freenode - publicly logged on https://libera.irclog.whitequark.org/linux-amlogic
naoki has quit [Read error: Connection reset by peer]
naoki has joined #linux-amlogic
GNUtoo has quit [Ping timeout: 258 seconds]
GNUtoo has joined #linux-amlogic
Tartarus has quit [Ping timeout: 250 seconds]
Tartarus has joined #linux-amlogic
vagrantc has quit [Quit: leaving]
<steev> on the other system with conservative governor set, no pll either
vagrantc has joined #linux-amlogic
buzzmarshall has quit [Quit: Konversation terminated!]
vagrantc has quit [Quit: leaving]
GNUtoo has quit [Ping timeout: 258 seconds]
GNUtoo has joined #linux-amlogic
<narmstrong> steev: which kernel are you running ? The upstream clk-pll code is different from your patch
Ballerburg9005 has joined #linux-amlogic
tolszak has joined #linux-amlogic
<tolszak> narmstrong: Hi there, I updated poky and meta-multimedia to lastest kirkstone and amlogic-image-sato doesn't boot. What's the latest kirkstone commit on poky that meta-meson was tested against?
<narmstrong> tolszak: what’s the kernel version ?
<tolszak> narmstrong: 5.15.62
<narmstrong> tolszak: this version is broken, the 7cd70656d128 commit must be backported
Ballerburg9005 has quit [Ping timeout: 246 seconds]
<tolszak> narmstrong: THank you very much! Can it also cause issue with DRM?
<narmstrong> it does cause an issue with drm, the rest of the system should boot fine
<tolszak> narmstrong: My custom build based on the same kernel boots but gui app fails with -554 erroor from drmModeSetCrtc
<tolszak> narmstrong: Many many thanks, it saved me hours of work looking bisecting search the issue.
<narmstrong> I'll push a fix in meta-meson
ldevulder has quit [Remote host closed the connection]
ldevulder has joined #linux-amlogic
Ballerburg9005 has joined #linux-amlogic
<narmstrong> Pushed
<gab> tolszak: I had the same issue (no hdmi output) and cherry-picking commit 7cd70656d128 worked for me
<narmstrong> I'm trying to make use of the SRC_URI minrev/maxrev, hope it will work !
<tolszak> narmstrong: Thank you
BlueMatt[m] has quit [Quit: Bridge terminating on SIGTERM]
psydroid has quit [Quit: Bridge terminating on SIGTERM]
Tartarus has quit [Quit: Bridge terminating on SIGTERM]
Tartarus has joined #linux-amlogic
psydroid has joined #linux-amlogic
BlueMatt[m] has joined #linux-amlogic
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #linux-amlogic
gab has quit [Quit: WeeChat 3.0.1]
zkrx has quit []
zkrx has joined #linux-amlogic
tolszak has quit [Read error: Connection reset by peer]
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #linux-amlogic
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #linux-amlogic
<steev> narmstrong: i'm on 5.10.145 (stable 5.10 with patching)
<narmstrong> Ok still I don’t see where you got your pll lock wait, except from vendor kernel…
tolszak has joined #linux-amlogic
buzzmarshall has joined #linux-amlogic
<steev> narmstrong: ah, you're right, it's a patch i pulled in from Heiner Kallweit from the linux amlogic patchwork "clk: meson: pll: adjust timeout in meson_clk_pll_wait_lock()"
<steev> fwiw, i've been running it since yesterday at 5pm (it's currently 10:30am here) with sway running, a video playing on loop in mpv and a web browser going, with ondemand governor, and no pll lock messages
<tolszak> narmstrong: UNfortunately your patch doesn't work for me. I needed to remove minrev and maxrev. There is a note "Patch 0001-drm-bridge-display-connector-implement-bus-fmts-call.patch applies to later revisions" instead and as I understand the patch is not applied. I checked and minrev refers to SRCREV. checking env of linux-yocto shows that SRCREV=INVALID. Perhaps that's why
<tolszak> narmstrong: But without it works alright which is great :) thanks
tolszak has quit [Ping timeout: 268 seconds]
zkrx has quit []
zkrx has joined #linux-amlogic
vagrantc has joined #linux-amlogic
<Cheaterman> Hmm, I'm working on a less demanding app and I didn't get PLL warnings
<Cheaterman> The only ones I got were about audio source IIRC, the initial HDMI one
<Cheaterman> But a single one of these
<Cheaterman> I'll keep you guys in touch once I get back to testing the demanding app
<Cheaterman> I pre-emptively set default gov to performance on my OS image for new deployments
<Cheaterman> In the meantime, I'll look for it, but do you guys happen to know off-hand if there's a way to set default governor in kernel cmdline or something to that effect
<Cheaterman> (for existing deployments, that sounds like one of the easiest way to make it happen for me)
<Cheaterman> (as opposed to pushing a new kernel and set of modules, although I could also do that)
<steev> cpufreq.default_governor=
zkrx has quit []
zkrx has joined #linux-amlogic
zkrx has quit []
zkrx has joined #linux-amlogic
tolszak has joined #linux-amlogic
tolszak has quit [Ping timeout: 250 seconds]
<Cheaterman> thanks a lot
ldevulder has quit [Quit: Leaving]
<steev> Cheaterman: where i am, it is very warm, and i don't want to put active cooling on my radxa zero, so I'd rather not set it to performance, otherwise mine idles between 55-65
Ballerburg9005 has quit [Ping timeout: 260 seconds]
<Cheaterman> I see, makes sense for home use ; I largely use N2+ for work so heat isn't a big concern