

Stephen Graf
Members-
Posts
147 -
Joined
-
Last visited
Other groups
Contributor/Maintainer
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
@going I have a few questions about the kernel sound configuration: why is the SUN50IW9_CODEC configured in two places? do we need CONFIG_SND_SUN8I_CODEC=y and CONFIG_SND_SUN8I_CODEC_ANALOG=y? # # Allwinner SoC Audio support # CONFIG_SND_SUN4I_CODEC=y CONFIG_SND_SUN50IW9_CODEC=m CONFIG_SND_SUN8I_CODEC=y CONFIG_SND_SUN8I_CODEC_ANALOG=y CONFIG_SND_SUN50I_CODEC_ANALOG=y CONFIG_SND_SUN4I_I2S=m CONFIG_SND_SUN4I_SPDIF=m CONFIG_SND_SUN50I_DMIC=m CONFIG_SND_SUN9I_HDMI_AUDIO=m CONFIG_SND_SUN8I_ADDA_PR_REGMAP=y # end of Allwinner SoC Audio support CONFIG_SND_SOC_SUNXI_MACH=m CONFIG_SND_SOC_SUNXI_AHUB_DAM=m CONFIG_SND_SOC_SUNXI_INTERNALCODEC=m CONFIG_SND_SOC_SUNXI_SUN50IW9_CODEC=m # # Allwinner SoC Audio support V2 # CONFIG_SND_SOC_SUNXI_AAUDIO=m CONFIG_SND_SOC_SUNXI_AHUB=m # end of Allwinner SoC Audio support V2
-
@going I am starting to compare the original sound patches from kernel 6.6 to the latest. I came accross a minor point that I suspect does not affect anything, but should be corrected. The patch file: arch/arm64/boot/dts/allwinner/sun50i-h616-orangepi-zero.dtsi has two entries for the audio codec. They are the same so I don't think it affects the final dtb. &codec { allwinner,audio-routing = "Line Out", "LINEOUT"; status = "okay"; }; &de { status = "okay"; }; &codec { allwinner,audio-routing = "Line Out", "LINEOUT"; status = "okay"; };
-
@going I have an image from when I tested the tcon patch a few weeks ago, v25.02 rolling for Orange Pi Zero3 running Armbian Linux 6.12.13-edge-sunxi64, and the analog audio works properly until I try to use the pulseaudio volume control at which point the audio speeds up. Restarting celluloid clears the problem. The Celluloid volume control works properly and does not cause a problem. Too confusing! Dmesg does not show an error about the codec clock. Can you tell what changed?
-
@going There might be a clue to the sound problem in the following: sysadmin@orangepizero3:~$ sudo dmesg | grep -iE 'audio|ahub|video|codec|hdmi|drm' [ 0.079206] /soc/hdmi@6000000: Fixed dependency cycle(s) with /soc/tcon-top@6510000 [ 0.079254] /soc/tcon-top@6510000: Fixed dependency cycle(s) with /soc/hdmi@6000000 [ 0.084097] /soc/hdmi@6000000: Fixed dependency cycle(s) with /soc/tcon-top@6510000 [ 0.084454] /soc/hdmi@6000000: Fixed dependency cycle(s) with /soc/tcon-top@6510000 [ 0.084604] /soc/tcon-top@6510000: Fixed dependency cycle(s) with /soc/hdmi@6000000 [ 0.086562] /soc/hdmi@6000000: Fixed dependency cycle(s) with /connector [ 0.086632] /connector: Fixed dependency cycle(s) with /soc/hdmi@6000000 [ 0.912097] sun4i-codec 5096000.codec: Failed to get the module clock [ 0.912123] sun4i-codec 5096000.codec: probe with driver sun4i-codec failed with error -2 [ 1.893626] sun4i-drm display-engine: bound 1100000.mixer (ops 0xffff8000811bd460) [ 1.893826] sun4i-drm display-engine: bound 6510000.tcon-top (ops 0xffff8000811c2200) [ 1.894162] sun4i-drm display-engine: bound 6515000.lcd-controller (ops 0xffff8000811ba228) [ 1.894226] sun8i-dw-hdmi 6000000.hdmi: supply hvcc not found, using dummy regulator [ 1.894461] sun8i-dw-hdmi 6000000.hdmi: Detected HDMI TX controller v2.12a with HDCP (DWC HDMI 2.0 TX PHY) [ 1.894775] sun8i-dw-hdmi 6000000.hdmi: EVENT=plugin [ 1.895002] sun8i-dw-hdmi 6000000.hdmi: registered DesignWare HDMI I2C bus driver [ 1.895247] sun4i-drm display-engine: bound 6000000.hdmi (ops 0xffff8000811bc528) [ 1.895741] [drm] Initialized sun4i-drm 1.0.0 for display-engine on minor 0 [ 1.895777] sun8i-dw-hdmi 6000000.hdmi: read_hpd result: 1 [ 2.082951] sun4i-drm display-engine: [drm] fb0: sun4i-drmdrmfb frame buffer device [ 6.372421] systemd[1]: Starting modprobe@drm.service - Load Kernel Module drm... [ 6.470837] systemd[1]: modprobe@drm.service: Deactivated successfully. [ 6.471579] systemd[1]: Finished modprobe@drm.service - Load Kernel Module drm. [ 7.573250] videodev: Linux video capture interface: v2.00 [ 7.688212] cedrus 1c0e000.video-codec: Device registered as /dev/video0 [ 7.887240] [drm] Initialized panfrost 1.3.0 for 1800000.gpu on minor 1 [ 9.349292] sun8i-dw-hdmi 6000000.hdmi: EVENT=plugout [ 9.349334] sun8i-dw-hdmi 6000000.hdmi: read_hpd result: 2 [ 9.498174] sun8i-dw-hdmi 6000000.hdmi: EVENT=plugin [ 9.498214] sun8i-dw-hdmi 6000000.hdmi: read_hpd result: 1 [ 9.498316] sun8i-dw-hdmi 6000000.hdmi: EVENT=plugin [ 19.333441] hdmi-audio-codec hdmi-audio-codec.5.auto: Only one simultaneous stream supported! [ 19.333474] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 19.333494] ahub_plat-i2s-hifi: ASoC: error at __soc_pcm_open on ahub_plat-i2s-hifi: -22 [ 29.107222] hdmi-audio-codec hdmi-audio-codec.5.auto: Only one simultaneous stream supported! [ 29.107251] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 29.107270] ahub_plat-i2s-hifi: ASoC: error at __soc_pcm_open on ahub_plat-i2s-hifi: -22 [ 941.536296] sun8i-dw-hdmi 6000000.hdmi: EVENT=plugin [ 1049.709728] sun8i-dw-hdmi 6000000.hdmi: EVENT=plugout [ 1049.709779] sun8i-dw-hdmi 6000000.hdmi: read_hpd result: 2 [ 1049.859960] sun8i-dw-hdmi 6000000.hdmi: EVENT=plugin [ 1049.859997] sun8i-dw-hdmi 6000000.hdmi: read_hpd result: 1 [ 1049.860100] sun8i-dw-hdmi 6000000.hdmi: EVENT=plugin [ 1066.819613] sun8i-dw-hdmi 6000000.hdmi: EVENT=plugin [ 1463.903829] sun8i-dw-hdmi 6000000.hdmi: EVENT=plugout [ 1463.903883] sun8i-dw-hdmi 6000000.hdmi: read_hpd result: 2 [ 1464.055245] sun8i-dw-hdmi 6000000.hdmi: EVENT=plugin [ 1464.055282] sun8i-dw-hdmi 6000000.hdmi: read_hpd result: 1 [ 1464.055381] sun8i-dw-hdmi 6000000.hdmi: EVENT=plugin
-
Yes that works fine. I have to edit this post as the video only works "fine" on a small window with a lower bit rate avi file (H264). Other videos I tested stuttered and got worse as the window size was increased. Most videos would not play in full screen mode (1920x1080), filling only 1/4 of the screen. I watched the system monitor while playing a video and cpu usage was very high 80-100% on all cores. Ok so I did some more investigation. The first quick test I did was with Celluloid and Media Player, the programs that come with Mate. I then installed vlc, because I wanted to see the codec info about the media. It is vlc that is a cpu hog! Both Celluloid and Media Player work well even at full screen. The cpu usage is around 50%.
-
I was hoping that there was a clock rate that needed to be divided by 2 or 4.
-
I think so. sysadmin@orangepizero3:~$ lsmod | grep lima lima 65536 0 gpu_sched 49152 2 lima,panfrost drm_shmem_helper 24576 2 lima,panfrost sysadmin@orangepizero3:~$ lsmod | grep gpu_sched gpu_sched 49152 2 lima,panfrost sysadmin@orangepizero3:~$ glxinfo -B name of display: :0 display: :0 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: Panfrost (0xffffffff) Device: Mali-G31 (Panfrost) (0xffffffff) Version: 22.3.6 Accelerated: yes Video memory: 1975MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 3.1 Max compat profile version: 3.1 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.1 OpenGL vendor string: Panfrost OpenGL renderer string: Mali-G31 (Panfrost) OpenGL core profile version string: 3.1 Mesa 22.3.6 OpenGL core profile shading language version string: 1.40 OpenGL core profile context flags: (none) OpenGL version string: 3.1 Mesa 22.3.6 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL ES profile version string: OpenGL ES 3.1 Mesa 22.3.6 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10 ********* display show gears running.*********** sysadmin@orangepizero3:~$ glxgears Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. 303 frames in 5.0 seconds = 60.491 FPS 301 frames in 5.0 seconds = 60.000 FPS 301 frames in 5.0 seconds = 60.000 FPS 300 frames in 5.0 seconds = 59.994 FPS ^C ************** Display show G3D **************** sysadmin@orangepizero3:~$ g3dviewer Gtk-Message: 09:52:52.184: Failed to load module "canberra-gtk-module" (g3dviewer:3131): LibG3D-WARNING **: 09:52:52.232: libg3d: plugins: failed to load /usr/lib/aarch64-linux-gnu/libg3d/plugins/import/imp_vrml.so: /usr/lib/aarch64-linux-gnu/libg3d/plugins/import/imp_vrml.so: undefined symbol: yywrap ** (g3dviewer:3131): CRITICAL **: 09:52:53.802: add_objects: assertion 'object->name != NULL' failed screenshot "g3dviewer-screenshot-g3d.ac.png" saved.
-
Using a Mate desktop provides the same results for the HDMI and sound as the Cinnamon tested previously. However the Mate desktop is very stable.
-
@going Thank you for updating the master with PR#7705. I have been able to build and test a Debian 12 Linux 6.13.7 cinnamon image for an orangepizero3 with the following results: HDMI works as expected. Initial resolution is monitor default (1920x1080) and there are lots of optional settings in the display manager. The monitor name was detected. Sound on HDMI works. Analog sound has a problem. It outputs audio after enabling channels with alsamixer but the audio rate is double or quadruple (cute funny sounds). I saw this problem when I worked on the initial sound patch, but it only occurred intermittently when changing between output sound devices. With the test image I can not get rid of it. Cinnamon did not work well, hanging on numerous occasions. The system did not crash and I was able to reboot from cli. I doubt this has anything to do with the recent patch. I will test again with a Mate desktop.
-
Then I will test again tomorrow.
-
@going Extra confirmation. Yesterday I cloned the master and built orangepizero3 debian edge images for cinnamon and xfce . Both hung on the initial load of the kernel. I then removed the above mentioned L472 patch and rebuilt the cinnamon image which now works.
-
@bhouseski I regularly boot directly from a usb connected SSD drive which is twice as fast as the SD card. First you have to put u-boot on the SPI flash. Find u-boot-sunxi-with-spl somewhere on the SD card you are running and flash it to SPI. The following is from the u-boot manual: Installing on SPI flash from Linux If the devicetree enables and describes the SPI flash device, you can access the SPI flash content from Linux, using the MTD utils: # apt-get install mtd-utils # mtdinfo # flashcp -v u-boot-sunxi-with-spl.bin /dev/mtdX You can then try to boot without an SD card installed. I had some difficulty in getting u-boot to consistently see the USB devices until I added a delay into the boot environment to allow time for the USB to connect. Stop the boot procedure and do the following. (The usb_pgood_delay variable did not exist on the opz3.) editenv usb_pgood_delay -> input a number, bigger than the existing (ms) (I used 5000, 5 sec) saveenv
-
@mantouboji Yes in testing for the Nov release I tested legacy, current and edge builds for the orangepione. Ambian-config managed the overlays properly. If you think there is a further problem with other builds you should document it thoroughly and submit a bug report. Would you also please remove the solution tag from your post of Oct 8. Telling someone to go fix it is not a solution for anything. Thankfully a number of people put in effort to determine that the root cause was in the build procedure and then corrected the procedure. That was the solution.
-
The official image works as it should. The edge image may in time be fixed when whoever is working on the changes finishes. It is called the "bleeding edge" for a reason. One can not expect all things to work properly with edge images.
-
Too many questions. Not enough answers.