power-domain-gpio is not enabled by default?

[GrantRudd]

Hi There!

I'm new to Zephyr and digging through all the abstractions that are available. I'm currently attempting to set up a motor control subsystem that consists of an H-Bridge and an encoder on a switched power rail. This seems like a prime use case for a power domain. I am using the included power-domain-gpio. I have this added to my H-Bridge driver in the device tree as such (the encoder has not been added to the device tree yet):

	motion_power_domain: power_rail_3v3 {
		compatible = "power-domain-gpio";
		enable-gpios = <&gpio0 15 GPIO_ACTIVE_HIGH>;
		status = "okay";
	};

	motor: motor {
		compatible = "akm,ap1012a";
		pwms = <&pwm0 0 PWM_USEC(25) PWM_POLARITY_NORMAL>,
			   <&pwm0 1 PWM_USEC(25) PWM_POLARITY_NORMAL>;
		pwm-names = "forward","reverse";
		psave-gpios = <&gpio0 31 GPIO_ACTIVE_LOW>;
		power-domain = <&motion_power_domain>;
	};

The device runtime power management works as expected for my motor driver. However, the power domain I have set up initializes to PM_DEVICE_STATE_ACTIVE and does not update with my calls to get and put calls unless I specifically enable the power domain elsewhere:

pm_device_runtime_enable(dev->pm->domain);

Is it expected that the power-domain-gpio requires the user to call pm_device_runtime_enable? I see the other implementations of power domains call this in their init functions. Is there a reason power-domain-gpio is any different?

Thanks!