Repository navigation
device/husky: MODEM-PLAN.md, S1 to S5e with results - #514
Conversation
…ated results and uname -r Signed-off-by: Lef <me@lefteros.com>
|
@Somnius thank you for writing this up so quickly and for stopping when I asked. It's a careful record: one flash per stage, the retry counts, the UFS counters at every step, and for each stage what it does and doesn't prove. I read the hook on your branch and it does what the plan says: only the stock line helpers, no state change, no CP memory, no PCIe and no PMU. I also checked that Google's A few things to fix in the file before I merge it:
Smaller ones:
I still owe you the answer on #472, and S6 waits for it. Nothing else to run on the modem until then. |
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>
|
@derekross thank you for the careful read. I went through all six and the smaller ones, and pushed them as one commit on the branch: 2cf5c3f.
The smaller ones are in too: Power + Volume Up for a hung kernel, that nothing armed a watchdog and every step was attended, why S5d and S5e were on battery (a few minutes each, at 92 %, and on this phone that is full: the charger chip finishes at 4350 mV, as in #452, and I can't get it above 92 % either, not even on the Baseus charger I bought for this phone), the dead-screen kit sentence with linux-omarchy-mobile#215, and Expect, rollback and risk lines plus the stop rules for S6. I'm still holding every modem and power-line step until you answer the #472 question. |
|
Thank you, @Somnius. I went through the new commit point by point against the file, not just I'll merge it as it is. A few small things for later, none needed now:
I still owe you the answer on #472, and nothing more runs on the modem until then. |
* 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 is the modem plan @derekross asked for on kernel #187: S1 to S5e on the 8 Pro with the steps, the gates, the stop conditions, the dated results and the
uname -rof each stage. Where a log didn't print the release itself, the file says which image set was flashed. It also has an "on hold" section (no more modem steps, no power lines until the answer on #472) and a list of what is still unknown.The code that ran is on a public branch: https://github.com/Somnius/linux-omarchy-mobile/tree/husky-modem-cpif-test-hook (a test only debugfs hook, not for merge).
It's docs only. I ran tools/pr-check against main, it passes. I didn't run the whole tests/all, CI will.