-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add new board armsom-cm5-io #7211
Conversation
@amazingfate The jpeg encoder does not seem to be initialized, although it has been enabled in the device tree.
|
Dirver of jpege is not enabled. I will build kernel with it enabled and test. |
Enable |
I will check it on my board, by default on my dts should be enabled |
@amazingfate can be useful? root@youyeetoo-r1-v3:~# sudo dmesg | grep -E "jpeg|JPEG|jpg|JPG"
[ 9.611996] mpp_vepu2 jpege-ccu: probing start
[ 9.612004] mpp_vepu2 jpege-ccu: probing finish
[ 10.070067] mpp_vepu2 fdba0000.jpege-core: Adding to iommu group 4
[ 10.070192] mpp_vepu2 fdba0000.jpege-core: probing start
[ 10.070337] mpp_vepu2 fdba0000.jpege-core: attach ccu success
[ 10.070364] mpp_vepu2 fdba0000.jpege-core: probing finish
[ 10.070485] mpp_vepu2 fdba4000.jpege-core: Adding to iommu group 5
[ 10.070545] mpp_vepu2 fdba4000.jpege-core: probing start
[ 10.070655] mpp_vepu2 fdba4000.jpege-core: attach ccu success
[ 10.070675] mpp_vepu2 fdba4000.jpege-core: probing finish
[ 10.070781] mpp_vepu2 fdba8000.jpege-core: Adding to iommu group 6
[ 10.070841] mpp_vepu2 fdba8000.jpege-core: probing start
[ 10.070945] mpp_vepu2 fdba8000.jpege-core: attach ccu success
[ 10.070967] mpp_vepu2 fdba8000.jpege-core: probing finish
[ 10.071082] mpp_vepu2 fdbac000.jpege-core: Adding to iommu group 7
[ 10.071144] mpp_vepu2 fdbac000.jpege-core: probing start
[ 10.071247] mpp_vepu2 fdbac000.jpege-core: attach ccu success
[ 10.071267] mpp_vepu2 fdbac000.jpege-core: probing finish
[ 10.071683] mpp_jpgdec fdb90000.jpegd: Adding to iommu group 3
[ 10.071848] mpp_jpgdec fdb90000.jpegd: probe device
[ 10.071980] mpp_jpgdec fdb90000.jpegd: probing finish
My actual configuration: root@youyeetoo-r1-v3:~# zcat /proc/config.gz | grep -i ROCKCHIP_MPP_*
CONFIG_ROCKCHIP_MPP_SERVICE=y
CONFIG_ROCKCHIP_MPP_PROC_FS=y
CONFIG_ROCKCHIP_MPP_RKVDEC=y
CONFIG_ROCKCHIP_MPP_RKVDEC2=y
CONFIG_ROCKCHIP_MPP_RKVENC=y
CONFIG_ROCKCHIP_MPP_RKVENC2=y
CONFIG_ROCKCHIP_MPP_VDPU1=y
CONFIG_ROCKCHIP_MPP_VEPU1=y
CONFIG_ROCKCHIP_MPP_VDPU2=y
CONFIG_ROCKCHIP_MPP_VEPU2=y
CONFIG_ROCKCHIP_MPP_IEP2=y
CONFIG_ROCKCHIP_MPP_JPGDEC=y
# CONFIG_ROCKCHIP_MPP_JPGENC is not set
CONFIG_ROCKCHIP_MPP_AV1DEC=y
# CONFIG_ROCKCHIP_MPP_VDPP is not set |
@SuperKali jpege is only found on rk3576 now and vdd is only found on rk3528. Rk3588 should have all vpu nodes working with current vendor kernel config. |
Thanks, that solved the problem. |
Oh, i gotcha |
Description
ArmSoM CM5 is a rk3576 SoM compitable with raspberrypi CM4 carrier board. And CM5 IO is the official carrier board from ArmSoM.
More info:
https://docs.armsom.org/armsom-cm5
https://docs.armsom.org/armsom-cm5-io
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration.
./compile.sh BOARD=armsom-cm5-io BRANCH=vendor BUILD_MINIMAL=no DEB_COMPRESS=xz KERNEL_CONFIGURE=no RELEASE=noble KERNEL_GIT=shallow BUILD_DESKTOP=yes DESKTOP_APPGROUPS_SELECTED= DESKTOP_ENVIRONMENT=gnome DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base
Checklist:
Please delete options that are not relevant.