This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

PROCESSOR-SDK-J721S2: Sysconfig tool regarding pinmuxing wakeup domain for devicetrees

Part Number: PROCESSOR-SDK-J721S2
Other Parts Discussed in Thread: SYSCONFIG

Hello,

the wkup_pmx0 node in the devicetree file k3-j721s2-mcu-wakeup.dtsi got split up into 4 different parts because of some non-addressable
regions a while ago.

(see https://lore.kernel.org/linux-arm-kernel/20230602153554.1571128-1-nm@ti.com/)

The devicetree extension of the Sysconfig Tool (as of version  1.18.0+3266)
already puts the muxing into the right wkup_pmx node but the offset is not updated yet:

For example Pin C27 used as WKUP_GPIO0_3

/* This file was auto-generated by TI PinMux on 6.12.2023 at 14:44:38. */
/* This file should only be used as a reference. Some pins/peripherals, */
/* depending on your use case, may need additional configuration. */

&wkup_pmx0 {
	mywkup_gpio1_pins_default: mywkup_gpio1-default-pins {
		pinctrl-single,pins = <
		>;
	};

};
&wkup_pmx1 {
	mywkup_gpio1_pins_default: mywkup_gpio1-default-pins {
		pinctrl-single,pins = <
		>;
	};

};
&wkup_pmx2 {
	mywkup_gpio1_pins_default: mywkup_gpio1-default-pins {
		pinctrl-single,pins = <
			J721S2_WKUP_IOPAD(0x0cc, PIN_INPUT, 7) /* (C27) WKUP_GPIO0_3 */
		>;
	};

};
&wkup_pmx3 {
	mywkup_gpio1_pins_default: mywkup_gpio1-default-pins {
		pinctrl-single,pins = <
		>;
	};

};

However the correct offset is

J721S2_WKUP_IOPAD(0x064, PIN_OUTPUT, 7) /* (C27) WKUP_GPIO0_3 */

Can you update the calculation in the Sysconfig tool here please?

Best regards

Dominik