Skip to content

Conversation

@bmasta018
Copy link
Contributor

Add new recipe for Qualcomm Sensors Proprietary modules which provides sensors streaming data to Sensing Hub.

DESCRIPTION = "Prebuilt libraries and test applications for sensors services"
LICENSE = "LICENSE.qcom-2"
LIC_FILES_CHKSUM = "file://${UNPACKDIR}/usr/share/doc/sensors/NO.LOGIN.BINARY.LICENSE.QTI.pdf;md5=7a5da794b857d786888bbf2b7b7529c8"
SRC_URI = "https://qartifactory-edge.qualcomm.com/artifactory/qsc_releases/software/chip/component/sensors.lnx.0.0/${PBT_BUILD_DATE}/prebuilt_yocto/qcom-sensors-prebuilts_${PV}_armv8a.tar.gz"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please move the declaration of PBT_BUILD_DATE before its first use.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why? I think it makes sense. I usually ask to have PBT_BUILD_DATE grouped together with the sha256sum as those two change together.

@@ -0,0 +1,66 @@
SUMMARY = "Prebuilt Qualcomm sensors libraries and test applications"
DESCRIPTION = "Prebuilt libraries and test applications for sensors services"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add a proper description of what these libraries and test applications are actually doing, this is just too generic.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated the description in latest patch

DESCRIPTION = "Prebuilt libraries and test applications for sensors services"
LICENSE = "LICENSE.qcom-2"
LIC_FILES_CHKSUM = "file://${UNPACKDIR}/usr/share/doc/sensors/NO.LOGIN.BINARY.LICENSE.QTI.pdf;md5=7a5da794b857d786888bbf2b7b7529c8"
SRC_URI = "https://qartifactory-edge.qualcomm.com/artifactory/qsc_releases/software/chip/component/sensors.lnx.0.0/${PBT_BUILD_DATE}/prebuilt_yocto/qcom-sensors-prebuilts_${PV}_armv8a.tar.gz"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why? I think it makes sense. I usually ask to have PBT_BUILD_DATE grouped together with the sha256sum as those two change together.

ln -sf libSEESalt.so.${PV} ${D}${libdir}/libSEESalt.so.0
ln -sf libSEESalt.so.${PV} ${D}${libdir}/libSEESalt.so

# Install proto , registry and Service files
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Registry would be a part of the per-device data, so it probably should go to hexagon-dsp-binaries.

Copy link
Contributor Author

@bmasta018 bmasta018 Dec 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As we understand it, hexagon-dsp-binaries typically contains compiled DSP executables or shared objects built with the Hexagon C/C++ toolchain.
Placing configuration files into hexagon-dsp-binaries requires careful consideration of their final locations on the target filesystem (for example, under /etc/ or /firmware/). In parallel, from a SensingHub firmware perspective, these configuration files are expected to reside at predefined, fixed locations on the target. Changing the paths to these JSON files would break the current expectations in the firmware’s parsing logic and would require corresponding changes in the firmware as well.
we got your point and we will consider this and come back when we open source our HLOS source code in coming days. Considering this as a artifacts and end to end enablement perspective - we feel it should be fine for now withe current status.
Kindly let us know your feedback.

@github-actions
Copy link

github-actions bot commented Dec 9, 2025

Test run workflow

Test jobs for commit 1bfc488

@test-reporting-app
Copy link

test-reporting-app bot commented Dec 9, 2025

Test Results

 14 files  ±0   28 suites  ±0   37m 15s ⏱️ + 1m 37s
 50 tests ±0   50 ✅ ±0  0 💤 ±0  0 ❌ ±0 
304 runs  ±0  304 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 1bfc488. ± Comparison against base commit 65bdc36.

♻️ This comment has been updated with latest results.

SUMMARY = "Prebuilt Qualcomm sensors libraries and test applications"
DESCRIPTION = "Prebuilt libraries and test applications for sensors services"
LICENSE = "LICENSE.qcom-2"
LIC_FILES_CHKSUM = "file://${UNPACKDIR}/usr/share/doc/sensors/NO.LOGIN.BINARY.LICENSE.QTI.pdf;md5=7a5da794b857d786888bbf2b7b7529c8"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please stop using the .pdf file to mention the License. The tarball must include LICENSE.qcom-2 file.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, the CHANGES file isn't updated, there is no NOTICE eaither.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added the LICENSE file in txt format. The changes files and Notice file has also been updated.

@github-actions
Copy link

github-actions bot commented Dec 9, 2025

Test run workflow

Test jobs for commit 1bfc488

Prebuilt core binaries required for sensor enablement and
hardware sensor data access. These prebuilt binaries also
Includes test applications to validate sensor services
functionality through the Sensinghub Interface.

Signed-off-by: Bhanu Vivek Matsa <[email protected]>
@bmasta018 bmasta018 force-pushed the sensors-prebuilts-enablement branch from 1bfc488 to 4f38376 Compare December 11, 2025 12:46
@@ -0,0 +1,55 @@
SUMMARY = "Prebuilt Qualcomm sensors libraries and test applications"
DESCRIPTION = "Prebuilt core binaries required for sensor enablement and hardware sensor data access. These prebuilt binaries also Includes test applications to validate sensor services functionality through the Sensinghub Interface."
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/Includes/include

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.

5 participants