Repository navigation
docs: husky roadmap and DEVICES row brought up to 2026-11-07 - #472
Conversation
device/husky/ROADMAP.md was frozen at 2026-10-31, when GPU, Bluetooth, haptics, the AoC and the speakers were all 'no', and the husky row in DEVICES.md still had touch and buttons as 'testing' with their PRs in review. Touch and buttons are merged and verified on both phones, so they say works with their notes entries; everything that runs only on a test tree says testing with the PR it waits on; the rows with nothing started say what was read from the stock device tree and that it was not tested. Suspend says it has not been run, with what is known about idle power. NFC moves to testing: on a test kernel the ST54L answers and reads tags through nxp-nci (kernel derekross#208 and derekross#209, drafts). GNSS stays no, with its first steps in review (kernel derekross#210 and derekross#211, drafts). Written from the PR states (checked with gh today), the notes and what ran on a phone (kernel 7.3.0-rc6-omamobile-push1-g50ef3c279021 for the test-tree rows, a later test tree for NFC). Nothing was booted for this change. Signed-off-by: Lef <me@lefteros.com>
|
@Somnius thank you for going through every row. The 8 Pro's page was well out of date, and a single pass with the PR states as of today is very useful. Most of this I'm happy with as it is. One sentence needs to come first, though. The roadmap says your phone now "sets the successful bit with a local unit that is not in any package". Marking slot B is a
Until then, the routine Brett and I described there is the safe one: re-flash a known-good set before the last try. In the roadmap, please replace the sentence with a dated record ("from … to … a local unit marked slot B on this phone; stopped pending #252"). Lines 16 and 55 and the DEVICES Boot cell then agree again. A few wording fixes in the cells:
Thanks again. With those in, this is a good snapshot of where the 8 Pro stands. |
The matrix re-read against what merged and ran on hardware since 2026-11-02: - Pixel 7: Bluetooth and the torch move to testing (kernel #196, #197, #426); fingerprint moves to WIP (kernel #207; the package side, #458, is in review); AVB footers and reboot=warm noted. - Pixel 8a: a new row, from first light and UFS behind the guard (kernel #192, #206; #414). - Pixel 6 Pro: GPU scaling and cooling (kernel #189) and UFS suspend (kernel #188) merged. - Pixel 9a: GPU levels merged through kernel #96; GNSS's moving-car session (#114) and the link driver (kernel #185). - Pixel 7a: Bluetooth's device tree merged (kernel #98). The Pixel 8 Pro's row is left to #472. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…rging wording, NOTES entries
# Conflicts: # docs/DEVICES.md
… slot B Line 55 and the open question now say what you decided on derekross#252: marking is a manual, attended step, and nothing marks slot B on the 8 Pro until the boot LUN guard change and derekross#483 are in. Line 55 also carries the same dated record as line 16 and the DEVICES Boot cell, as you asked. Signed-off-by: Lef <me@lefteros.com>
|
@derekross fixed, in this order. The local unit The other points: Charging now keeps the runs apart: sink at the Type-C 3 A level (input limit 0x13 to 0x77, +0.33 to +0.52 A near full), and about +1.5 A from a 30 W PD charger in a run without the driver, with 1.485 A named as the device-tree cap. AoC links I merged |
|
@Somnius thank you. This is exactly what I hoped for. The record on the local unit is dated and matches what you posted on #252, the roadmap follows the ruling there, the charging cell now says what you measured and what is the device tree's cap, and the two overlay boots have their own notes entry with the kernels and how you got back. The touch and buttons notes saying which unit ran which tag, and that nobody has run the merged kernel yet, is the honest version I wanted. I'll merge #450 first, since the AoC cell now links its plan, and then this one. Two small things, optional, in this PR or a later one:
Thanks again for the careful pass. |
|
@derekross, you said on #472 that power domains need DTZPC handling on gs101. For the modem link test on the 8 Pro (zuma), the first step that touches hardware does the first PHY and controller access on HSI1 with only the PMU isolation bit (0x3ec4 bit 0), no domain or regulator change. Is there a DTZPC or some other gate on zuma I have to handle before that, or anything you'd want me to read first? I won't run it until I hear from you. Also, is the secure ATU call (SMC 0x820020d8) only for gs201, as it looks in the driver? |
…oot cell wording (#488) Two optional points from the review of #472, and the record of slot B on Lef's phone. The roadmap dates the marked state: B stayed marked (0x35 read 06) from the local unit's last write until the first flash after the unit was masked on 2026-11-07, when it read 04. Since then a boot spends one of B's tries (retry count 3 after set_active, 2 after one boot), so the flash-before-the-last-try routine applies. slot-successful:b was not read after those flashes; Lef will add it after the next one. The bit is not cleared by hand. The DEVICES Boot cell says Lef's phone, not this phone. Signed-off-by: Lef <me@lefteros.com>
Times are now Athens (UTC+2) with the key ones in UTC, and the plan says plainly that S3 to S5e ran after my question on derekross#472 (18:04 UTC) and before any answer, in the status and in Current state. Stock references name Google's s5300 tree and branch, with derekross's line numbers marked as his. The hook description says six AP2CP lines (pda_active is left out on purpose) and the two cpif.ko builds are named by sha256, S5a/S5b without the pda_active file and S5c to S5e with it. The NV check is the first gate and the plan says it ran afterwards. The leftovers on the phone are listed (no modem-test.conf; the test cpif.ko only in the test module trees and /root). The overlays and the S5 scripts that ran are in device/husky/overlays and device/husky/bringup, with two comment lines added to each script. Also: the 92 percent and short-run reason for S5d and S5e, Power + Volume Up for a hung kernel, a sentence on the dead-screen kit, and the Expect, rollback and risk lines for S6. Signed-off-by: Lef <me@lefteros.com>
* device/husky: MODEM-PLAN.md, S1 to S5e with steps, stop conditions, dated results and uname -r Signed-off-by: Lef <me@lefteros.com> * device/husky: MODEM-PLAN.md after derekross's review on #514 Times are now Athens (UTC+2) with the key ones in UTC, and the plan says plainly that S3 to S5e ran after my question on #472 (18:04 UTC) and before any answer, in the status and in Current state. Stock references name Google's s5300 tree and branch, with derekross's line numbers marked as his. The hook description says six AP2CP lines (pda_active is left out on purpose) and the two cpif.ko builds are named by sha256, S5a/S5b without the pda_active file and S5c to S5e with it. The NV check is the first gate and the plan says it ran afterwards. The leftovers on the phone are listed (no modem-test.conf; the test cpif.ko only in the test module trees and /root). The overlays and the S5 scripts that ran are in device/husky/overlays and device/husky/bringup, with two comment lines added to each script. Also: the 92 percent and short-run reason for S5d and S5e, Power + Volume Up for a hung kernel, a sentence on the dead-screen kit, and the Expect, rollback and risk lines for S6. Signed-off-by: Lef <me@lefteros.com> --------- Signed-off-by: Lef <me@lefteros.com>
The matrix re-read against what merged and ran on hardware since 2026-11-02: - Pixel 7: Bluetooth and the torch move to testing (kernel derekross#196, derekross#197, derekross#426); fingerprint moves to WIP (kernel derekross#207; the package side, derekross#458, is in review); AVB footers and reboot=warm noted. - Pixel 8a: a new row, from first light and UFS behind the guard (kernel derekross#192, derekross#206; derekross#414). - Pixel 6 Pro: GPU scaling and cooling (kernel derekross#189) and UFS suspend (kernel derekross#188) merged. - Pixel 9a: GPU levels merged through kernel derekross#96; GNSS's moving-car session (derekross#114) and the link driver (kernel derekross#185). - Pixel 7a: Bluetooth's device tree merged (kernel derekross#98). The Pixel 8 Pro's row is left to derekross#472. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ss#472) The Pixel 8 Pro's roadmap and DEVICES row as of 2026-11-07: each row checked against the PRs' states, the AoC cell linking device/husky/AOC-PLAN.md, the charging cell with measured numbers and the device tree's cap told apart, which units ran touch and buttons on which tag, a NOTES entry for the two overlay boots, and a dated record of the local unit that marked slot B on one phone from 11-05 until it was masked under the derekross#252 ruling. Signed-off-by: Lef <me@lefteros.com>
…oot cell wording (derekross#488) Two optional points from the review of derekross#472, and the record of slot B on Lef's phone. The roadmap dates the marked state: B stayed marked (0x35 read 06) from the local unit's last write until the first flash after the unit was masked on 2026-11-07, when it read 04. Since then a boot spends one of B's tries (retry count 3 after set_active, 2 after one boot), so the flash-before-the-last-try routine applies. slot-successful:b was not read after those flashes; Lef will add it after the next one. The bit is not cleared by hand. The DEVICES Boot cell says Lef's phone, not this phone. Signed-off-by: Lef <me@lefteros.com>
* device/husky: MODEM-PLAN.md, S1 to S5e with steps, stop conditions, dated results and uname -r Signed-off-by: Lef <me@lefteros.com> * device/husky: MODEM-PLAN.md after derekross's review on derekross#514 Times are now Athens (UTC+2) with the key ones in UTC, and the plan says plainly that S3 to S5e ran after my question on derekross#472 (18:04 UTC) and before any answer, in the status and in Current state. Stock references name Google's s5300 tree and branch, with derekross's line numbers marked as his. The hook description says six AP2CP lines (pda_active is left out on purpose) and the two cpif.ko builds are named by sha256, S5a/S5b without the pda_active file and S5c to S5e with it. The NV check is the first gate and the plan says it ran afterwards. The leftovers on the phone are listed (no modem-test.conf; the test cpif.ko only in the test module trees and /root). The overlays and the S5 scripts that ran are in device/husky/overlays and device/husky/bringup, with two comment lines added to each script. Also: the 92 percent and short-run reason for S5d and S5e, Power + Volume Up for a hung kernel, a sentence on the dead-screen kit, and the Expect, rollback and risk lines for S6. Signed-off-by: Lef <me@lefteros.com> --------- Signed-off-by: Lef <me@lefteros.com>
This brings the Pixel 8 Pro pages up to date. The husky roadmap was frozen at 2026-10-31, when GPU, Bluetooth, haptics, the AoC and the speakers were all "no", and the DEVICES row still had touch and buttons as "testing" with their PRs in review.
What changed:
What I did not check: nothing was booted for this, it is written from the PR texts, the merged files and what already ran on my phone (test trees built on @greenbrettmichael's open PRs, kernel 7.3.0-rc6-omamobile-push1-g50ef3c279021 for most rows, a later test tree for NFC). @greenbrettmichael's rows cite his PRs, I did not re-test his phone. @derekross, if you'd rather keep touch and buttons at "testing" until someone boots the published kernel, say so and I'll change the two cells. Docs only, nothing runs on a phone, so no smoke report.