D

These drivers should not differ much from each other, right? Anyway, I found a reasonable patch to fix this behavior. I couldn't see this in the Armbian kernel, but what I need is: patch.

Linux 6.1.31-sun50iw9 #1.0.4 SMP Wed Aug 6 19:06:53 UTC 2025 aarch64 GNU/Linux I couldn't find any known kernel issues.

Unfortunately, LLM is wrong here. There are MAX98357A boards, such as the violet one, which support (L+R)/2 and single/selected channel modes. I was able to configure the board using ESP32 and a sinus wave, so I can confirm it is possible and the board is not malfunctioning. For some reason, the sunxi driver (or ALSA) misbehaves, and I can't determine where the problem is.

Hi everyone, I got my OrangePi Zero 2W to work with MAX98357A board, the violet one, but I can only hear one channel. I didn't modify ALSA much, just focused on DTS: ... fragment@1 { target-path = "/soc"; __overlay__ { ahub0_plat: ahub0_plat { #sound-dai-cells = <0>; compatible = "allwinner,sunxi-snd-plat-ahub"; apb_num = <2>; /* for dma port 5 */ dmas = <&dma 5>, <&dma 5>; dma-names = "tx", "rx"; playback_cma = <128>; capture_cma = <128>; tx_fifo_size = <128>; rx_fifo_size = <128>; tdm_num = <0>; tx_pin = <0>; rx_pin = <0>; pinctrl-names = "default", "sleep"; pinctrl_used; pinctrl-0 = <&ahub_daudio0_pins_a>, <&ahub_daudio0_pins_b>, <&ahub_daudio0_pins_c>; pinctrl-1 = <&ahub_daudio0_pins_d>; status = "okay"; }; ahub0_mach: ahub0_mach { compatible = "allwinner,sunxi-snd-mach"; soundcard-mach,name = "ahubi2s0"; soundcard-mach,format = "i2s"; soundcard-mach,frame-master = <&ahub0_cpu>; soundcard-mach,bitclock-master = <&ahub0_cpu>; soundcard-mach,slot-num = <2>; soundcard-mach,slot-width = <32>; status = "okay"; ahub0_cpu: soundcard-mach,cpu { sound-dai = <&ahub0_plat>; soundcard-mach,pll-fs = <4>; soundcard-mach,mclk-fs = <0x100>; }; ahub0_codec: soundcard-mach,codec { }; }; hdmi: hdmi@6000000 { status = "disabled"; }; }; }; ... Did I miss something, and now I'm hearing only the left channel? Has anyone managed to listen to stereo using external DAC? Best!

Thanks for replying @ag123. I don't negate the fact that my dts might be broken (review below), but why can't see `pwmchip0` in `/sys/class/pwm`? That indicates a release bug as arm64-dts-sun50i-h618-orangepi-zero2w-add-dtb.patch enables `pwm` and `pwm5`. /dts-v1/; /plugin/; / { compatible = "allwinner,sun50i-h616"; fragment@0 { target = <&pio>; __overlay__ { pwm4_pin: pwm4-pin { pins = "PI14"; function = "pwm4"; }; }; }; fragment@1 { target-path = "/"; __overlay__ { backlight_pwm: backlight_pwm { compatible = "pwm-backlight"; brightness-levels = <0 25 50 75 100 125 150 175 200 225 255>; default-brightness-level = <6>; pwms = <&pwm 4 25000 0>; pwm_names = "backlight"; status = "okay"; }; }; }; fragment@2 { target-path = "/soc"; __overlay__ { pwm4: pwm4@0300a000 { compatible = "allwinner,sunxi-pwm4"; pinctrl-names = "default"; pinctrl-0 = <&pwm4_pin>; status = "okay"; }; }; }; fragment@3 { target = <&spi1>; __overlay__ { status = "okay"; cs-gpios = <&pio 7 5 0>; /*PH5=CS0 PH9=CS1*/ ili9341: ili9341@0 { compatible = "adafruit,yx240qv29", "ilitek,ili9341"; reg = <0>; pinctrl-names = "default"; spi-max-frequency = <48000000>; rotation = <270>; reset-gpios = <&pio 8 6 0>; /* PI6 */ dc-gpios = <&pio 7 4 0>; /* PH4 */ backlight = <&backlight_pwm>; }; ads7846: ads7846@0 { compatible = "ti,ads7846"; reg = <1>; pinctrl-names = "default"; spi-max-frequency = <2000000>; interrupts = <8 5 1>; /* PI5 - IRQ */ interrupt-parent = <&pio>; pendown-gpio = <&pio 8 5 1>; /* PI5 */ ti,swap-xy = <1>; ti,keep_vref_on = /bits/ 16 <1>; ti,x-min = /bits/ 16 <280>; ti,y-min = /bits/ 16 <350>; ti,x-max = /bits/ 16 <3850>; ti,y-max = /bits/ 16 <3850>; ti,pressure-min = /bits/ 16 <0>; ti,pressure-max = /bits/ 16 <255>; ti,x-plate-ohms = /bits/ 16 <133>; ti,debounce-max = /bits/ 16 <50>; ti,debounce-tol = /bits/ 16 <30>; ti,debounce-rep = /bits/ 16 <1>; wakeup-source; }; }; }; fragment@4 { target = <&pwm>; __overlay__ { sunxi-pwms = <&pwm4>, <&pwm5>; }; }; };

Hi! OrangePi Zero 2w user here: I'm trying to understand why there is no `pwmchip0` in `/sys/class/pwm`. I'm using the latest kernel 6.6.31 with an extra dts overlay. I noticed that there is uart5 enabled by default, so I should see `pwmchip0`, right? Was there any regression reported? EDIT: also, why is there a definition for pwm5 when it does not exist?

Hi, I'm migrating from the OrangePi image to Armbian, and can't make the touchscreen working, it does not respond to any actions. It works pretty well on the OrangePi's image. Did I mess up something here? uname -a: Linux orangepizero2w 6.6.31-current-sunxi64 #1 SMP Fri May 17 10:02:40 UTC 2024 aarch64 GNU/Linux Touchscreen DTS: /dts-v1/; /plugin/; / { compatible = "allwinner,sun50i-h616"; fragment@0 { target-path = "/"; __overlay__ { backlight_gpio: backlight_gpio { compatible = "gpio-backlight"; gpios = <&pio 8 14 0>; // PI14 default-on; }; /*backlight_pwm: backlight_pwm { compatible = "pwm-backlight"; brightness-levels = <0 25 50 75 100 125 150 175 200 225 255>; default-brightness-level = <6>; pwms = <&pwm 4 25000 0>; // PI14 pwm_names = "backlight"; status = "okay"; };*/ }; }; fragment@1 { target = <&spi1>; __overlay__ { status = "okay"; cs-gpios = <&pio 7 5 0>; /*PH5=CS0 PH9=CS1*/ ili9341: ili9341@0 { compatible = "adafruit,yx240qv29", "ilitek,ili9341"; reg = <0>; pinctrl-names = "default"; spi-max-frequency = <48000000>; rotation = <270>; reset-gpios = <&pio 8 6 0>; /* PI6 */ dc-gpios = <&pio 7 4 0>; /* PH4 */ backlight = <&backlight_gpio>; }; ads7846: ads7846@0 { compatible = "ti,ads7846"; reg = <1>; pinctrl-names = "default"; spi-max-frequency = <2000000>; interrupts = <8 5 1>; /* PI5 - IRQ */ interrupt-parent = <&pio>; pendown-gpio = <&pio 8 5 0>; /* PI5 */ ti,swap-xy = <1>; ti,keep_vref_on = /bits/ 16 <1>; ti,x-min = /bits/ 16 <280>; ti,y-min = /bits/ 16 <350>; ti,x-max = /bits/ 16 <3850>; ti,y-max = /bits/ 16 <3850>; ti,pressure-min = /bits/ 16 <0>; ti,pressure-max = /bits/ 16 <255>; ti,x-plate-ohms = /bits/ 16 <133>; ti,debounce-max = /bits/ 16 <50>; ti,debounce-tol = /bits/ 16 <30>; ti,debounce-rep = /bits/ 16 <1>; wakeup-source; }; }; }; }; Xorg.0.log (fragment): [ 19.707] (II) config/udev: Adding input device ADS7846 Touchscreen (/dev/input/event0) [ 19.707] (**) ADS7846 Touchscreen: Applying InputClass "libinput touchscreen catchall" [ 19.707] (**) ADS7846 Touchscreen: Applying InputClass "calibration" [ 19.707] (II) LoadModule: "libinput" [ 19.708] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so [ 19.733] (II) Module libinput: vendor="X.Org Foundation" [ 19.733] compiled for 1.21.1.3, module version = 1.2.1 [ 19.733] Module class: X.Org XInput Driver [ 19.733] ABI class: X.Org XInput driver, version 24.4 [ 19.733] (II) Using input driver 'libinput' for 'ADS7846 Touchscreen' [ 19.733] (**) ADS7846 Touchscreen: always reports core events [ 19.733] (**) Option "Device" "/dev/input/event0" [ 19.772] (II) event0 - ADS7846 Touchscreen: is tagged by udev as: Touchscreen [ 19.773] (II) event0 - ADS7846 Touchscreen: device is a touch device [ 19.773] (II) event0 - ADS7846 Touchscreen: device removed [ 19.824] (**) Option "config_info" "udev:/sys/devices/platform/soc/5011000.spi/spi_master/spi1/spi1.1/input/input0/event0" [ 19.824] (II) XINPUT: Adding extended input device "ADS7846 Touchscreen" (type: TOUCHSCREEN, id 6) [ 19.825] (**) Option "AccelerationScheme" "none" [ 19.825] (**) ADS7846 Touchscreen: (accel) selected scheme none/0 [ 19.825] (**) ADS7846 Touchscreen: (accel) acceleration factor: 2.000 [ 19.825] (**) ADS7846 Touchscreen: (accel) acceleration threshold: 4 [ 19.828] (II) event0 - ADS7846 Touchscreen: is tagged by udev as: Touchscreen [ 19.829] (II) event0 - ADS7846 Touchscreen: device is a touch device [ 19.831] (II) config/udev: Adding input device ADS7846 Touchscreen (/dev/input/mouse0) [ 19.831] (**) ADS7846 Touchscreen: Applying InputClass "calibration" [ 19.831] (II) No input driver specified, ignoring this device. [ 19.831] (II) This device may have been added with another device file. [ 19.833] (II) config/udev: Adding input device sunxi-ir (/dev/input/event1) [ 19.833] (**) sunxi-ir: Applying InputClass "libinput keyboard catchall" [ 19.833] (II) Using input driver 'libinput' for 'sunxi-ir' [ 19.833] (**) sunxi-ir: always reports core events [ 19.833] (**) Option "Device" "/dev/input/event1" [ 19.836] (II) event1 - sunxi-ir: is tagged by udev as: Keyboard Pointingstick

Hi everyone! I wonder if modifying the "fbdev" driver to use Mali GPU to improve gaming performance is possible. I enabled `gpu` dtb, but according to "glxinfo -B" it uses "Device: llvmpipe, Accelerated: no". I'm curious if this can be improved somehow. BTW I found this old commit for Odroid C2: link