Closed zys1310992814 closed 5 years ago
What DTB is used ? The core of 4.19 out of date and no longer used.
when I use Armbian_5.73_Aml-s905_Debian_stretch_default_4.20.2_20190130.img.xz the kernel is ok,but hdmi no audio output,so I use 4.19.
What DTB is used to 4.20 ?
now I pull your latest code and make zImage. I wish the hdmi works ok. I down load a armbian img file that hdmi ok I use mount the img,and use dtb and kernel config file form it
I think the kernel panic is belong to the kernel. I replace the kernel which makes panic with the one the hdmi is ok,and the kernel is ok,and the DTB is still the old one.so I think DTB is ok,The reson is the kernel.
[ 22.879434] ------------[ cut here ]------------ [ 22.879443] Unknown pixelformat 0x31324d41 [ 22.879504] WARNING: CPU: 0 PID: 2935 at drivers/media/v4l2-core/v4l2-ioctl.c:1340 v4l_enum_fmt+0x1558/0x1850 [ 22.879507] Modules linked in: fuse bnep btsdio bluetooth ecdh_generic brcmfmac brcmutil cfg80211 rfkill asix usbnet meson_ir ao_cec rc_core meson_gxbb_wdt pwm_meson meson_rng rng_core adc_keys input_polldev ip_tables x_tables ipv6 realtek [ 22.879556] CPU: 0 PID: 2935 Comm: gst-plugin-scan Not tainted 4.19.0-rc7-aml-s9xxx #7 the panic is happend when the desktop is running,when I was not install the desktop,everything is ok
HDIM audio is still not work in 4.20.
I think the problum is the DTB. the kernel is ok,no panic about v4l2.
I repeat the question. What DTB do you use in the 4.20 kernel (with which sound does not work) ? I don't need information about the 4.19 kernel and its panic.
Send me your dtb file, I will add the necessary fixes for the sound.
how did I send it to you? I want to say thanks a lot. email address?
send pull request my branch
Then take the DTB file from VIM1, just process it DTC and compare them. There will be a section about the sound, where you need to fix a few lines.
yes,I got the sound code.But I think it is hard for me ,I am working on it now.
sound { compatible = "simple-audio-card"; simple-audio-card,name = "meson-gx-audio"; assigned-clocks = < 0x0b 0x0f 0x0b 0x0d 0x0b 0x0e >; assigned-clock-parents = < 0x00 0x00 0x00 >; assigned-clock-rates = < 0x11940000 0x10266000 0x17700000 >;
simple-audio-card,dai-link@0 {
format = "i2s";
mclk-fs = < 0x100 >;
bitclock-master = < 0x3b >;
frame-master = < 0x3b >;
plat {
sound-dai = < 0x3c >;
};
cpu {
sound-dai = < 0x3b >;
};
codec {
sound-dai = < 0x16 >;
};
};
};
ok,I just burn Armbian_5.67_Aml-s9xxx_Debian_stretch_default_4.19.7_20181228.img,and I use the right dtb,and there is no kernel panic about v4l2,and hdmi audio and BT works fine. by the way,thanks a lot.
These days ,I just use meson-gxl-s905d-p231.dtb and kernel 4.20 on my board,and The HDMI and video is ok,so I think my board is base on p231 board,The only trouble is bluetooh,It is not wok ,can you just add bluetooth(bcm43438-bt) support for phicomm-n1 base on meson-gxl-s905d-p231.dtb?
All device is ok now! Thanks
hi,I got in trouble when the S905D run armbian.The kernel log is below. [ 22.356805] fuse init (API version 7.27) [ 22.879434] ------------[ cut here ]------------ [ 22.879443] Unknown pixelformat 0x31324d41 [ 22.879504] WARNING: CPU: 0 PID: 2935 at drivers/media/v4l2-core/v4l2-ioctl.c:1340 v4l_enum_fmt+0x1558/0x1850 [ 22.879507] Modules linked in: fuse bnep btsdio bluetooth ecdh_generic brcmfmac brcmutil cfg80211 rfkill asix usbnet meson_ir ao_cec rc_core meson_gxbb_wdt pwm_meson meson_rng rng_core adc_keys input_polldev ip_tables x_tables ipv6 realtek [ 22.879556] CPU: 0 PID: 2935 Comm: gst-plugin-scan Not tainted 4.19.0-rc7-aml-s9xxx #7 [ 22.879558] Hardware name: Phicomm N1 (DT) [ 22.879562] pstate: 40000005 (nZcv daif -PAN -UAO) [ 22.879566] pc : v4l_enum_fmt+0x1558/0x1850 [ 22.879569] lr : v4l_enum_fmt+0x1558/0x1850 [ 22.879571] sp : ffff00000de93b80 [ 22.879573] x29: ffff00000de93b80 x28: 00000000c0405602 [ 22.879578] x27: ffff000009da9b68 x26: ffff800025e6d008 [ 22.879582] x25: 0000000000000000 x24: ffff8000103ea100 [ 22.879587] x23: ffff800025e6d008 x22: ffff000009da9b68 [ 22.879591] x21: ffff800025e4c600 x20: ffff00000de93cf8 [ 22.879596] x19: 0000000000000000 x18: ffffffffffffffff [ 22.879600] x17: 0000000000000000 x16: 0000000000000000 [ 22.879605] x15: ffff00000a17a000 x14: 00000000fffffff0 [ 22.879610] x13: ffff00000a24e6e0 x12: ffff00000a17a000 [ 22.879614] x11: 0000000000000000 x10: ffff00000a24d000 [ 22.879619] x9 : 0000000000000000 x8 : 0000000000000003 [ 22.879623] x7 : 0000000000000000 x6 : 0000000000000173 [ 22.879627] x5 : 0000000000000000 x4 : 0000000000000001 [ 22.879631] x3 : 0000000000000007 x2 : 0000000000000007 [ 22.879636] x1 : a37cf81da9540f00 x0 : 0000000000000000 [ 22.879641] Call trace: [ 22.879645] v4l_enum_fmt+0x1558/0x1850 [ 22.879648] video_do_ioctl+0x358/0x4b0 [ 22.879652] video_usercopy+0x284/0x4e8 [ 22.879655] video_ioctl2+0x14/0x20 [ 22.879659] v4l2_ioctl+0x38/0x58 [ 22.879665] do_vfs_ioctl+0xb8/0x8e0 [ 22.879669] ksys_ioctl+0x80/0xb8 [ 22.879673] arm64_sys_ioctl+0x1c/0x28 [ 22.879679] el0_svc_common+0x60/0xe8 [ 22.879682] el0_svc_handler+0x24/0x80 [ 22.879686] el0_svc+0x8/0xc [ 22.879689] ---[ end trace 00d2ceae7bd14dde ]--- [ 23.713892] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready