rebase commits from rk-6.1-rk1 to rk-6.1-rkr3 #200
Conversation
Signed-off-by: Stephen Chen <stephen@radxa.com>
Signed-off-by: Stephen Chen <stephen@radxa.com>
Signed-off-by: Stephen Chen <stephen@radxa.com>
Signed-off-by: Zhang Rui <rui.crater@gmail.com>
arm64: dts: Add device trees for NanoPi R6S and R6C arm64: dts: Add device trees for NanoPi R6S and R6C arm64: dts: Add device trees for NanoPi R6S and R6C
- rework: - rk3588-rk806-single-khadas.dtsi instead of hacking common dtsi - arm64: dts: rk3588s-khadas-edge2: remove chosen node - drop useless nvr-demo / chosen-thingy dtsi - squashed, scripts/packaging/etc removed, grouped by directory - source - https://github.com/khadas/linux/commits/khadas-edges-5.10.y - khadas/linux@85a8b25
|
|
Like 4:2:0 10-bit, rotate_mode needs to be assigned to (1 << 6) when scaling is not going to be used in rga2. Or the output image is corrupted. Signed-off-by: nyanmisaka <nst799610810@gmail.com>
Good to hear, so we can just drop this commit.
Rockchip just released new sdk with kernel tag rkr3 to their customers several days ago. Jeffy doesn't have much permission to upload such new kernel version. |
|
Whoops, I accidentally marked it as ready for review, ignore that lol. |
|
Hey @amazingfate, I found a bug where max user processes and pending signals where very low on the 6.1 rkr3 kernel, causing some users to experience a number of issues preventing new processes to be started when there is ample resources available on the system. I did some bisecting and was able to hunt down the problematic commits; 286ef81 and 8ca3ffc, I recommend they be reverted. I'm very curious about commit 286ef81 as to why it caused the problem, but this is something I will research another day. Additional Info: Joshua-Riek/ubuntu-rockchip#919 |
|
@Joshua-Riek Do you have |
|
I had |
…otup" This reverts commit d376ca6. It's reported that when using Radxa CM5 with RPI CM4 IO board, USB2.0 host ports don't work. By default RK3588 USB DRD DWC3_0 (usb@fc000000) is set in otg mode. In hardware, RK3588 TYPEC0_USB20_OTG_ID is pulled down to groud by a 2.2k resistor. It is needed to perform GCTL_CORE_SOFTRESET during bootup. Signed-off-by: Stephen Chen <stephen@radxa.com> (cherry picked from commit ec8a9ad) Signed-off-by: Joshua Riek <jjriek@verizon.net>
- straight from https://github.com/friendlyarm/kernel-rockchip/tree/nanopi6-v6.1.y - at sha1 34cd890017997ea3be9524977b278ed4c21298b9
…oard devicetree hdptxphy_hdmi_clk0/1 sub node is removed by commit fa7c72a: arm64: dts: rockchip: rk3588: remove unused sub node hdptxphy_hdmi_clk0/1. So remove them from all the board dts.
amazingfate
force-pushed
the
rk-6.1-rkr3_wip
branch
from
c9f9b79
to
ecda768
Compare
|
Tested with rk3568 board hinlink-h66k and rk3528 board hinlink-ht2 and rk3588 board rock-5b, working fine. |
|
Tested on Mekotronics R58X ( For reference, complete ANSI dmesg across kernels on this board.
|
|
Also tested on Meko R58X-Pro with Panthor and KDE-Neon. Works fine. |
|
Tested on the Mixtile-Blade3, including SATA (via overlay), 4-pin fan, nvme, 2x 2.5gbit eth. dmesg:
With rkr3, seems like there's some dmesg errors ref regulators and I've quickly tested Jellyfin (10.9.7) and it transcodes |
|
Tested on NanoPC T6-LTS, after cherry-picking and adapting #207.
nvme, usb2 / usb3 / type-c udc, hdmi, etc, all work. |
Dropped commits:
need to check if this patch is still necessarythis WARN_ON is removed in rkr3,need to check if this patch is still necessary. Rkr3 adds a new condition!rockchip_rfbc(plane, modifier)to this ERROR log, and I haven't see it after boot. The error log will print plane name, so I think it should be okay to keep this.I just made these patches applied,
have not built this kenel yetkernel boots fine.