ChanServ changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630)
alpernebbi has quit [Ping timeout: 480 seconds]
alpernebbi has joined #aarch64-laptops
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
<Dylanger> Anyone know why I can't get the speakers working on Trogdor/Homestar?
<Dylanger> I'm using this, but pulse shows no audio devices
<Dylanger> Homestar uses `max98360a`
<Dylanger> `speaker-test -D plughw:CARD=sc7180rt5682max,DEV=1 -c 2`
<Dylanger> This works
<Dylanger> I can actually hear the speakers with this
<Dylanger> Ooo fair enough, cheers I'll be careful
<Dylanger> [ 961.540482] arm-smmu 15000000.iommu: Unhandled context fault: fsr=0x402, iova=0xfdef14e0, fsynr=0x200022, cbfrsynra=0x1021, cb=4
<Dylanger> [ 961.552193] MultiMedia1: bus access error
<Dylanger> [ 961.556456] arm-smmu 15000000.iommu: Unhandled context fault: fsr=0x402, iova=0xfdef26a0, fsynr=0x200022, cbfrsynra=0x1021, cb=4
<Dylanger> Getting this if I set `plughw:CARD=sc7180rt5682max,DEV=1` as the SPEAKER
<Dylanger> Interesting, seems to trip the SMMU
<Dylanger> I thought LPASS wasn't running as a remoteproc
<Dylanger> Hm yeah `plughw` works but regular `hw` doesn't
<Dylanger> I'm able to play an MP3/WAV from the speaker
<Dylanger> director@DRIFTWOOD:~$ pw-play --list-targets
<Dylanger> Available targets ("*" denotes default):
<Dylanger> I have a feeling the issue is pipewire
srinik has quit [Killed (NickServ (Too many failed password attempts.))]
srinik has joined #aarch64-laptops
macc24 has joined #aarch64-laptops
iivanov_ has joined #aarch64-laptops
iivanov_ has quit [Remote host closed the connection]
iivanov_ has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
<steev> unhepful comment, but i've been extremely unimpressed with the pipewire changeover
<broonie> Dylanger: That smells like the constraints in the driver aren't accurate and plughw happens to pick a configuration that doesn't trip them up.
<broonie> Userspace shouldn't be able to do anything that the IOMMU gets upset with, at least not without ignoring constraints.
<robclark> for more or less anything that isn't a gpu, I'd kinda hope that userspace couldn't trigger iommu faults
<broonie> Might be worth checking newer versions of the QC drivers for fixes, there does seem to be a lot of activity with them.
<broonie> robclark: well, quite.
pg12_ has joined #aarch64-laptops
pg12 has quit [Ping timeout: 480 seconds]
macc24 has quit [Ping timeout: 480 seconds]
<Dylanger> <broonie> "Dylanger: That smells like the..." <- When you say constraints do you mean within the kernel driver itself?
<Dylanger> Or the UCM2 Config
<broonie> I mean constraints that the hardware/firmware has.
<Dylanger> I think the `max98360a` is the DAC for all trogdor devices
<Dylanger> Hm, I see, so I may have to bytepatch from audio firmware
<Dylanger> <broonie> "Dylanger: That smells like the..." <- It was my understanding plughw simply added/converted the media to whatever the hw supported, then hw was just raw
<Dylanger> I didn't expect plughw to be able to dynamically select other configs
<broonie> It may be picking a different configuration to convert to to that which speaker-test picks when playing natively.
<Dylanger> Ah right, I'll need to strace it or something
<Dylanger> See wtf it's pulling