On Tue, Nov 22, 2016 at 5:26 PM, Bastien Nocera <had...@hadess.net> wrote:
> On Tue, 2016-11-22 at 17:23 +0100, Lennart Poettering wrote: > > On Tue, 22.11.16 12:13, Bastien Nocera (had...@hadess.net) wrote: > > > > > Hey, > > > > > > I'm adding support for reading the mount-matrix[1] from > > > accelerometer > > > devices in iio-sensor-proxy, but we'll need to add a way to > > > override > > > the mount-matrix in case the data from the device-tree is > > > incorrect, or > > > missing[2]. > > > > > > I was wondering whether we should ship the hwdb quirks in systemd > > > or > > > iio-sensor-proxy. > > > > > > Opinions? > > > > If it's generic enough then the hwdb is definitely a good place for > > things like that. If the concept however only has value for > > iio-sensor-proxy specifically then it should probably live in that > > package. Of course the lines are blurry there, so compare with the > > input case: hwdb carries dpi quirk data for all kinds of mice, and if > > this data is like that, then it fits in. > > The quirks apply to the devices, and are in the same format as what's > offered by the kernel when the firmware provides it, so it's not iio- > sensor-proxy specific in any way. If we were to replace iio-sensor- > proxy, we'd still use this metadata. > > I'll send a patch in as soon as I've done testing on a machine that > does need this quirking. > Hi Bastien, I recently opened a PR to iio-sensor-proxy with a quirk for my laptop. Since this is my main computer testing is easy. Let me know if I can help.
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel