https://devzone.nordicsemi.com/f/nordic-q-a/119825/sdk2-9-0---qspi-and-twi-driver-power-management-config_pm_device_runtimeHi. After migration from SDK2.7.0 to SDK2.9.0 I have issues with power mangement. CONFIG_PM_DEVICE_RUNTIME=y, which I used, causes that twi driver doesn&#39;t start. I try to manage with this issue and call pm_device_runtime_enable(i2c_dev) when I initen-USTelligent Community 13Wed, 19 Mar 2025 08:22:59 GMThttps://devzone.nordicsemi.com/thread/527954?ContentTypeID=1Wed, 19 Mar 2025 08:22:59 GMT137ad170-7792-4731-bb38-c0d22fbe4515:5c26e354-008d-4414-a971-90438b515590Sigurd Hellesvik<p>Hi,</p> [quote user=""]1. Is it right way? Is it enough to&nbsp;make that twi_driver power management works automatically?[/quote] <p>I bet that the change you see between v2.7.0 and v2.9.0 is related to <a href="https://github.com/nrfconnect/sdk-zephyr/commit/9f0ebb64a610745f2dd14a4b6adae8b7023134fe">This Commit</a>.</p> <p>From this, it looks to me that nrfx_twim_enable() is not longer called automatically by the TWI init code. So in this case, I agree that it looks like you will have to use Power Management to enable TWI now.</p> [quote user=""]2. How to manage qspi driver? (I have external flash on board). The same way will be OK? In this case, I have no idea where to call pm_device_runtime_enable.[/quote] <p>No, external flash over QSPI is a bit different. I believe that this should be enabled at first. Then you can put the external flash into Deep Power Down (DPD) mode + uninit the QSPI using the Power Management API. See here for <a href="https://github.com/nrfconnect/sdk-zephyr/blob/9f0ebb64a610745f2dd14a4b6adae8b7023134fe/drivers/flash/nrf_qspi_nor.c#L1261">driver code</a> (And wake it up the also).</p> <p>Regards,<br />Sigurd Hellesvik</p><div style="clear:both;"></div>