Skip to content

device/panther: the touchscreen (FT3658 kernel option, T6) and the touch notes - #149

Merged
derekross merged 7 commits into
derekross:mainfrom
nesmeck:panther-touch-node
Nov 1, 2026
Merged

derekross merged 7 commits into
derekross:mainfrom
nesmeck:panther-touch-node

Conversation

@nesmeck

@nesmeck nesmeck commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

The Pixel 7's (panther) touchscreen on the repo side, rebased onto main now that #145 is in.

docs/DEVICES.md is left as main has it: its Touch cell already gives the current state.

Phone evidence: the tools/phone-smoke report in #145's description covers this boot's kernel too (#134 + #133, plus the USI13 commit for the next PR), with touch ok.

Checks: tests/all (253 ok) and tools/pr-check upstream/main pass.

🤖 Generated with Claude Code

@derekross

Copy link
Copy Markdown
Owner

Thanks, Alejandro. TOUCH-PLAN is a model runbook. It stopped at T2 on the voltage rule instead of pushing on at 3.3 V. It takes regulator summaries before and after each step. It checks that unbind drops both rails with reset asserted. And it records the autoload boot past the 30 s cleanup. The devinfo table is the right kind of evidence too: only the version and the slot bytes, read-only, next to ABL's own getvar answers. Thank you for putting NOTES back in newest-first order as well.

I checked the pieces against the kernel side. CONFIG_TOUCHSCREEN_FOCALTECH_FT3658 is the symbol on omamobile (from #109). The module is focaltech_ft3658, the driver name ft3658 and the compatible focaltech,ft3658, as in derekross/linux-omarchy-mobile#134's node. bin/omamobile kernel merges device/panther/kernel.config only for DEVICE=panther, so no other phone's build changes.

A few things before I merge:

  1. This stacks on device-panther 0.1.1: the GPU, the haptics and suspend-to-idle #145 and carries its commit, so the test fix I've asked for there (the rule comparisons that fail when the package is built on its own) needs to reach this branch too. Once device-panther 0.1.1: the GPU, the haptics and suspend-to-idle #145 is squash-merged, please rebase onto main without its commit: git rebase --onto origin/main a69b7d1. NOTES.md and docs/DEVICES.md will conflict, because this branch changes lines device-panther 0.1.1: the GPU, the haptics and suspend-to-idle #145 also changes. Take your side in both. Main has also moved since: I merged DEVICES: status after the 2026-10-28 evening merges #140, which edits the same panther lines in BRINGUP-M1.md, NOTES.md and DEVICES.md, so expect those three to conflict as well, and take your side there too. I tried it here: with your side taken, the tree is exactly your current head's.

  2. T6 needs its kernel release. The 2026-10-29 entry names omamobile-omarchy 0.1.20: the sleep lock turns the display off once the session is secure #134 and device/lynx: WIFI-PLAN after the fs_ready boot #133 but not the build. Please add the uname -r line, and the two PR heads it was built from (omamobile-omarchy 0.1.20: the sleep lock turns the display off once the session is secure #134 at ace1ba57fbe7, device/lynx: WIFI-PLAN after the fs_ready boot #133 at fdc4f4403103, if those are what you merged), so the result stays tied to the PRs as they are now. A tools/phone-smoke report from that boot in the description would cover CONTRIBUTING §6.5 for both this PR and device-panther 0.1.1: the GPU, the haptics and suspend-to-idle #145.

  3. Two small ones. TOUCH-PLAN's status line is dated 2026-10-27 but reports T6 from the 29th. And in the "second stock fallback" entry, could you add one line saying whether the bytes that differ in efs, efs_backup, modem_userdata and persist sit in the same checkpoint, superblock and journal areas as after boot 6? That's what tells us recovery's mount explains them.

Thanks too for writing up linux-modules-cleanup eating a modules-push tree. The service comes with Omarchy's base packages, so it most likely affects every phone, not just yours. That one is ours to fix in the tooling.

@derekross

Copy link
Copy Markdown
Owner

One correction from my side, and it's our mistake, not yours: we asked you on #109 to put CONFIG_TOUCHSCREEN_FOCALTECH_FT3658=m in device/panther/kernel.config. That file is only for options that would break another device (docs/RELEASES.md, the paragraph after the descriptor table), because the release kernel (§4) is one build for every phone and never reads a device's kernel.config. The FT3658 driver binds only to its own compatible, so the module breaks nothing elsewhere, and in kernel.config a release kernel would ship without Pixel 7 touch.

Could you move the line to kernel/configs/omamobile.config instead, next to the other touchscreen options, with a short comment pointing at device/panther/TOUCH-PLAN.md, and drop device/panther/kernel.config (or leave it out of this PR)? The T6 entry can then say the option comes from the shared fragment. Sorry for the extra round trip.

derekross added a commit that referenced this pull request Oct 30, 2026
The matrix and the Wanted list against what has merged since #140, with
each pull request's state checked on GitHub today:

- Pixel 7 (panther): the GPU and haptics nodes (kernel #129, #130) were
  closed because they landed unchanged through kernel #134, merged with
  the touchscreen node and s2idle by default; device-panther 0.1.1 (#145)
  carries the GPU's always-on rule, the feedbackd rule and the sleep.conf
  drop-in. GPU and Haptics stay "testing" and now cite #134, #145 and the
  2026-10-28 notes. Touch stays WIP: kernel #134's body records touches
  driving Hyprland and the PIN screen, but the driver fixes (kernel #133)
  and the kernel option with the touch notes (#149) are still in review.
  Suspend: "no" with the s2idle default named, since the notes say it
  hasn't run.
- Pixel 6 Pro (raven): Haptics "no" -> "works": HAPTICS-TORCH-PLAN H5
  passed (2026-10-28/29), cs40l25-vibra and the node merged as kernel
  #114, feedbackd's rule in device-raven 0.1.27 (#113). Display names
  its open kernel PR, #116.
- Pixel 7a (lynx): Bluetooth "no" -> WIP: the merged WIFI-PLAN (#133)
  records it scanning through its own UART; kernel #98 and #98 are in
  review. The Wanted line says so too.
- Pixel 7 Pro (cheetah) detail: Boot names the AVB footers a chained
  vbmeta_b needs (NOTES 2026-10-28 and 10-29, #104); Suspend describes
  the merged tier 1 auto-sleep (#64, off by default behind the
  omamobile-sleep toggle, P0-P5 on 2026-10-26) in place of the old
  "until S8" text. Nothing from the open #171, #172, #174-#176.
- Wanted: coral's #52 is merged, so its line no longer says "in review";
  flame gets a line for its native install in review (#55, #56, #58,
  #59, split out of #17); the OnePlus 13 (dodge) is listed with #111 and
  kernel #115, both open.

The Pixel 9a row and the Pixel 9 family line are left to #165. Every
status word still parses with the website's parseCell.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
@derekross

Copy link
Copy Markdown
Owner

Hi Alejandro, a gentle nudge: #145 is merged, so git rebase --onto origin/main a69b7d1 works now. With the FT3658 line moved to kernel/configs/omamobile.config and the T6 uname -r added, I'll merge. If you'd rather, I can make the config move myself; just say so.

nesmeck and others added 7 commits October 31, 2026 13:50
The Pixel 7's touch controller read only zeros because ABL leaves its
supplies off: S2MPG12 LDO25M (VDD) and LDO26M (AVDD), as on the Pixel
Fold. With linux-omarchy-mobile#27's S2MPG12 LDO driver on the local
kernel branch, the touch driver switches them on in Google's order and
the controller answers: chip ID 0x56, firmware 0x16.

LDO26M holds 3.3 V when ABL hands over, above stock's 2.5-3.0 V range;
the plan stopped there (T2) and the DT now fixes it at 3.0 V, which the
regulator core set while the rail was off (T2b). Only the two touch
rails changed state, at the voltages expected; unbind asserts reset and
drops both (T5). Touch events (T4) wait for someone at the phone; a
read-only register dump shows the chip awake and scanning.

NOTES gets the devinfo 3.19 evidence so far for L-36: every getvar and
slot-byte reading agrees with cheetah's layout.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The corners land where they should on the 1080x2400 panel, so the board
file needs no swap or inversion flags; the owner unlocked the phone by
touch. All gates passed; autoload is next.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The bootargs no longer keep the FT3658 and the S2MPG12 regulators out,
and the touch comes up 3.6 s into the boot; the lock screen took the PIN
by touch. NOTES.md records the next slot-B getvar for L-36, and two
things found on the way: Omarchy's shut down reboots the phone with the
cable in, and linux-modules-cleanup drops a modules-push tree when
another kernel boots first.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Getting to fastboot spent slot B's last retry again and stock recovery ran; the reset was declined and a fresh read-only backup taken.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The 2026-10-27 entries had landed oldest first below the stock facts,
while the header says newest first. Put them in order after the
2026-10-28 entry, and note on the 10-27 power-off entry that it reboots
without the cable too.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Add panther's kernel.config with CONFIG_TOUCHSCREEN_FOCALTECH_FT3658=m,
as derekross asked in linux-omarchy-mobile#109, for the touch node in
review in linux-omarchy-mobile#134. NOTES records T6, one boot of that
node with the driver's review fixes (derekross#133), suspend-to-idle and LDO25M at
1.8 V: the touch loads at boot, works across the panel and unlocks the
PIN screen, and the GPU and the haptics keep working. TOUCH-PLAN's status
and the Pixel 7 row's Touch cell say so.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ss#149's review points

Move CONFIG_TOUCHSCREEN_FOCALTECH_FT3658=m to kernel/configs/omamobile.config,
next to the other touchscreen options, and drop device/panther/kernel.config:
that file is for options that would break another device, and the release
kernel never reads it; the driver binds only to its own compatible.

NOTES' T6 entry names its kernel release and how it relates to the PR heads
(derekross#134 at ace1ba57fbe7, derekross#133 at fdc4f4403103: the build's local merge has the
same tree), and that the option came from the shared fragment. The second
stock fallback entry says where the changed bytes sit: the same areas as
after boot 6. TOUCH-PLAN's status line carries T6's date, and BRINGUP-M1's
status says the FT3658 never answered because of its supplies, pointing at
TOUCH-PLAN's result.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@nesmeck
nesmeck force-pushed the panther-touch-node branch from 8405c21 to d9bb1d5 Compare October 31, 2026 20:57
@nesmeck

nesmeck commented Oct 31, 2026

Copy link
Copy Markdown
Contributor Author

Thanks for the nudge, and no need to move the config yourself. Pushed (d9bb1d5), rebased with git rebase --onto origin/main a69b7d1:

  1. The config. CONFIG_TOUCHSCREEN_FOCALTECH_FT3658=m is in kernel/configs/omamobile.config after the Synaptics TCM line, with a comment pointing at TOUCH-PLAN; device/panther/kernel.config is gone. The T6 entry says the option came from the shared fragment, which is also what the T6 build actually used (the line was there, uncommitted, when it was built).
  2. T6's kernel. 7.3.0-rc6-omamobile-push1-g8d46192a301e. Its local merge (8d46192a3) was made before the commit messages got their test paragraphs and sign-offs, so it isn't literally ace1ba57f + fdc4f4403, but git merge-tree of those two heads gives the same tree (0eb5d6eb); the entry says so.
  3. The small ones. TOUCH-PLAN's status is dated 2026-10-29. For the fallback bytes, I compared both backup pairs block by block: the second fallback changed the same areas as boot 6 in all four. In efs, efs_backup and modem_userdata, the checkpoint (the other of its two copies) and the root inode's node block, written with the checkpoint version just before the new one; in persist, the superblock, the first five journal blocks (2057-2061) and one inode table block where only the ctime of /sensors and /sensors/registry moved, the same two inodes as after boot 6. No data block, so recovery's mount explains it. The boot 6 entry only said "superblock and journal"; the new line names the inode block too.
  4. BRINGUP-M1. The status now says the FT3658 never answered in boots 6 to 8, with the driver loaded, because its supplies were off, and points at TOUCH-PLAN, where touch works from T4 on.

The DEVICES.md conflict I resolved to main's side: your Touch cell already says #134 is merged and #133 and this PR are in review, so this PR no longer touches that file.

🤖 Generated with Claude Code

@derekross
derekross merged commit 4087aaa into derekross:main Nov 1, 2026
2 checks passed
@derekross

Copy link
Copy Markdown
Owner

Thanks, Alejandro, and thanks for taking the config move yourself after our own mix-up. Everything I asked for is in: the clean rebase without #145's commit, the FT3658 option in the shared fragment with device/panther/kernel.config gone, T6's uname -r with both PR heads, the corrected status date, and the fallback-bytes line. focaltech,ft3658 appears only in the panther board file on the published kernel, so the module can't bind on any other phone. Merged. One note for the kernel side: until derekross/linux-omarchy-mobile#133 lands, a kernel from the published branch has the driver without its review fixes, so I'll try to get #133 in soon.

derekross added a commit that referenced this pull request Nov 1, 2026
…s on the 7 Pro (#254)

Kernel #153 (husky touch), #166 and #133 and omarchy-mobile #149 (panther touch) merged on 2026-10-31 and 11-01, and omamobile-audio 0.5.8 raised the 7 Pro's default speaker gains under verified protection. The website's device pages are built from this file.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
The matrix and the Wanted list against what has merged since derekross#140, with
each pull request's state checked on GitHub today:

- Pixel 7 (panther): the GPU and haptics nodes (kernel derekross#129, derekross#130) were
  closed because they landed unchanged through kernel derekross#134, merged with
  the touchscreen node and s2idle by default; device-panther 0.1.1 (derekross#145)
  carries the GPU's always-on rule, the feedbackd rule and the sleep.conf
  drop-in. GPU and Haptics stay "testing" and now cite derekross#134, derekross#145 and the
  2026-10-28 notes. Touch stays WIP: kernel derekross#134's body records touches
  driving Hyprland and the PIN screen, but the driver fixes (kernel derekross#133)
  and the kernel option with the touch notes (derekross#149) are still in review.
  Suspend: "no" with the s2idle default named, since the notes say it
  hasn't run.
- Pixel 6 Pro (raven): Haptics "no" -> "works": HAPTICS-TORCH-PLAN H5
  passed (2026-10-28/29), cs40l25-vibra and the node merged as kernel
  derekross#114, feedbackd's rule in device-raven 0.1.27 (derekross#113). Display names
  its open kernel PR, derekross#116.
- Pixel 7a (lynx): Bluetooth "no" -> WIP: the merged WIFI-PLAN (derekross#133)
  records it scanning through its own UART; kernel derekross#98 and derekross#98 are in
  review. The Wanted line says so too.
- Pixel 7 Pro (cheetah) detail: Boot names the AVB footers a chained
  vbmeta_b needs (NOTES 2026-10-28 and 10-29, derekross#104); Suspend describes
  the merged tier 1 auto-sleep (derekross#64, off by default behind the
  omamobile-sleep toggle, P0-P5 on 2026-10-26) in place of the old
  "until S8" text. Nothing from the open derekross#171, derekross#172, derekross#174-derekross#176.
- Wanted: coral's derekross#52 is merged, so its line no longer says "in review";
  flame gets a line for its native install in review (derekross#55, derekross#56, derekross#58,
  derekross#59, split out of derekross#17); the OnePlus 13 (dodge) is listed with derekross#111 and
  kernel derekross#115, both open.

The Pixel 9a row and the Pixel 9 family line are left to derekross#165. Every
status word still parses with the website's parseCell.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…uch notes (derekross#149)

Panther's touchscreen: CONFIG_TOUCHSCREEN_FOCALTECH_FT3658=m in the shared fragment next to the Synaptics line (focaltech,ft3658 appears only in gs201-panther.dts, so it binds nowhere else), and BRINGUP-M1, NOTES and TOUCH-PLAN with T6's result on 7.3.0-rc6-omamobile-push1-g8d46192a301e (kernel derekross#134 at ace1ba57fbe7, derekross#133 at fdc4f4403103). device/panther/kernel.config is gone.
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…s on the 7 Pro (derekross#254)

Kernel derekross#153 (husky touch), derekross#166 and derekross#133 and omarchy-mobile derekross#149 (panther touch) merged on 2026-10-31 and 11-01, and omamobile-audio 0.5.8 raised the 7 Pro's default speaker gains under verified protection. The website's device pages are built from this file.

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.

2 participants