Repository navigation
device/panther: the touchscreen (FT3658 kernel option, T6) and the touch notes - #149
Conversation
|
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 I checked the pieces against the kernel side. A few things before I merge:
Thanks too for writing up |
|
One correction from my side, and it's our mistake, not yours: we asked you on #109 to put Could you move the line to |
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>
|
Hi Alejandro, a gentle nudge: #145 is merged, so |
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>
8405c21 to
d9bb1d5
Compare
|
Thanks for the nudge, and no need to move the config yourself. Pushed (
The 🤖 Generated with Claude Code |
|
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 |
…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>
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>
…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.
…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>
The Pixel 7's (panther) touchscreen on the repo side, rebased onto main now that #145 is in.
CONFIG_TOUCHSCREEN_FOCALTECH_FT3658=minkernel/configs/omamobile.config, next to the other touchscreen options, with a comment pointing atdevice/panther/TOUCH-PLAN.md. The driver binds only tofocaltech,ft3658, so the module changes nothing on other phones, and the release kernel gets Pixel 7 touch. Nodevice/panther/kernel.config.device/panther/NOTES.md: one boot of kernel7.3.0-rc6-omamobile-push1-g8d46192a301e, arm64: dts: gs201-panther: the touchscreen, suspend-to-idle and LDO25M linux-omarchy-mobile#134 (the touch node,mem_sleep_default=s2idle, LDO25M at 1.8 V, on top of the GPU and haptics) merged with the driver's review fixes, Input: ft3658 - review fixes: DMA-safe buffers, fsleep(), the Google source linux-omarchy-mobile#133. The build's local merge has the same tree as the merge of the PR heads (omamobile-omarchy 0.1.20: the sleep lock turns the display off once the session is secure #134 atace1ba57fbe7, device/lynx: WIFI-PLAN after the fs_ready boot #133 atfdc4f4403103).mem_sleepreads[s2idle] deep,vdd-ts/avdd-tsread 1.8/3.0 V,focaltech_ft3658loads at boot (chip ID 0x56, firmware 0x16), touches work across the panel and unlock the PIN screen with no SPI or CRC errors, and the GPU and haptics keep working.persist's superblock, journal and the ctime of two directories; no data block). NOTES is newest first, as its header says, and BRINGUP-M1's status points at TOUCH-PLAN's result.docs/DEVICES.mdis left as main has it: its Touch cell already gives the current state.Phone evidence: the
tools/phone-smokereport 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) andtools/pr-check upstream/mainpass.🤖 Generated with Claude Code