RE: High Current Consumption when UART is configured with disable-rx flag and zephyr,pm-device-runtime-auto

Prodromos Kampas — Tue, 22 Jul 2025 14:46:42 GMT

We are using the LOG() macros from zephyr I am not sure how we can use the code you suggest.

RE: High Current Consumption when UART is configured with disable-rx flag and zephyr,pm-device-runtime-auto

Prodromos Kampas — Thu, 17 Jul 2025 12:29:24 GMT

The main problem we are dealing with is that without the use of the disable-rx flag the software crashes at some point, waiting indefinitely in the while loop in the uart_nrfx_uarte.c file, in the uarte_pm_suspend() function.

If we use the disable-rx flag, the code is not stuck anymore in the following while loop but the current consumption is really high.

while (!nrf_uarte_event_check(uarte, NRF_UARTE_EVENT_RXTO)) {
	/* Busy wait for event to register */
	Z_SPIN_DELAY(2);
}

static void uarte_pm_suspend(const struct device *dev)
{
	NRF_UARTE_Type *uarte = get_uarte_instance(dev);
	const struct uarte_nrfx_config *cfg = dev->config;
	struct uarte_nrfx_data *data = dev->data;

	(void)data;
#ifdef UARTE_ANY_ASYNC
	if (data->async) {
		/* Entering inactive state requires device to be no
		 * active asynchronous calls.
		 */
		__ASSERT_NO_MSG(!data->async->rx.enabled);
		__ASSERT_NO_MSG(!data->async->tx.len);
		if (IS_ENABLED(CONFIG_PM_DEVICE_RUNTIME)) {
			/* If runtime PM is enabled then reference counting ensures that
			 * suspend will not occur when TX is active.
			 */
			__ASSERT_NO_MSG(nrf_uarte_event_check(uarte, NRF_UARTE_EVENT_TXSTOPPED));
		} else {
			wait_for_tx_stopped(dev);
		}

#if !defined(CONFIG_UART_NRFX_UARTE_ENHANCED_RX)
		if (data->async && HW_RX_COUNTING_ENABLED(cfg)) {
			nrfx_timer_disable(&cfg->timer);
			/* Timer/counter value is reset when disabled. */
			data->async->rx.total_byte_cnt = 0;
			data->async->rx.total_user_byte_cnt = 0;
		}
#endif
	} else if (IS_ENABLED(UARTE_ANY_NONE_ASYNC))
#endif
	{
		if (nrf_uarte_event_check(uarte, NRF_UARTE_EVENT_RXSTARTED)) {
#if defined(UARTE_INTERRUPT_DRIVEN) && defined(CONFIG_PM_DEVICE)
			if (data->int_driven) {
				data->int_driven->rx_irq_enabled =
					nrf_uarte_int_enable_check(uarte, NRF_UARTE_INT_ENDRX_MASK);
				if (data->int_driven->rx_irq_enabled) {
					nrf_uarte_int_disable(uarte, NRF_UARTE_INT_ENDRX_MASK);
				}
			}
#endif
			nrf_uarte_task_trigger(uarte, NRF_UARTE_TASK_STOPRX);
			while (!nrf_uarte_event_check(uarte, NRF_UARTE_EVENT_RXTO)) {
				/* Busy wait for event to register */
				Z_SPIN_DELAY(2);
			}
			nrf_uarte_event_clear(uarte, NRF_UARTE_EVENT_RXSTARTED);
			nrf_uarte_event_clear(uarte, NRF_UARTE_EVENT_RXTO);
			nrf_uarte_event_clear(uarte, NRF_UARTE_EVENT_ENDRX);
			nrf_uarte_event_clear(uarte, NRF_UARTE_EVENT_ERROR);
		}

		wait_for_tx_stopped(dev);
	}

#ifdef CONFIG_SOC_NRF54H20_GPD
	nrf_gpd_retain_pins_set(cfg->pcfg, true);
#endif

	nrf_uarte_disable(uarte);

	(void)pinctrl_apply_state(cfg->pcfg, PINCTRL_STATE_SLEEP);
}

RE: High Current Consumption when UART is configured with disable-rx flag and zephyr,pm-device-runtime-auto

Susheel Nuguru — Thu, 17 Jul 2025 12:01:08 GMT

It seems like the disable-rx is not doing what we expect it to do.

Without disable-rx, the driver seems to leave the channel running
With disable-rx, the driver never queues RX so I think it never calls the power management plugs to shut down the hardware.

I think the fix is here is to let the driver power off itself and then explicity turn off RX in your firmware. A template code can be like this.

static const struct device *uart0 = DEVICE_DT_GET(DT_NODELABEL(uart0));

void main(void)
{
    ...
    ...
    
    pm_device_runtime_enable(uart0);

    /* 
     * when you want to disable rx path
     */
    uart_rx_disable(uart0);
    pm_device_action_run(uart0, PM_DEVICE_ACTION_SUSPEND);

    ...
    ...
}

leave zephyr,pm-device-runtime-auto; as is in your devicetree