Skip to content

device/husky: SENSORS-PLAN.md, stage 0 - #929

Open
gitColinX wants to merge 1 commit into
derekross:mainfrom
gitColinX:husky-sensors-plan
Open

gitColinX wants to merge 1 commit into
derekross:mainfrom
gitColinX:husky-sensors-plan

Conversation

@gitColinX

Copy link
Copy Markdown
Contributor

The 8 Pro's Sensors row was unassigned and had no plan. This adds one in the cheetah shape and puts my name on the row, as Lef agreed on #1. Documentation only; nothing runs.

Stage 0 (offline, from my own factory image, CP3A.261005.005):

  • The parts, from the AoC's sensor registry:
    • an ICM45631 IMU on i3c0;
    • two MMC5633 magnetometers;
    • an ICP20100 barometer;
    • a TMD3719 for light and proximity;
    • a VD6282 for spectral, flicker and rear light;
    • an MLX90632 IR thermometer.
  • Which registry files apply: /chosen/plat on my phone reads CDT 0x26100, so husky_common.reg plus husky_dvt.reg. That is one read-only sysfs read.
  • The rails, from the stock dtbo: L7S L7S_SENSORS at 1.6 to 1.95 V and L5S L5S_PROX at 2.5 to 3.3 V. Our S2MPG15 driver already has both from the 9a, but pmic-2 is disabled on husky and there is no zuma AoC node.
  • What is missing in the kernel, in the device package (an omamobile-aoc.service alias, a wait for the USF node, registry staging in extract-vendor-firmware) and in omamobile-sensors (the ICM45631's gyro rates, the 60 Hz display state sent to the TMD3719, and the f2fs persist).

Two decisions to ask for before any registry load:

  • The stock registry hands the AoC the FTM5 touch controller, with gestures and a touch bus negotiator that Linux does not have.
  • Whether the sensor rails are cycled before the first load. On the 7 Pro, rails left on across a warm reboot hid the I3C IMU (C6d).

Stages 2 to 6 wait for Lef's zuma AoC series. No Google file is in the repository: the plan names parts, addresses and file names only.

tools/pr-check origin/main: all ok.

The 8 Pro's Sensors row was unassigned and had no plan. This adds one
in the cheetah shape, agreed with Lef on derekross#1, and takes the row.

Stage 0 is offline: the parts, buses and interrupts from the AoC's
sensor registry in the owner's own vendor image, the stock rails from
the dtbo, and the one read-only sysfs read that picks the registry
files (CDT 0x26100 on Colin's phone). It lists what the kernel, the
device package and omamobile-sensors still need, two decisions to ask
for before any registry load (the touch controller the registry hands
to the AoC, and the rails), and gated stages that wait for Lef's zuma
AoC series. No Google file is in the repository.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.

1 participant