XPost: linux.debian.devel.release
Package: release.debian.org
Severity: normal
X-Debbugs-Cc:
[email protected]
Control: affects -1 + src:iio-sensor-proxy
User:
[email protected]
Usertags: unblock
Please unblock package iio-sensor-proxy
[ Reason ]
Fix buffer mode discovery on several devices like chromebooks
and Framework 12" laptops. Without these iio-sensor-proxy will
not read sensible values on these devices as buffer mode does
not provide any data although announced by the kernel.
[ Impact ]
iio-sensor-proxy will not work on these devices.
[ Tests ]
Patches have been tested upstream
https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/merge_requests/400
on the affected devices and I've tested on some devices availble to me
that the package doesn't break currently working ones. We also have
tests upstream (that run during package build).
[ Risks ]
Not very high as the code changes were confined (see attached debdiff).
[ Checklist ]
[x] all changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in testing
[ Other info ]
I've not yet uploaded the package yet as I wanted to check first if we
can fix this before release.
unblock iio-sensor-proxy/3.7-3
diff --git a/debian/changelog b/debian/changelog
index 46e5332..733426f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+iio-sensor-proxy (3.7-3) unstable; urgency=medium
+
+ * Backport upstream fixes to check not accidentaly use buffer
+ driver.
+
+ -- Guido G�nther <
[email protected]> Sat, 26 Jul 2025 10:08:39 +0200
+
iio-sensor-proxy (3.7-2) unstable; urgency=medium
* Upload to unstable
diff --git a/debian/patches/buffer_drv_data_new-rework-trigger_name-handling.patch b/debian/patches/buffer_drv_data_new-rework-trigger_name-handling.patch
new file mode 100644
index 0000000..ebcd81d
--- /dev/null
+++ b/debian/patches/buffer_drv_data_new-rework-trigger_name-handling.patch
@@ -0,0 +1,128 @@
+From: "Sicelo A. Mhlongo" <
[email protected]>
+Date: Sun, 25 May 2025 19:17:51 +0200
+Subject: buffer_drv_data_new: rework trigger_name handling
+
+In each buffer driver, the get_trigger_name() call is always immediately +followed by a call to buffer_drv_data_new(). To simplify the code, +buffer_drv_data_new() now calls get_trigger_name(). Inci