This is not tied to a current confirmed product issue. It is a general architectural concern that is likely to appear for latency-sensitive interrupt workloads. Having a common pw_kernel primitive would avoid future one-off driver implementations and provide a clearer model for handling devices where userspace wake-up latency is insufficient.
This is not tied to a current confirmed product issue. It is a general architectural concern that is likely to appear for latency-sensitive interrupt workloads. Having a common pw_kernel primitive would avoid future one-off driver implementations and provide a clearer model for handling devices where userspace wake-up latency is insufficient.