v2 Phase 1: verify FT3168 touch needs no coordinate transform

On-hardware calibration (5-point corner+center tap) confirms the FT3168 on the
2.06 panel reports directly in panel pixel space (~0..409 x ~0..501), correctly
oriented with no axis swap or mirror — a center tap reads ~(209,228) against the
410x502 panel center (205,251), a 1:1 mapping within finger error. The existing
raw passthrough is correct; record the verified result in the driver comment.
The temporary on-screen TOUCH_DEBUG overlay used to gather this has been removed.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
wenil
2026-06-20 14:16:00 +03:00
co-authored by Claude Opus 4.8
parent 25b101d086
commit 8d82beaacf
@@ -10,9 +10,11 @@
// reg 0x03 / 0x04: X1 high (low nibble) + X1 low
// reg 0x05 / 0x06: Y1 high (low nibble) + Y1 low
//
// Axis orientation: started with no swap/mirror (matches the portrait FT3168
// on the 1.8 board). If touch coordinates come out flipped/swapped on this
// panel, mirror/swap them in touch_read_into_shared_state() below.
// Axis orientation: verified on hardware (v2 Phase 1). The FT3168 reports
// directly in the panel's pixel space (~0..409 x ~0..501), correctly oriented
// (x grows left->right, y grows top->bottom, no axis swap). A center tap reads
// ~(209,228) vs the 410x502 panel center (205,251) — a 1:1 mapping within
// finger error. Raw values pass straight through; no mirror/swap/scale needed.
static volatile bool touch_data_ready = false;
static volatile bool touch_pressed = false;