[brkosebay]

Problem

The A9 AOP driver on main reads apple,aop-target, apple,chip-id and apple,chip-revision from the device tree, and the motion sensor drivers read their factory calibration from properties of the same kind. iBoot puts these values in the ADT, but nothing on main copies them into the FDT. Going by the driver's probe, the A9 AOP (and with it the accelerometer, gyroscope and pressure sensor) cannot start without them. This is read from the code; main's AOP path has not been run on an A9 without this patch.

Changes

One m1n1 patch, 0021-kboot-Pass-the-A9-AOP-s-boot-arguments-and-sensor-ca.patch:

• copies aop-target (from iop-aop-nub), chip-id (from /chosen) and chip-revision (from /arm-io) into the AOP node as apple,… properties;
• copies each motion sensor's factory calibration from its ADT node below iop-aop-nub into the sensor child node of the same name, with an apple, prefix. Calibration that iBoot left as an unresolved syscfg/ reference is skipped.

It is the m1n1 patch from #101, unchanged. #101 landed only the kernel side.

Testing

• The m1n1 series on this branch (hoolock, then orchard 0001–0014 plus this patch) applies to the pinned m1n1 c9ef56f.
• The same patch was built into the Orchard 0.4 test images that booted on an iPad 5 (J71t), on top of kernel: Retain the tethered warm boot state across kexec #107's PSCI patches 0015–0020, together with kernel: Motion sensors on the A9 and A10 through the Always-On Processor #101's original kernel side. It has not been built or run on its own on main, and not with main's reworked AOP driver.
• Other A9 boards have not been tested.

Numbering

The file keeps the number 0021 that it has in #107, which carries the identical file. Whichever of the two lands first, the other merges cleanly, and the next update of #107 drops its copy. Until #107 lands, 0015–0020 are unused on main; the patches still apply in order.

🤖 Generated with Claude Code