Re: [PATCH v2 2/3] nvmem: Add read-only SpacemiT K3 eFuse support
From: Philipp Zabel
Date: Mon Nov 16 2026 - 06:54:53 EST
On Mo, 2026-11-16 at 15:54 +0800, Jiayu Du wrote:
> Add read-only NVMEM access to bank 0 and bank 7 of the SpacemiT K3 eFuse
> controller. These banks contain temperature calibration parameters and
> other configuration data.
>
> Keep the root key and SSK registers outside the exposed bank ranges.
>
> FUSE_READY reports completion of a software-triggered reload. Trigger a
> reload through GEU_CONFIG bit 22 with a 1 us reset pulse, then poll
> FUSE_READY at a 1 us interval with a 10 ms timeout before taking the
> snapshot. Fail probe if the reload times out.
>
> Snapshot the shadow registers with aligned 32-bit reads and expose the
> data in little-endian order at controller-relative offsets. Serve reads
> from the snapshot and use keepouts for the remaining register ranges.
>
> Enable the AES_WTM clock only while accessing the hardware. Leave its
> shared reset deasserted on teardown because WTM_RST resets the entire GEU.
I don't understand this, possibly because I don't know what GEU is.
What is this reset shared with, and why exactly does the reset need to
stay deasserted?
regards
Philipp