Unable to disable GPIOTE for nRF Connect SDK 2.6.1

[Christopher]

Hi, 

Recently I upgraded to nRF Connect SDK 2.6.1 and I was required to enable the GPIOTE in order to build properly. Doing this has significantly increased (nearly doubled) the total current consumption at runtime. How can I disable this peripheral now? I am unable to do so now using the overlay file.

Old: 

&gpiote {
    status = "disabled";
};

New:

&gpiote {
    status = "okay";
};

Thank you,

[Susheel Nuguru]

You need to use PORT events instead of high precision events when using GPIOTE with lower power consumption. Can you try if the suggestion mentioned here works with nRF53 aswell?

[Christopher]

Sorry, I would like to disable the GPIOTE peripheral. I am unable to build the code unless it is enabled, but that is not what we desire. 

Thank you 

[Susheel Nuguru]

It should have been disabled when you disable here. Can you check in your build\zephyr\zephyr.dts file to see if this is disabled or if something else kept it enabled? If you can post your zephyr.dts file here, I can take a look.

[Christopher]

When I build with it set to "disabled", I get the following error. The zephyr.dts has this also for the two GPIOS. How can I remove the need for the <&gpiote> in the definition for the gpios?

C:/ncs/v2.7.0/zephyr/include/zephyr/toolchain/gcc.h:87:36: error: static assertion failed: "Please enable GPIOTE instance for used GPIO port!"

			gpio0: gpio@842500 {
				compatible = "nordic,nrf-gpio";
				gpio-controller;
				reg = < 0x842500 0x300 >;
				#gpio-cells = < 0x2 >;
				status = "okay";
				port = < 0x0 >;
				gpiote-instance = < &gpiote >;
				phandle = < 0x6 >;
			};
			gpio1: gpio@842800 {
				compatible = "nordic,nrf-gpio";
				gpio-controller;
				reg = < 0x842800 0x300 >;
				#gpio-cells = < 0x2 >;
				ngpios = < 0x10 >;
				status = "okay";
				port = < 0x1 >;
				gpiote-instance = < &gpiote >;
				phandle = < 0x9 >;
			};

[Christopher]

I added this to my overlay file and it appears to work now. I am going to check the power output to be sure.

&gpio0 {
	/delete-property/ gpiote-instance;
};

&gpio1 {
	/delete-property/ gpiote-instance;
};