Userland PM16D17 #582
Userland PM16D17 #582
Conversation
Add restarting the service after adding the drop-in. Signed-off-by: Baocheng Su <[email protected]>
The current PM16D17 kernel sensor driver is not using the existing kernel API, but self-invented device tree bindings, which is rejected while upstreaming, see [1]. This patch replaces the kernel driver with a user-land driver. 1. https://lore.kernel.org/linux-iio/[email protected]/ Signed-off-by: Baocheng Su <[email protected]>
| @@ -15,6 +15,7 @@ | |||
| from datetime import datetime | |||
| from systemd import journal | |||
| from enum import Enum | |||
| from pystemd.dbuslib import DBus, DbusMessage | |||
There was a problem hiding this comment.
Make the event-record an identical user story?
There was a problem hiding this comment.
There is a leakage due to the lack of kernel ABI or userspace API compatibility, which seems to be an unmanageable limitation.
Otherwise, looks good to me.
There was a problem hiding this comment.
Regarding our upcoming release, we may need to hold off on merging this PR to avoid involving additional third-party libraries for OSS clearance.
|
Quite a lot of changes... Given all this effort, it might have been worth to make at least the complications with Everlight transparent to upstream and ask for further guidance. |
Sure, I will append our new findings to the kernel mailing list. |
Upstream is hard for this chip driver, we decide to use userland driver instead.