Speaker protection

[anonymix007]

How to use the speaker protection module?

Suppose I have the following graph: https://github.com/linux-msm/audioreach-topology/blob/main/X1E80100-LENOVO-Thinkpad-T14s.m4

How would I need to change it to make use of speaker protection?
What parameters would I need to set for it to work?

[quic-plai]

Hi,
Yes, we are aware of community feedback about lack of speaker protection support. There is on-going effort to enable speaker protection support based on AudioReach ASoC topology architecture. In kernel, we are adding control link support to use case graph which would allow speaker protection modules running in ADSP to communicate temperature and excursion data. In userspace, plan is to have userspace daemon to set up the path to feed temperature data from speaker amp to SoC and also supply calibration data. Support will come in next few months.

[herbsmn]

Hello. This is very exciting. Is there a place where one can view your progress on this?

[quic-plai]

Thanks for taking notice of the discussion. Yes, we are actively working on speaker protection enablement in collaboration with Linaro folks. Soon , we will have control link & static calibration patches upstream into sound/soc/qcom/qdsp6 followed by VI feedback kernel patch. Will keep this thread updated with latest progress.

[github-actions]

AudioReach/audioreach.triage This issue has been marked as stale due to 30 days of inactivity.

[herbsmn]

Any updates on this? May 14, 2026 21:21:08 github-actions[bot] ***@***.***>:

…

[Image]*github-actions[bot]* left a comment (AudioReach/audioreach-graphservices#1)[#1 (comment)] AudioReach/audioreach.triage This issue has been marked as stale due to 30 days of inactivity. — Reply to this email directly, view it on GitHub[#1 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ACBKRURMPDO2BWMVBYBOWHL42Z5IPAVCNFSM6AAAAACY62DVPOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DINJWGMZDIOBZGA]. Triage notifications on the go with GitHub Mobile for iOS[https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675] or Android[https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub]. You are receiving this because you commented. [Tracking image][https://github.com/notifications/beacon/ACBKRUUEAQGLEKUPL3IEBPL42Z5IPBFCNFSM6AAAAACY62DVPOWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTYAAAAACCM6D4NKM4TFMFZW63VHMNXW23LFNZ2A.gif]

[github-actions]

AudioReach/audioreach.triage This issue has been marked as stale due to 30 days of inactivity.

[quic-plai]

Hi @herbsmn ,

Sorry for delayed response. We actually have been making progress though not quite at the pace we would like. On kernel driver side, we have upstreamed following changes
https://lore.kernel.org/all/20251217094602.55117-3-krzysztof.kozlowski@oss.qualcomm.com/
https://lore.kernel.org/all/20260326113531.3144998-1-ravi.hothi@oss.qualcomm.com/
There is other pending change to be posted. At the same time, we are still working to release speaker protection module running on Hexagon DSP.

May I know which Qualcomm-based product you are looking to enable speaker protection?