Direct usage of a kernel driver for lower level access to a sensor?

RE: Direct usage of a kernel driver for lower level access to a sensor?

Benik3 — Wed, 18 Feb 2026 08:47:47 GMT

I ended simply with using generic I2C driver and mapping the ctx for STM32 ipa driver. At the end it was easier then I though :)

RE: Direct usage of a kernel driver for lower level access to a sensor?

Benik3 — Tue, 17 Feb 2026 09:58:03 GMT

Hi.
Thanks for the reply.
So the best would be probably to make a new custom driver (which will be almost copy of the actual driver) but it will expose the needed functions in the driver API.

Or of course I should be able to simply use the the I2C directly, in such case I just have to investigate, how it is mapped to the stm ipa driver.

I have also one maybe "heretical" idea: What to make a custom driver, map the I2C line (using the STMEMSC_CTX_I2C) and expose this ctx object in the driver API so I can use it with the stm ipa driver directly (and I don't have to do zephyr driver wrapper definition for each function)?

RE: Direct usage of a kernel driver for lower level access to a sensor?

Vidar Berg — Fri, 13 Feb 2026 15:07:13 GMT

Hello,

Please have a look at this devafademy course : https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-7-device-driver-dev/topic/device-driver-model-2/, and see if this helps you get started. I have not looked at this particular driver integration but I don't see why you should not be able to reuse existing parts of the ST driver and include it in your application, but I see lsm6dso.c is created specifically for the sensor API.

Best regards,

Vidar