Skip to content

Conversation

@minlexx
Copy link
Contributor

@minlexx minlexx commented Feb 14, 2025

On some older SoCs (older than SDM845) downstream userspace starts a Sensor Registry service (271) to provide sensor configuration information to a remote processor (SDSP or ADSP). After receiving registry data, SDSP or ADSP exposes a Sensor Manager service "SMGR" (256), which allows to access sensor readings. Add these services to the known list of services.

Tested on sdm660 device with userspace sns-reg service running:

$ qrtr-lookup | grep -i sens
       23       1        0    0    23 Thermal sensors service
     4097 N/A      192    1 16401 DIAG service (SENSORS:CNTL)
     4097 N/A      194    1 16403 DIAG service (SENSORS:DATA)
     4097 N/A      196    1 16404 DIAG service (SENSORS:DCI)
      271       2        0    1 16418 Sensor Registry service
      256       1       50    5    60 Sensor Manager service

(last 2 lines with IDs 256 & 271)

On some older SoCs (older than SDM845) downstream userspace starts a
Sensor Registry service (271) to provide sensor configuration information
to a remote processor (SDSP or ADSP). After receiving registry data, SDSP
or ADSP exposes a Sensor Manager service "SMGR" (256), which allows to
access sensor readings. Add these services to the known list of services.

Signed-off-by: Alexey Minnekhanov <alexeymin@postmarketos.org>
@lumag lumag merged commit 5923eea into linux-msm:master Mar 1, 2025
2 checks passed
@minlexx minlexx deleted the lookup-new-smgr-ids branch March 2, 2025 14:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants