Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • Is "do it in kernelspace" important to you (and if so, why exactly)? Because you'd typically don't do that in kernel space, but open the appropriate GPIO pseudofile, select so to get woken up when the state changes, and then do your I²C transfer – in userspace. You can technically do the same in kernel land, if you want to, but it's less clean and not necessarily lower-overhead. That's why I ask for the reason you want to do that in kernel space – depending on the reason, you'd approach this differently. Commented Dec 1 at 8:56
  • The intent is to get accurate and consistent time stamping and sample intervals. I was planning on using kernel GPIO interrupt which should be highly deterministic, I assume triggering I2C transfer makes sense then. Commented 2 hours ago