05:31 <austriancoder> am64x: is there a sane way to define define PADMMR_MCU_LOCK1_KICK0 register value via dts?

05:46 <austriancoder> it is needed to get mcu_spi0 functional

05:54 <austriancoder> I added a pinctr lhttps://dpaste.org/7DYq for mcu and using it in my own board dts - but I am still unsure where I need to write the kick register

17:53 <NishanthMenon_> austriancoder, TI IT firewalls dont let me use dpaste. padconf driver does'nt understand lock-unlock logic (which was primarily created for safety applications). unfortunately, that means, we'd have to unlock from .c (unless we write a brand new driver -> prefer not to do it unless we intend to protect every reg pad reg operation with lock/unlock

17:56 <NishanthMenon_> arch/arm/mach-k3/am642_init.c (ctrl_mmr_unlock) -> interesting it just unlocks the main pad regions and does'nt touch the mcu regions.. but should be trivial to add it for MCU_PADCFG_CTRL0_CFG0 0x004080000 (https://www.ti.com/lit/ug/spruim2b/spruim2b.pdf)?

17:57 <NishanthMenon_> except unless there is clocking dependencies on mcu domain.. that I dont remember..