Repository navigation
Conversation
The K116s has the J714s's Mesa sensor: spi2, chip select 0, 8 MHz, sensor-id 0x3356, powered by NUB GPIO 21, data ready on AP GPIO 138 (ADT /arm-io/spi2/mesa). Describe it as on the J714s and take pin 138 out of the reserved ranges. The node is Thomas Glanzmann's, from his K116s notes. Suggested-by: Thomas Glanzmann <thomas@glanzmann.de> Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
Thanks, this is a clean change. The node matches the J714s block, the reserved-range edit opens only pin 138, and the K116s is already in the T6050 SEP profile. So the PR is device tree only. We are also moving the SEP profile choice to the SoC compatible, after which no T6050 machine needs a board admit. Your test list already covers most of the hardware row. To close it, could you add these, at this PR's head:
Pasting the command output is enough. After that we will run no-regression rows on our A18 Pro (Neo) and M4 Pro machines. The change is board-local, so we expect no change there. |
|
Ryan, thanks. Here is the rest of the row. All of it is from a K116s (firmware 27.2) running this commit on 1. Verify after a deep sleep. From the journal of 2026-11-18: six deep-sleep wakes, and the first verify after each one matched.
Over every boot since the node went in, 2. A finger that is not enrolled. and the driver at the same time: 3. Cold boot. The enrolled finger is restored at every boot ("Touch ID: restored 1 enrolled identity/identities; enrolment survived reboot"). |
|
Thanks, that completes the row: first-try matches after six deep-sleep wakes, For reference, the SoC-based SEP profile choice we mentioned is now #2311. Once it lands, the K116s entry in the profile list is no longer needed, and nothing changes for this PR. |
Thomas, this is the node from your K116s notes, unchanged. The K116s has the J714s's Mesa sensor: spi2, chip select 0, 8 MHz, sensor-id 0x3356, power on NUB GPIO 21, data ready on AP GPIO 138 (checked against this machine's ADT). Pin 138 leaves the reserved ranges.
Tested on a K116s (firmware 27.2), on
integration/aurora0abc2f3 plus my K116s series, with your libfprint 1.94.100+aurora13 and fprintd 1.94.5+aurora4 packages:aurora-touchid-setupbuilds both files from the factory records.Not tested: wrong-finger rejection and lockout.