https://devzone.nordicsemi.com/f/nordic-q-a/112029/zephyr-uart-driver-and-compatibilityLooking at the uart_nrfx_uarte2.c driver it appears that Nordic is not looking for the compatibility string in the driver but instead is looking for uart0,uart1, etc. This seems to violate the correct way to create a driver for Zephyr. When can we expecten-USTelligent Community 13Wed, 12 Jun 2024 09:12:53 GMThttps://devzone.nordicsemi.com/thread/488452?ContentTypeID=1Wed, 12 Jun 2024 09:12:53 GMT137ad170-7792-4731-bb38-c0d22fbe4515:ccdd2d8d-db1d-4419-87d2-56e8cbf9d238Hieu<p>Hi Trampas,</p> <p>Do you mean how the implementation doesn&#39;t use&nbsp;DT_DRV_COMPAT?</p> <p>If so, then it is just because the driver uses a different approach.&nbsp;Please refer to this docs:<br /><a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.6.1/zephyr/build/dts/howtos.html#write-device-drivers-using-devicetree-apis">Devicetree HOWTOs — Zephyr Project documentation (nRF Connect SDK) (nordicsemi.com)</a></p> <p>Hieu</p><div style="clear:both;"></div>