sdk: bootstrap standalone repo (P0)
- Dual license (LICENSE / LICENSE-MIT / LICENSE-APACHE) matching the crate manifests. - ADRs 0001-0005: kernel base (direct 5.10->6.18.46 forward-port), tiered MC/DC, standalone repo, CI runner (3rd repo-scoped runner on 0640), driver source-of-truth. - README goal 1 reconciled to the verified 6.18.46 forward-port (was stale plan44/6.6). - Drop tracked build objects (*.o now gitignored). - Capture the display (VOP dclk-pol + WIN1) and GT911 touch bring-up VERIFIED docs + capabilities-audit update from this session. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017wB8KB3MMQztRDXCMCkPrf
This commit is contained in:
BFE Engineering
co-authored by
Claude Opus 4.8
Claude Opus 4.8
parent
19ff701deb
commit
189f7aec38
@@ -16,8 +16,20 @@ PWM backlight · **USB host** (dwc3/xhci) + usb2phy · grf/pmu syscons.
|
||||
- **GMAC** — eth0 Link Up 100 Mbps/Full (`gmac/`).
|
||||
- **SARADC** — iio:device0 reads 2 ch; the −22 was vref, not clk (`adc/SARADC-FIX.md`).
|
||||
|
||||
## ✅ VOP display — VERIFIED this run (2026-08-25)
|
||||
Full WardenOS Dashboard renders on the 86-Panel on 6.18 (`_b`), webcam-verified,
|
||||
pixel-identical to stock `_a`. Two VOP driver bugs were the final black-screen
|
||||
cause: `rgb_dclk_pol` hardcoded inverted (panel needs 0), and the wrong primary
|
||||
scanout window (rv1106 uses **WIN1**, not rv1126's WIN2). Full chain + `_a`-vs-`_b`
|
||||
register diff in `display/VERIFIED.md`.
|
||||
|
||||
## ✅ GT911 touch — VERIFIED this run (2026-08-25)
|
||||
UI responds to taps/swipes on the panel ([maintainer]-confirmed); GT911 detected
|
||||
(`ID 911, version 1060`), `/dev/input/event0` held by warden-ui. Fix:
|
||||
`CONFIG_TOUCHSCREEN_GOODIX=y` (built-in — the rootfs `goodix.ko` is a 5.10 build
|
||||
that can't load on 6.18) + GT911 node on `&i2c3`. Details in `touch/VERIFIED.md`.
|
||||
|
||||
## 🔨 In flight
|
||||
- **VOP display** — binds; connector is tomorrow's on-panel work.
|
||||
- **i2s-tdm** — DAI builds; needs the codec + card (below).
|
||||
- **AIC8800 BT** — module built (6.18 vermagic); HCI bring-up not yet exercised.
|
||||
|
||||
|
||||
@@ -39,13 +39,11 @@ rockchip-drm display-subsystem: bound ff990000.vop
|
||||
brightness settable). **The VOP driver port is validated** — the register data,
|
||||
version, feature, and resets are right.
|
||||
|
||||
## Open (needs on-panel eyes + a little more debug)
|
||||
## ✅ RESOLVED — full UI renders on the panel (2026-08-25)
|
||||
|
||||
`/sys/class/drm/card0-*` has **no connector yet** — `rockchip_rgb_init` isn't
|
||||
producing one (log: `Cannot find any crtc or sizes`), despite INTERNAL_RGB set and
|
||||
a clean vop→panel of_graph. Likely a panel-probe-order / `drm_of_find_panel_or_bridge`
|
||||
detail. This is the last mile of M4 and, unlike the driver bind, needs the panel
|
||||
physically observed (pixels can't be verified over serial/ssh). To pin it down: a
|
||||
debug print in `rockchip_rgb_init` (child_count / find-panel ret), and set the panel
|
||||
bus_format to `MEDIA_BUS_FMT_RGB666_1X18` (a small `panel_dpi_probe` addition, since
|
||||
mainline panel-dpi doesn't read bus-format from DT).
|
||||
The connector *and* the deeper black-screen chain that followed it are fixed; the
|
||||
86-Panel now draws the full WardenOS Dashboard on 6.18 (`_b`), verified by webcam.
|
||||
The two final root causes were VOP driver bugs — `rgb_dclk_pol` hardcoded inverted,
|
||||
and the wrong primary scanout window (rv1106 scans out via **WIN1**, not WIN2).
|
||||
See **`VERIFIED.md`** for the complete bring-up chain, the `_a`-vs-`_b` register
|
||||
diff that pinned it down, and every file changed.
|
||||
|
||||
@@ -0,0 +1,87 @@
|
||||
# Display (VOP + RGB panel) — ✅ VERIFIED on warden-c8a3 (2026-08-25)
|
||||
|
||||
The 86-Panel renders the **full WardenOS Dashboard UI** on our self-built Linux
|
||||
6.18.46 (`_b` slot), pixel-identical to the stock 5.10 `_a` slot. Verified by
|
||||
webcam pointed at the physical panel (pixels can't be checked over serial/ssh) —
|
||||
`warden-ui -b DRM` drawing the Dashboard: nav sidebar, "Wellhead 03" site card,
|
||||
Mesh/WAN/LAN/RS485 status rows, correct colors, no banding, no colour swap.
|
||||
|
||||
This closes the "Open" item in `README.md` (connector-not-created + the deeper
|
||||
black-screen chain that followed it).
|
||||
|
||||
## The bring-up chain (each step was a real blocker)
|
||||
|
||||
1. **Connector never created** (`Cannot find any crtc`): `CONFIG_ROCKCHIP_RGB`
|
||||
was not set, AND the vendor `&rgb` bridge node's dangling endpoint
|
||||
(`rgb_in_vop -> vop_out_rgb`) read to fw_devlink as a vop↔panel dependency
|
||||
cycle, so the VOP probed before the panel. Fix: enable `ROCKCHIP_RGB` +
|
||||
`/delete-node/ &rgb;` so `vop_out_rgb <-> panel_in_vop` is the only graph link
|
||||
(rockchip_rgb_init then defers + retries and finds the panel → `LVDS-1`).
|
||||
2. **Backlight dark**: `&pwm1` had `pinctrl-names = "active"`; mainline
|
||||
pwm-rockchip relies on the driver core auto-applying the **`"default"`** state,
|
||||
so the PWM pin was never muxed. Fix: rename to `"default"`.
|
||||
3. **bus-format unset** (RGB output width undefined): mainline `panel-dpi`
|
||||
ignores the DT `bus-format`. Fix: small `panel_dpi_probe()` patch to read it +
|
||||
`bus-format = <MEDIA_BUS_FMT_RGB666_1X18>` on the panel node.
|
||||
4. **RGB output pins unmuxed** (no data reaches the panel): the 22-pin parallel
|
||||
bus (`lcd_clk` + `lcd_d0..d17` + den/hsync/vsync) needs the `&lcd_pins` mux.
|
||||
The vendor carried it as `pinctrl-0 = <&lcd_pins>` **on the `&rgb` node**, which
|
||||
we deleted in step 1. Fix: re-attach it on `&vop` (`pinctrl-names="default"`;
|
||||
the core auto-applies it at VOP probe).
|
||||
5. **`reset-gpios` on the panel node is WRONG** (leave it off): GPIO0_A1 resets the
|
||||
CH32V003 panel-init MCU, released once early by U-Boot `board_init()`. Handing
|
||||
it to `panel-simple` makes `drm_panel_prepare()` re-reset the MCU mid-scanout.
|
||||
Luckfox deleted these props upstream (commit e2b0ffa22); the flare-edge 5.10 DTS
|
||||
documents the deletion as "the fix." We match: **backlight only, no reset-gpios**.
|
||||
|
||||
## The two root causes of the final "backlit-black" (VOP driver bugs)
|
||||
|
||||
With connector + backlight + pins + panel-init all correct, the screen was still
|
||||
physically black (backlight on, `LVDS-1` connected, VOP streaming, fb0 720×720,
|
||||
`modetest`/splash written) — the classic "everything healthy, glass dark" state.
|
||||
Found by dumping the VOP register block `0xff990000` on the **working `_a` slot**
|
||||
and diffing against `_b` (same SoC, same register map):
|
||||
|
||||
**Bug 1 — DCLK polarity inverted.** `rockchip_drm_vop.c` hardcodes
|
||||
`rgb_dclk_pol = 1` for the LVDS/RGB output. The panel latches pixel data on the
|
||||
**non-inverted** edge — `_a` reads `PX30_DSP_CTRL0` (0xff990020) = `0x1`
|
||||
(rgb_dclk_pol bit1 = **0**). The vendor 5.10 derives it as
|
||||
`(bus_flags & PIXDATA_DRIVE_NEGEDGE) ? 1 : 0`, which is 0 for this panel. With the
|
||||
inverted clock the panel samples RGB on the wrong edge → black. **Fix:** set
|
||||
`rgb_dclk_pol` to 0 in the `DRM_MODE_CONNECTOR_LVDS` case.
|
||||
|
||||
**Bug 2 — wrong primary scanout window.** The rv1106 VOP scans out through
|
||||
**WIN1**, but our port reused rv1126's win table (`win0`-overlay + **`win2`**-primary).
|
||||
The vendor `rv1106_vop_win_data` is `{ NULL-win0, rk3366_lit_win1_data-primary }` —
|
||||
i.e. WIN1 (`PX30_WIN1_*` at 0x090). Mainline was configuring WIN2, which never
|
||||
reaches this SoC's RGB interface, so WIN1 stayed all-zero and nothing scanned out.
|
||||
Register evidence (`_a` working vs `_b` broken, before the fix):
|
||||
|
||||
| reg | name | `_a` (works) | `_b` (black) |
|
||||
|---|---|---|---|
|
||||
| 0x090 | WIN1_CTRL0 (enable) | `0x00000001` | `0x00000000` |
|
||||
| 0x098 | WIN1_VIR (stride) | `0x000002D0` (720) | `0x00000000` |
|
||||
| 0x0a0 | WIN1_MST (fb addr) | `0x0F900000` | `0x00000000` |
|
||||
| 0x0a4 | WIN1_DSP_INFO (size)| `0x02CF02CF` (720×720) | `0x00EF013F` (stale) |
|
||||
|
||||
**Fix:** `rv1106_vop_win_data[] = { { .phy = &px30_win1_data, PRIMARY } }`
|
||||
(`px30_win1_data` already exists in mainline over `PX30_WIN1_*` — just wasn't wired
|
||||
for rv1106). After the fix `_b` reads WIN1_CTRL0=1, WIN1_DSP_INFO=0x02CF02CF —
|
||||
matching `_a`.
|
||||
|
||||
## Files changed (in research/linux-6.18.46)
|
||||
|
||||
- `drivers/gpu/drm/rockchip/rockchip_drm_vop.c` — `rgb_dclk_pol` 1 → 0 (LVDS case).
|
||||
- `drivers/gpu/drm/rockchip/rockchip_vop_reg.c` — `rv1106_vop_win_data` uses
|
||||
`px30_win1_data` as the single PRIMARY window (was rv1126's win0+win2).
|
||||
- `drivers/gpu/drm/panel/panel-simple.c` — `panel_dpi_probe()` reads DT `bus-format`.
|
||||
- `arch/arm/boot/dts/rockchip/rv1106-warden.dts` — `&vop` pinctrl `<&lcd_pins>`;
|
||||
`&pwm1` pinctrl "default"; `/delete-node/ &rgb`; panel `bus-format` RGB666,
|
||||
no reset-gpios.
|
||||
|
||||
## Known separate issue (NOT display)
|
||||
|
||||
`_b` still cold-reboots periodically (pre-existing `_b` general-stability issue,
|
||||
independent of the display — the panel renders correctly the whole time it is up).
|
||||
Tracked separately; the high-bootlimit env (`bootlimit=10000`) keeps these reboots
|
||||
from tripping `altbootcmd=download` into the loader during bring-up.
|
||||
@@ -0,0 +1,57 @@
|
||||
# GT911 capacitive touch — ✅ VERIFIED on warden-c8a3 (2026-08-25)
|
||||
|
||||
Touch works on our self-built 6.18.46 (`_b`): the WardenOS UI responds to
|
||||
taps/swipes ([maintainer] confirmed on the physical panel). Objective evidence:
|
||||
|
||||
```
|
||||
Goodix-TS 3-0014: ID 911, version: 1060
|
||||
input: Goodix Capacitive TouchScreen as .../i2c-3/3-0014/input/input0
|
||||
```
|
||||
`/dev/input/event0` is created and held open by `warden-ui` (pid 517, exclusive
|
||||
EVIOCGRAB — which is why a second reader sees 0 bytes; the events go to the UI).
|
||||
|
||||
## Root cause on `_b`
|
||||
|
||||
Touch was dead on `_b` while fine on `_a`. dmesg showed:
|
||||
```
|
||||
module goodix: .gnu.linkonce.this_module section size must match the kernel's
|
||||
built struct module size at run time
|
||||
```
|
||||
The **stock rootfs ships `goodix.ko` built for the 5.10 kernel**; it cannot load
|
||||
on our 6.18 (`struct module` layout mismatch). Our 6.18 `.config` did **not** have
|
||||
the driver at all (`# CONFIG_TOUCHSCREEN_GOODIX is not set`), and the DTS had no
|
||||
GT911 node — so nothing drove the GT911.
|
||||
|
||||
## Fix
|
||||
|
||||
1. **`CONFIG_TOUCHSCREEN_GOODIX=y`** — build the mainline Goodix driver *into* the
|
||||
kernel (no module → no vermagic/struct mismatch; the stale rootfs `.ko` still
|
||||
fails to insmod but is now harmless).
|
||||
2. **GT911 DT node** under `&i2c3` (matches the vendor 86-panel wiring):
|
||||
```
|
||||
touchscreen@14 {
|
||||
compatible = "goodix,gt911";
|
||||
reg = <0x14>;
|
||||
interrupt-parent = <&gpio0>;
|
||||
interrupts = <RK_PA0 IRQ_TYPE_EDGE_FALLING>;
|
||||
irq-gpios = <&gpio0 RK_PA0 GPIO_ACTIVE_HIGH>;
|
||||
reset-gpios = <&gpio3 RK_PD0 GPIO_ACTIVE_HIGH>;
|
||||
};
|
||||
```
|
||||
plus `pinctrl-0 = <&i2c3m2_xfer &tp_rst &tp_irq>` on `&i2c3` and the `tp_rst`
|
||||
(GPIO3_D0) / `tp_irq` (GPIO0_A0) pin groups.
|
||||
|
||||
Polarity note: mainline goodix drives reset **logical 0 = hold, 1 = release**, and
|
||||
the GT911 reset is physically active-low, so `reset-gpios` is **ACTIVE_HIGH**
|
||||
(logical==physical) — NOT the ACTIVE_LOW the vendor 5.10 driver used. Confirmed
|
||||
against mainline gt911 DT examples (sun7i-a20-wexler-tab7200 etc.): both irq-gpios
|
||||
and reset-gpios are ACTIVE_HIGH; reg 0x14 needs irq-gpios for address select.
|
||||
|
||||
Non-fatal: `Direct firmware load for goodix_911_cfg.bin failed (-2)` — the GT911
|
||||
uses its flashed internal config; touch works without a cfg.bin.
|
||||
|
||||
## Files changed (research/linux-6.18.46)
|
||||
|
||||
- `.config` — `CONFIG_TOUCHSCREEN_GOODIX=y`.
|
||||
- `arch/arm/boot/dts/rockchip/rv1106-warden.dts` — GT911 node on `&i2c3`,
|
||||
`tp_rst`/`tp_irq` pin groups under `&pinctrl`.
|
||||
Reference in New Issue
Block a user