Posts by jernej

  • Sleep/wake function based on HDMI signal input

    Quote from pope3909

    If so, I propose that LibreELEC constantly monitors display status and forces Kodi to go into "low power mode" when it detects that the display has been off for XX minutes (perhaps 5 minutes). Also I propose that LibreELEC forces Kodi to wake from "hibernation mode" and/or "low power mode" instantly when it detects that the display has been turned back on.

    This is already implemented via HDMI CEC. If I turn TV off, Kodi detects this via CEC and sends suspend signal to system immediately (no delay). Wakeup is much more complex, since it depends on SoC and its drivers. Whole procedure once worked on Allwinner SoCs (except R40), but wakeup via CEC is currently broken for some reason...

    In other words, sleep part is already implemented, but you don't want it if wakeup part isn't implemented and here is the issue - only some platforms implements that.

    Pi4 AFAIK doesn't have power management implemented in kernel.

  • OrangePi 3 LTS: Ethernet Connection Timed Out

    To revive this topic a bit and maybe give some hope. Recently, there was a patch submitted to linux-sunxi ML to fix ethernet on another board, but with Motorcomm Ethernet PHY with adding some extra properties. I have no idea why it would work, but it doesn't hurt to try at this point. gadget_guy would you be willing to test? What do you prefer? Patch? Image? Update file? LE11 or LE12 nightly?

  • [Orange Pi 3 LTS] Freezes

    Recently we spoke about many issues in clock driver. Guess what, I found one. HDMI clock isn't set correctly. That's why I have troubles with some displays, in this case LG TV. It seems that monitors are more forgiving, but fps would suffer.

  • [Orange Pi 3 LTS] Freezes

    Quote from frakkin64

    I have been running for just about 3 days with schedutil governor, no freezing, no problems at all.

    Glad to hear it. I have wondered if you forget to report :D But I assumed silence is good in this case.

    Quote from frakkin64

    It looks to me you found the cause of the freezing with this patch.

    Great, I'll submit it as a fix, not only to LE, but in mainline Linux in general. If you don't mind, I would submit it with your "Reported-by:" and "Tested-by:" tags (you can give them to me via PM, but in the end, they will be publicly visible in commit message).

    Quote from frakkin64

    Thank you so much for helping solve this.

    I think thanks goes to you, with your insane amount of testing. I just chimed in with ideas.

    P.S. I make a few more improvements in nightly LE12 images. Network related patch is reverted and there is also a bugfix for ocassional DRAM init issue and possible HEVC decoding issue. On top of that, there is full 10-bit display pipeline support and GPU DVFS.

    If only we can figure OPi 3 LTS network issue now :)

  • [Orange Pi 3 LTS] Freezes

    Quote from frakkin64

    Speaking of the GPU, I noticed that the OPP tables (sun50i-h6-gpu-opp.dtsi) are not included for any device other than Beelink GS1.

    Yeah, GS1 was first, but then nobody actually updated and tested other boards.

    Quote from frakkin64

    I also assume the Tanix TX6 does dynamic frequency scaling (just with a fixed voltage?).

    Correct (for CPU). GPU scaling should just work, if table is included.

    Quote from frakkin64

    I started looking at the clock code, and like everything it is a lot of indirection, macros, etc that takes years to fully understand -- and even then, there are things probably still not understood.

    My research of bugs often lead me to clocks. So yeah, it's complex mechanism and, at least in the past, source of many issues.

    Quote from frakkin64

    I guess I am thinking that's why this isn't the root cause, the other factor is the scaling up/down of the frequency probably has an inherent delay and I would expect for the CPU clock to be adjusted the CPU is actually halted and the CCU has an inherent delay to wait for the clock to lock before releasing the CPU halt and perhaps that timing is greater than the regulator stabilization time (which worst case is 44us).

    That's entirely possible.

    I found something. H6 user manual has description how to properly adjust CPUX PLL. I'm sure that at least delay at the end is missing. However, I also noticed that many other SoCs, like A64 and H3, reparent CPU clock to something stable, like 24 MHz, switch CPUX PLL and then reparent back. I suppose that this is also valid option, at least until we can figure out more direct process.

  • [Orange Pi 3 LTS] Freezes

    This is a very good research and find. I always thought ramp delay is in us and it has never occurred to me to be coefficient. Anyway, if this is the culprit, I would ask you to send patch to Linux mailing lists to update all H6 boards with AXP805. It would also explain why my primary H6 development board - Tanix TX6 - doesn't show this kind of issues. It use fixed voltage regulator instead of AXP805.

  • Nightly images for A64, H3, H5, H6 and R40 boards

    Dear all,

    finally I wrote experimental support for 10-bit HDMI output on Allwinner H6, so HDR videos should render without any processing, directly to TV. Note, due to missing HW decoding driver features, only VP9 is rendered in 10-bit, while HEVC is still rendered in 8-bit. However, due to proper settings in HDMI output, it should be better colourwise anyway.

    Please test.

    Source: https://github.com/jernejsk/LibreELEC.tv/commits/h6-10bit

    Update file: http://jernej.libreelec.tv/test/h6-10bit/

  • [Orange Pi 3 LTS] Freezes

    Quote from frakkin64

    My understanding with DVFS is you have to switch the voltage first, then bump the clock.

    For raising frequency yes. For lowering it, it's the other way around.

    Quote from frakkin64

    I guess I am wondering if you don't wait for the voltage ramp-up and you have adjusted the clock before the voltage is stablized would that cause SoC to crash (i.e. not enough voltage/current to support the higher clock rate).

    You can easily adjust ramp up time in DT with regulator-ramp-delay. For testing purposes, you can set it to some ridiculous high number, like 100 ms.

  • [Orange Pi 3 LTS] Freezes

    Can you test some other frequency? IIRC it's possible to select opp through sysfs. If it doesn't matter which frequency is selected, as long as it's not switched, then the bug is in frequency switching code.

    I have to give you big thank you for your patience in debugging this issue.

  • [Orange Pi 3 LTS] Freezes

    Quote from frakkin64

    So it's either a combination of scheduler + iommu disabling, or it didn't run long enough, or it is frequency switching.

    Frequency switching can be a bit tricky, true.

    Quote from frakkin64

    Can you trigger the config target via scripts/build, or do you usually do that outside of the LE build system?

    Easiest way is to execute make ARCH=arm64 menuconfig in LE linux build folder and change whatever you want. Then you diff changes between .config in build folder and linux.aarch64.conf and pick changes that are of interest. Don't take all changes, there are some magic values, which are replaced by build script.