#asahi-dev · 2022-10-17 12:41
jannauremaining battery trippled from almost trippled from ~4h to 12h#asahi-dev · 2022-10-17 12:40
jannauwow, running kcalc in the background uses ~6W#asahi-dev · 2022-10-16 13:43
jannauChaosPrincess: done#asahi-dev · 2022-10-16 13:13
jannaulooks like it#asahi-dev · 2022-10-16 13:05
jannauit does a read after a write but for both channels. I added a debug printk in the generic ioctl handler#asahi-dev · 2022-10-16 13:01
jannaupovik: the ioctl argument is struct snd_ctl_elem_value so it should be able to set channels values atomically#asahi-dev · 2022-10-16 12:38
jannauyes, m2 macbook pro 13"#asahi-dev · 2022-10-16 12:38
jannauChaosPrincess: I'm looking and will test on j493#asahi-dev · 2022-10-16 12:36
jannaupovik: do you know if it is expected that alsamixer uses 2 write ioctls to update the DAC volume?#asahi-dev · 2022-10-16 12:34
jannaui.e. audio worked without replug#asahi-dev · 2022-10-16 12:32
jannaupovik: plug detection worked now#asahi-dev · 2022-10-16 12:32
jannauyes, the i2c irq patch makes the volume control much faster. thanks amarioguy #asahi-dev · 2022-10-16 12:13
jannaupovik: yes, plug and mic are detected on initial driver load#asahi-dev · 2022-10-16 12:05
jannaupovik: please include the cs42l42 compatible removal, I will close my PR as the m1 ultra cpufreq dt fix won't make sense if marcan rewrites cpufreq#asahi-dev · 2022-10-16 12:02
jannauthere is the keyboard backlight PR#asahi-dev · 2022-10-16 12:02
jannaumarcan: bluetooth v3 to get rid of the revert which broke bluetooth#asahi-dev · 2022-10-16 12:01
jannaupovik: plug/mic detection is logged during boot so the driver might just lose the state?#asahi-dev · 2022-10-16 11:58
jannauyes, I was thinking the same#asahi-dev · 2022-10-16 11:55
jannaudid you check if the i2c irq support improves this?#asahi-dev · 2022-10-16 11:54
jannauuser experience seems to still bad due to slow volume updates of the driver#asahi-dev · 2022-10-16 11:53
jannauthe kde balance behavior might be intentional. it seems to adjust both channels and the resets unmodified channel. with the fixed volume scale it's much better#asahi-dev · 2022-10-16 11:50
jannaubehavior in alsamixer is now good, muting works#asahi-dev · 2022-10-16 11:49
jannaupovik: headset detection didn't work on boot, I had to replug the headset#asahi-dev · 2022-10-16 11:48
jannaupovik: known and fixed in the version merged for 6.1#asahi-dev · 2022-10-16 11:20
jannaureference distro uses pulse#asahi-dev · 2022-10-16 11:11
jannauat some point asahi shipped pulseaudio. I explicitly installed pipewire#asahi-dev · 2022-10-16 11:10
jannauyes, using pipewire#asahi-dev · 2022-10-16 11:10
jannauspeakers disabled here, if I unplug the headphone it switches the profile to "Off" and displays no output profiles#asahi-dev · 2022-10-16 11:08
jannauyeah, I have "n/a" as profile for the headphones as well but headphone out works#asahi-dev · 2022-10-16 11:01
jannauyes, this is with the latest ucm#asahi-dev · 2022-10-16 11:01
jannaumodifying the volume of a single channel modifies first both channels before setting both to the intended values#asahi-dev · 2022-10-16 10:59
jannaudoesn't fix the kde audio settings balance issue. issue there could be even more an user space issue#asahi-dev · 2022-10-16 10:51
jannauonly question is if it makes sense that alsamixer uses non-linear scaling on top#asahi-dev · 2022-10-16 10:48
jannauthe actual values look reasonable for a non-linear 0-100 scale. I don't think anyone will hear a difference between -156.0 and -256.0 dB gain#asahi-dev · 2022-10-16 10:46
jannauwithout mute it goes down to -256.0 and then jumps up to -120.0#asahi-dev · 2022-10-16 10:44
jannauit has a TODO comment#asahi-dev · 2022-10-16 10:38
jannauseems to affect pipewire volumes controls as well. I first triggered it kde balnce controls#asahi-dev · 2022-10-16 10:37
jannaupovik: with the mute flag I see a wraparound from 0 (-156 dB) to 100 (-0.5 dB) in alsamixer#asahi-dev · 2022-10-16 10:30
jannauno, it's the mute flag in DECLARE_TLV_DB_SCALE. single character fix#asahi-dev · 2022-10-16 10:04
jannauprogression of volume values is 283, 200, 511. so it gets bad after LSB increases despite decreasing the volume#asahi-dev · 2022-10-16 10:01
jannauno, the problem seems to be in alsa code before the volume write function, maybe the issue is the alsa uses the register values directly, the control has just the LSB regs#asahi-dev · 2022-10-16 09:39
jannauI guess the converted integer values get negative and due to the overflow in the signed to unsigned conversion we write 511 (the max) to the registers, probably fixed by using SOC_DOUBLE_R_S_TLV which allows us to specify a minimum#asahi-dev · 2022-10-16 08:47
jannauaahhhhhhh! j493 CS42L84 Jack DAC wraps around from min to max gain, asahi-wip and alsa-ucm-conf-asahi 645f6c7#asahi-dev · 2022-10-13 20:48
jannauinteresting, an OOM due to linking chromium caused DCP to break. it did not crash but scanout was certainly broken. instantly a black screen#asahi-dev · 2022-10-11 22:28
jannauall dcp/dcpext? share their __TEXT segment#asahi-dev · 2022-10-11 22:27
jannau32 byte per segment, 8-byte physical addr, 8 bytes unknown, 8-byte device address, 4-byte size, remeining 4 bytes look like flags#asahi-dev · 2022-10-11 22:23
jannausigh, dcp*'s __TEXT is not mapped in their dart. "segment-ranges" in iop-dcp*-nub finally make sense#asahi-dev · 2022-10-10 21:32
jannau\o/#asahi-dev · 2022-10-10 21:31
jannauLinus has merged t600x dart: https://lore.kernel.org/lkml/166543539761.11766.7130453309101940100.pr-tracker-bot@kernel.org/#asahi-dev · 2022-10-08 21:18
jannauyeah! I'm doing something that DCP doesn't like and but it doesn't crash. trying to add support for YUV pixelformats and it reports underruns