Skip to content

J514s: SEP and Touch ID (T6030) - #282

Open
adammharris wants to merge 3 commits into
omacom:integration/aurorafrom
adammharris:feat/t6030-j514s-touchid-omacom
Open

adammharris wants to merge 3 commits into
omacom:integration/aurorafrom
adammharris:feat/t6030-j514s-touchid-omacom

Conversation

@adammharris

Copy link
Copy Markdown

Touch ID on the 14" M3 Pro MacBook Pro (J514s, T6030).

Changes

  • t6030.dtsi: adds the SEP, its DART and mailbox, and spi2 with the Mesa sensor child, all disabled. The SEP and its DART sit at the same addresses as on T8122, with the same BIT(40) DMA window (vm-base 0x10000004000, vm-size 0xffff0000). The mailbox uses AIC 366–369, the DART AIC 372, and spi2 is at 0x289108000 on AIC 876.
  • t6030-j514s.dts: enables the mailbox, spi2 and the sensor. Power is NUB GPIO 33, active high. As on J613, the data-ready line (AP GPIO 200) is left out and the driver polls. The calibration comes from the Mac's own iBoot system container as apple/mesacal-j514s.bin.
  • soc: apple: sep: adds a T6030 profile, which is T8122 with J514s's spi2 base. The J514s sensor is the same 0x3352 part, in SPI mode 1, with the variant-5 key store and xART guard level 1 from the first boot. Only apple,t6030 + apple,j514s is matched. J516s shares the SoC, but its ADT hasn't been read, so it stays off.
  • tools/aurora-sep/tests/test_t6030_sep.py: checks the compiled J514s tree against the ADT values, checks that J516s leaves the SEP and sensor off, and checks the profile match.

The values come from the J514s ADT (ioreg -p IODeviceTree, system firmware 27.0) with the /arm-io base of 0x210000000 added. The mailbox interrupts follow the ascending order the T6030 SIO mailbox already uses for its ADT list.

Testing

J514s, system firmware 27.0, with macOS on the same disk.

  • Read-only first boot (xart_writes=0 provision_keybag=0): the profile T6030/J514s is selected, the SEP attaches warm and advertises 12 endpoints, and the key store opens. /dev/sep-bio is published and the sensor's SPI driver binds at 8 MHz, mode 1. Nothing is written.
  • First boot with writes: the identity keybag is provisioned. The guard runs at level 1, protects all 10 existing macOS session records, and refuses nothing.
  • Sensor bring-up: the identifier appears 18 ms after power-on, then REGISTER_SERIAL, SESSION_SHARE and SESSION_COMMIT complete.
  • Enrolment and matching: fprintd-enroll and fprintd-verify work with Aurora's libfprint.
  • Persistence: a match still works after a reboot and after suspend and resume.
  • macOS: Touch ID still works in macOS afterwards.
  • Tests: test_t6030_sep.py and test_t8122_sep.py pass with the kernel's dtc. t6030-j514s.dtb and t6030-j516s.dtb build with W=1 and no new warnings.

The hardware test ran on this change applied to an omacom-based 7.2.11 J514s tree. It is the same diff apart from the profile's doc comment.

Not tested:

  • J516s, since there's no ADT for it.
  • The data-ready interrupt path: GPIO 200 is described in the ADT, but left out here.

The same change for the 7.3 aurora-wip tree is in aurora-silicon/linux#581.

🤖 Generated with Claude Code

adammharris and others added 3 commits October 29, 2026 14:09
Add the SEP, its DART and mailbox, and spi2 with the Mesa sensor child, as
the J514s ADT (system firmware 27.0) records them. The SEP and its DART
sit at the same addresses as on T8122, with the same BIT(40) DMA window
(vm-base 0x10000004000, vm-size 0xffff0000); the mailbox takes AIC 366-369
and the DART AIC 372. spi2 is at 0x289108000 on AIC 876.

Everything stays disabled: apple_sep enables the SEP and its DART when it
loads, and boards enable the mailbox, the bus and the sensor.

Assisted-by: LLM
Signed-off-by: Adam Harris <amh421@icloud.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Enable the SEP mailbox, spi2 and the Mesa sensor (0x3352) on the 14" M3
Pro. Per the J514s ADT, the sensor is powered from NUB GPIO 33, active
high. As on J613, its data-ready line (AP GPIO 200) is left out and the
driver polls. The calibration comes from this Mac's own iBoot system
container as apple/mesacal-j514s.bin.

J516s shares the SoC, but its sensor wiring is unchecked, so it stays
off.

Assisted-by: LLM
Signed-off-by: Adam Harris <amh421@icloud.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The J514s SEP is pre-booted by iBoot and speaks the variant-5 key store,
and its sensor is the same 0x3352 part T8122 carries, in SPI mode 1. So
J514s takes the T8122 profile with its own spi2 base, including the wide
DMA mask and xART guard level 1 from the first boot. Only J514s is
matched; the other T6030 Mac (J516s) has not had its ADT read.

Add a test that checks the J514s device tree against the ADT values and
that J516s leaves the SEP and the sensor off.

Tested on J514s, system firmware 27.0, with macOS on the same disk:
- the SEP attaches warm and advertises 12 endpoints
- the keybag is provisioned; the guard protects all 10 existing macOS
  session records and has refused nothing
- the sensor answers 18 ms after power-on and registers its serial
- enrolment and a match work, and a match still works after a reboot
  and after suspend
- macOS Touch ID still works afterwards

Assisted-by: LLM
Signed-off-by: Adam Harris <amh421@icloud.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@adammharris
adammharris marked this pull request as ready for review October 29, 2026 20:11
@c4software

c4software commented Nov 3, 2026 •

Copy link
Copy Markdown

Hi, I'm running a J514s (14" M3 Pro) on Omarchy 4.5.0rc3, and Touch ID isn't detected on the current packages. As expected, the tree has no SEP or Mesa node, and there's no T6030 profile yet.

Is anything blocking this PR? For example, a review concern, or more hardware results needed before merging? I can test on my J514s if that would help.

Also, once this lands, omarchy-mac's touchid-eligibility will probably need to accept apple,t6030 + apple,j514s as well. It currently returns unsupported:board for anything that isn't T8112, T6020/T6021, T8140 or T8122 J613/J615.

My setup
Machine apple,j514s / apple,t6030 (MacBook Pro 14", M3 Pro, Nov 2023), macOS on the same disk
System firmware (iBoot1) mBoot-20457.41.3 (asahi,system-fw-version reads unknown)
OS firmware stub 14.7 (iBoot2 iBoot-10151.140.19.700.2)
m1n1 stage1 v1.6.1-dirty, stage2 bc79acc4-dirty (m1n1-aurora 1.6.1.aurora22-1)
U-Boot uboot-aurora 2026.07.aurora6-1
Kernel linux-aurora 7.2.11.aurora14-1 (7.2.11-14-1-ARCH)
Omarchy omarchy 4.5.0rc3-1, omarchy-mac 0.2.3-2, omarchy-aurora-firmware 20261014-7
Touch ID state touchid-eligibility → none (no fingerprint@ node); never enabled, no keybag on this install

Drafted with an AI assistant (Claude Code); I reviewed it before posting.

@malik-na

malik-na commented Nov 4, 2026

Copy link
Copy Markdown
Member

Hi @adammharris, a question on the Secure Enclave bring-up for the M3 Max, since #282 is the template I'm following.

I read the J516C (MacBook Pro 16" M3 Max, T6031) hardware description from the Mac, read-only, and wrote the SEP, mailbox, DART, spi2 and sensor nodes for it, built and test-booted with the driver not loaded. Two values I'd like your eyes on before anyone loads it:

  1. The SEP's DART window. On the J516C the ADT gives start 0x100_00004000 and size 0x3ff00000. Your T6030 and the M3 Air nodes use size 0xffff0000. Does the driver depend on the window size, or only on the base address?
  2. The sensor on spi2. The J514s uses SPI mode 1 and part 0x3352. On the J516C the ADT's SPI config word is 0x08010100 (the boot flash's is 0x08010000), which hints at a mode bit, but I haven't read the part id. Did you confirm mode and part on the J514s from the ADT or from a running sensor?

Everything else (mailbox address and interrupts, power GPIO) I inferred from the M3 Air layout and marked as unverified. Happy to share the diff.

@adammharris

Copy link
Copy Markdown
Author

@malik-na Thanks for building on this.

1. The window size matters. The SEP driver doesn't read it, but apple-dart does: it sets the aperture end from apple,dma-range, and iommu-dma allocates downward from there. On my J514s the registered shmem IOVA is 0x100fff80000, right at the top of the 0xffff0000 window. So use the J516C's own ADT value rather than mine. Your 0x3ff00000 matches t6040.dtsi, so it's worth double checking that it came from the J516C's dart-sep node.
  1. Part 0x3352 came from the ADT only (sensor-id). The driver checks it against a list but never logs it, so a running sensor hasn't confirmed it. SPI mode 1 came from the T8122 profile and is proven by enrol and match working, including after reboot and suspend. I never tried mode 2. My mesa config word is also 0x08010100 and spinor is 0x08010000, so reading that bit as the mode bit fits, but it's an inference. The J516C's sensor-id should tell you whether T8122 or T6040 is the better base.

Good luck with the M3 Max work!

@c4software

Copy link
Copy Markdown

Tested this on a second J514s (14" M3 Pro), Omarchy 4.5.0, macOS on the same disk. It works here.

Build: linux-aurora 7.2.11.aurora14 (4fdd0fc) with this PR applied as a patch (applies cleanly), packaged with the omarchy-pkgs PKGBUILD. test_t6030_sep.py passes with the kernel's dtc.

  • Read-only first load (xart_writes=0 provision_keybag=0): profile T6030/J514s, warm attach, 12 endpoints, key store open (variant5), /dev/sep-bio published. Opening it binds the sensor at 8 MHz, mode 1; activation stops with ENOENT (no keybag). Nothing written.
  • With writes: keybag provisioned, guard level 1 protects the 10 existing session records, 0 refusals. fprintd enrolment and matching work with Omarchy's libfprint-git.
  • Persistence: enrolment survived reboot after a reboot and after booting macOS in between; a match still works after suspend and resume.
  • macOS: Touch ID still works there afterwards.

iBoot1 here is mBoot-20457.41.3 (asahi,system-fw-version reads unknown).

One thing outside this PR: omarchy-mac's touchid-eligibility returns unsupported:board for apple,t6030 + apple,j514s, so I had to patch its allow-list locally to get through the Omarchy fingerprint setup.

Drafted with an AI assistant (Claude Code); I reviewed it before posting.

@malik-na

Copy link
Copy Markdown
Member

Thanks a lot for the thorough J514s test, this is really useful. Enrol, match, reboot, suspend and macOS Touch ID afterwards all working is exactly the coverage this needed.

One small thing I'd like to add before I'm comfortable with it: you mention you did the read-only first load (xart_writes=0 provision_keybag=0), but I can't see the log from it anywhere in the thread. Could you paste the relevant bits from that boot? Something like:

journalctl -k -b | grep -i -E 'img4|xart|sep'

I'm mainly after the "IMG4 acknowledged" line and any "xART refused write" lines (there shouldn't be any on a read-only boot, and none in the guarded one either, going by what you said about 0 refusals). If you still have the journal from that first boot, that's ideal; if not and it's no trouble to redo a read-only boot from a fresh state, that works too, but don't wipe your enrolment for it.

Also noted on the touchid-eligibility allow-list for apple,t6030 + apple,j514s. That lives outside this PR, I'll sort it separately.

Thanks again for taking the time.

@c4software

Copy link
Copy Markdown

Here is the read-only first load, from the journal of that boot (still on disk, so nothing was redone and the enrolment was not touched). The driver was loaded by hand with modprobe apple-sep xart_writes=0 provision_keybag=0 at 21:21:19; /dev/sep-bio was opened once at 21:22:36.

journalctl -k -b <that boot> | grep -i -E 'img4|xart|sep' (48 lines, hostname shortened)
Oct 18 18:25:30 archlinux kernel: OF: reserved mem: 0x0000010002c84000..0x000001000322ffff (5808 KiB) map non-reusable sep-firmware
Oct 18 18:25:30 archlinux systemd[1]: TPM PCR OS Separator skipped, unmet condition check ConditionSecurity=measured-os
Oct 18 18:25:30 archlinux systemd[1]: TPM PCR NvPCR Initialization Separator skipped, unmet condition check ConditionSecurity=measured-os
Nov 10 21:19:49 macbook systemd[1]: TPM PCR OS Separator skipped, unmet condition check ConditionSecurity=measured-os
Nov 10 21:19:49 macbook systemd[1]: TPM PCR NvPCR Initialization Separator skipped, unmet condition check ConditionPathExists=/etc/initrd-release
Nov 10 21:21:19 macbook kernel: apple_sep: apple_sep: SEP DART state: enabled=false, apple,dma-offset present=true, apple,dma-range present=true
Nov 10 21:21:19 macbook kernel: apple_sep: apple_sep: SEP DART changeset applied (offset BIT(40), range 0..4 GiB, status okay)
Nov 10 21:21:19 macbook kernel: platform 29e400000.sep: Adding to iommu group 19
Nov 10 21:21:19 macbook kernel: apple_sep: apple_sep: SEP node enabled; platform device should now exist
Nov 10 21:21:19 macbook kernel: apple_sep 29e400000.sep: SEP platform profile: T6030/J514s
Nov 10 21:21:19 macbook kernel: apple_sep 29e400000.sep: xART: APFS-resolved .gl extent (base 0x4d4000); 170 slots, 12 live records, max revision 11007, 0 malformed, 0 duplicate, 0 repaired; writes disabled
Nov 10 21:21:19 macbook kernel: apple_sep: created a new host-state store
Nov 10 21:21:19 macbook kernel: apple_sep 29e400000.sep: trusted-keys: registering "trusted" key type backed by the SEP ref-key seal
Nov 10 21:21:19 macbook kernel: trusted_key: trusted_key: source 'applesep' registered
Nov 10 21:21:19 macbook kernel: apple_sep 29e400000.sep: discover: endpoint 0x14 (type 0, msg0 0x68696265140000fd); 1 known
Nov 10 21:21:19 macbook kernel: apple_sep 29e400000.sep: discover: endpoint 0x14 (type 1, msg0 0x01010101140100fd); 1 known
Nov 10 21:21:19 macbook kernel: apple_sep 29e400000.sep: discover: endpoint 0x18 (type 0, msg0 0x73746163180000fd); 2 known
Nov 10 21:21:19 macbook kernel: apple_sep 29e400000.sep: discover: endpoint 0x18 (type 1, msg0 0x02020202180100fd); 2 known
Nov 10 21:21:19 macbook kernel: apple_sep 29e400000.sep: discover: endpoint 0x00 (type 0, msg0 0x636e746c000000fd); 3 known
Nov 10 21:21:19 macbook kernel: apple_sep 29e400000.sep: discover: endpoint 0x00 (type 1, msg0 0x00000000000100fd); 3 known
Nov 10 21:21:19 macbook kernel: apple_sep 29e400000.sep: discover: endpoint 0x10 (type 0, msg0 0x78617273100000fd); 4 known
Nov 10 21:21:19 macbook kernel: apple_sep 29e400000.sep: discover: endpoint 0x10 (type 1, msg0 0x02020202100100fd); 4 known
Nov 10 21:21:19 macbook kernel: apple_sep 29e400000.sep: discover: endpoint 0x13 (type 0, msg0 0x7861726d130000fd); 5 known
Nov 10 21:21:19 macbook kernel: apple_sep 29e400000.sep: discover: endpoint 0x13 (type 1, msg0 0x02020202130100fd); 5 known
Nov 10 21:21:19 macbook kernel: apple_sep 29e400000.sep: discover: endpoint 0x15 (type 0, msg0 0x706e6f6e150000fd); 6 known
Nov 10 21:21:19 macbook kernel: apple_sep 29e400000.sep: discover: endpoint 0x15 (type 1, msg0 0x05050707150100fd); 6 known
Nov 10 21:21:19 macbook kernel: apple_sep 29e400000.sep: discover: endpoint 0x0e (type 0, msg0 0x686463700e0000fd); 7 known
Nov 10 21:21:19 macbook kernel: apple_sep 29e400000.sep: discover: endpoint 0x0e (type 1, msg0 0x010101010e0100fd); 7 known
Nov 10 21:21:20 macbook kernel: apple_sep 29e400000.sep: attach: 7 endpoints advertised in 18 messages
Nov 10 21:21:20 macbook kernel: apple_sep 29e400000.sep: xART: using /chosen/apfs-preboot-uuid
Nov 10 21:21:22 macbook kernel: apple_sep 29e400000.sep: discover: endpoint 0x17 (type 0, msg0 0x736b646c170000fd); 8 known
Nov 10 21:21:22 macbook kernel: apple_sep 29e400000.sep: discover: endpoint 0x17 (type 1, msg0 0x01010101170100fd); 8 known
Nov 10 21:21:22 macbook kernel: apple_sep 29e400000.sep: discover: endpoint 0x0c (type 0, msg0 0x737365200c0000fd); 9 known
Nov 10 21:21:22 macbook kernel: apple_sep 29e400000.sep: discover: endpoint 0x0c (type 1, msg0 0x010101010c0100fd); 9 known
Nov 10 21:21:22 macbook kernel: apple_sep 29e400000.sep: discover: endpoint 0x08 (type 0, msg0 0x7362696f080000fd); 10 known
Nov 10 21:21:22 macbook kernel: apple_sep 29e400000.sep: discover: endpoint 0x08 (type 1, msg0 0x01010101080100fd); 10 known
Nov 10 21:21:22 macbook kernel: apple_sep 29e400000.sep: discover: endpoint 0x0a (type 0, msg0 0x736372640a0000fd); 11 known
Nov 10 21:21:22 macbook kernel: apple_sep 29e400000.sep: discover: endpoint 0x0a (type 1, msg0 0x010101010a0100fd); 11 known
Nov 10 21:21:22 macbook kernel: apple_sep 29e400000.sep: discover: endpoint 0x12 (type 0, msg0 0x736b7320120000fd); 12 known
Nov 10 21:21:22 macbook kernel: apple_sep 29e400000.sep: discover: endpoint 0x12 (type 1, msg0 0x02010201120100fd); 12 known
Nov 10 21:21:23 macbook kernel: apple_sep 29e400000.sep: hwrng: registered after ready-phase survey (attempt 1)
Nov 10 21:22:36 macbook kernel: apple-mesa spi0.0: sep sensor: CS timing 20 ns programmed in hardware
Nov 10 21:22:36 macbook kernel: apple-mesa spi0.0: sep sensor: power line from the device node, driven low
Nov 10 21:22:36 macbook kernel: apple-mesa spi0.0: sep sensor: bound, 8000000 Hz, mode 1 (CPOL=0 CPHA=1)
Nov 10 21:22:36 macbook kernel: apple_sep: apple_sep: sensor node present in the device tree; enabling it and its SPI bus
Nov 10 21:22:36 macbook kernel: apple_sep 29e400000.sep: sensor: power via the sensor node's own gpios property
Nov 10 21:22:36 macbook kernel: apple_sep 29e400000.sep: Touch ID: no persisted identity keybag exists
Nov 10 21:22:36 macbook kernel: apple_sep 29e400000.sep: Touch ID activation failed: ENOENT; refusing retries this boot because a partial keybag load is not safely repeatable

On the two lines you asked about:

  • "IMG4 acknowledged": there is none, in this boot or in any of the later ones. In sep.rs that message is printed from on_boot(), the cold-boot handshake. This Mac attaches warm (diag/boot reads warm, iBoot has already started the SEP), so as far as I can tell that path never runs here.
  • xART refusals: none in any of the four boots on the patched kernel. The read-only boot ends its xART line with writes disabled. The only "refusing" line is the expected Touch ID activation failed: ENOENT; refusing retries this boot, since no keybag existed and provisioning was off.

For the first boot with writes, the xART lines are:

Nov 10 21:25:37 macbook kernel: apple_sep: xART guard level 1: 10 session records exist, 0 created by Linux; the other 10 are protected
Nov 10 21:25:37 macbook kernel: apple_sep 29e400000.sep: xART: APFS-resolved .gl extent (base 0x4d4000); 170 slots, 12 live records, max revision 11007, 0 malformed, 0 duplicate, 0 repaired; writes ENABLED
Nov 10 21:25:38 macbook kernel: apple_sep 29e400000.sep: xART: using /chosen/apfs-preboot-uuid
Nov 10 21:25:41 macbook kernel: apple_sep: xART guard: allowed the enclave to commit an existing kind-4 locker during this install's first keybag creation

Later boots show the same guard line, 12 live records each time, and max revision 11019, then 11062 after macOS had been booted in between.

One correction to my earlier comment. I wrote that a match still works after suspend and resume. Going back through the journal for this, the suspend never actually happened: apple-dcp aborted it both times.

PM: suspend entry (s2idle)
apple-dcp 2d6c00000.dcp: refusing system sleep: a display link is up
PM: Some devices failed to suspend, or early wake event detected
PM: suspend exit

So suspend/resume is untested on my side; please don't count it. Reboot persistence (enrolment survived reboot, twice, once with macOS booted in between) and macOS Touch ID afterwards stand. The Mac is back on the stock 7.2.11.aurora14-1 kernel now; I can reinstall the patched one and redo the suspend test properly if that would help.

Drafted with an AI assistant (Claude Code); I reviewed it before posting.

@c4software

Copy link
Copy Markdown

A note on the suspend correction above: from the user side the Mac did look like it went to sleep (that is why I first reported the test as passing), while the journal shows apple-dcp refusing the transition both times. So I can't tell whether what I saw was only the display going off, and whether the refused suspend is related to this PR or not. Either way the fingerprint match afterwards doesn't prove a resume path.

Drafted with an AI assistant (Claude Code); I reviewed it before posting.

@malik-na

Copy link
Copy Markdown
Member

Thanks for the log and for the correction.

Yes, a suspend retest would be a nice extra, but only if it's no trouble: adammharris already saw a match work after suspend on his J514s, so this isn't blocking anything.

On the refusal: a display link is up comes from iomfb_v14_7_external_busy() in drivers/gpu/drm/apple/iomfb_v14_7.c. 2d6c00000.dcp is the USB-C display processor, and it refuses sleep on purpose while its firmware holds a link or a powered display (an attached display doesn't come back after resume). This PR doesn't touch that driver, so the refusal isn't caused by it.

Two questions, if you can: was a display, dock or USB-C display cable plugged in during those two attempts? If you retest, please do it with nothing attached, and grab:

journalctl -k -b | grep -i -E 'dcp|sep|suspend|PM:'

plus whether a fingerprint match still works after a real resume. If it still refuses with nothing attached, that's worth its own issue. Don't wipe your enrolment for it.

@c4software

Copy link
Copy Markdown

Thanks for tracking that down. Yes: during those two attempts a display was plugged in over a USB-C cable, so the refusal matches what you describe and is unrelated to this PR.

I'll redo the suspend test with nothing attached when I get a chance (the Mac is back on the stock kernel for now, so it means reinstalling the patched one; the existing enrolment stays), and post the dcp|sep|suspend|PM: log along with whether a match works after a real resume.

Drafted with an AI assistant (Claude Code); I reviewed it before posting.

@c4software

Copy link
Copy Markdown

Suspend retest done, this time with nothing attached (no USB-C display, lid close/open).

Setup: same J514s, linux-aurora 7.2.11.aurora14 + this series, same keybag as on Nov 10 (LOAD_KEYBAG status 0, no new keybag provisioned).

One caveat: I could not keep the original enrolment. My own cleanup on Nov 10 ran fprintd-delete before I went back to the stock kernel, so the catacombs restored fine but empty (identity count 0). I enrolled the finger again under the existing keybag, then ran the test.

Result:

  • PM: suspend entry (s2idle) at 20:10:03, PM: suspend exit at 20:14:28, so 4 min 25 s asleep. suspend_stats: success 1, fail 0. No refusing system sleep from apple-dcp this time, which confirms the earlier refusal came from the attached display and not from this series.
  • fprintd-verify matched before suspend and matched again 16 s after resume (Verify result: verify-match (done)), with no module reload and no re-enrolment in between.
  • After resume: identity count 1, touchid: ready, sensor: online, keystore: open, xart_guard_refusals: 0.

Kernel log around the resume:

PM: suspend entry (s2idle)
PM: suspend exit
apple-dcp 2d2c00000.dcp: HDMI: setting up the output again (after system sleep)
apple_sep 29e400000.sep: sbio: registering sensor at bring-up stage 2
apple_sep 29e400000.sep: sbio: identity count 1 before CLEAR_STATE for sensor re-registration
apple_sep 29e400000.sep: sbio: identity count 1 after CLEAR_STATE for sensor re-registration
apple_sep 29e400000.sep: sbio: identity count 1 after sensor serial registration
apple_sep 29e400000.sep: sensor: no data-ready interrupt (describe it in DT); capture falls back to SPI polling

So suspend/resume is now tested and working here. Next I'll build the 7.3 branch from aurora-silicon/linux#1691 and report there.

Drafted with an AI assistant (Claude Code); I reviewed it before posting.

@c4software

Copy link
Copy Markdown

Retest on the current series, on top of integration/aurora bc2420e and merged with #481/#488/#489/#497/#484/#283.

  • Same keybag and enrolment as my earlier reports. No new keybag, no re-enrolment.
  • Set up through omarchy-mac's touchid-enable, with touchid-eligibility patched for apple,t6030 + apple,j514s, and libfprint-git 1.94.100 with the aurora v4/v5 patches.
  • Driver attributes: touchid=ready sensor_attach=attached restore=restored, and /run/omarchy-mac/touchid reads ready.
  • fprintd-verify: match OK, with the existing enrolment.
  • The only related kernel line is the expected one: sensor: no data-ready interrupt (describe it in DT); capture falls back to SPI polling.
  • Not retested on this build: verification after suspend (it passed on aurora14 + this PR, see above).
Test setup

Testing and write-up assisted by Claude Code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants