kernel/rv1106: batch A — TRNG verified + OTP (read fn corrected)

TRNG ✅ VERIFIED on c8a3: rv1106 trngv1 == rk3588 TRNG_V1 IP; one OF-table entry reusing rk3588_soc_data. /dev/hwrng active, rng_current=rockchip-rng, real HW entropy (c697503d... non-zero). Hardware entropy for the panel. OTP 🔨: rockchip-otp0 nvmem device registers; added rv1106_data (6-clock sbpi layout). First reg_read=rk3588_otp_read timed out ('timeout during read setup'); corrected to px30_otp_read (user-mode OTPC_USER interface = the vendor's rk3568_otp_read sequence). Cell reads re-verify next _b boot. See rng-otp/PORT-DONE.md. dts snapshot refreshed (rng+otp enabled). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017wB8KB3MMQztRDXCMCkPrf
2026-08-25 00:44:35 -06:00
parent 92905bf4d4
commit 270211029d
2 changed files with 58 additions and 0 deletions
@@ -187,3 +187,14 @@
 &rga2 {
 	status = "okay";
 };
+
+/* --- batch A: hardware RNG (trngv1, same IP as rk3588) --- */
+&rng {
+	compatible = "rockchip,rv1106-rng";
+	status = "okay";
+};
+
+/* --- batch A: OTP / nvmem (chip id, MAC, PHY bandgap for GMAC) --- */
+&otp {
+	status = "okay";
+};
@@ -0,0 +1,47 @@
+# TRNG + OTP port (batch A) — 6.18
+
+## TRNG (hardware RNG) — ✅ VERIFIED on warden-c8a3 (2026-08-25)
+rv1106's `rockchip,trngv1` is the same standalone TRNG_V1 IP as rk3588 (identical
+register map). Mainline `drivers/char/hw_random/rockchip-rng.c` already drives it.
+
+**Delta:** one OF-table entry reusing `rk3588_soc_data`:
+```c
+{ .compatible = "rockchip,rv1106-rng", .data = (void *)&rk3588_soc_data },
+```
+(The driver grabs clocks via `clk_bulk_get_all` and treats reset as optional, so
+rv1106's clock/reset names need no special handling.) Kconfig
+`HW_RANDOM_ROCKCHIP=y` (already set).
+
+**DT** (`rv1106-warden.dts`): override the dtsi `rng@ff448000` node —
+```dts
+&rng { compatible = "rockchip,rv1106-rng"; status = "okay"; };
+```
+
+**Evidence:** `/dev/hwrng` present, `rng_current = rockchip-rng`,
+`dd if=/dev/hwrng bs=16` → `c697 503d f9db 6b84 50e4 e1ee f232 b2ae` (real HW
+entropy, non-zero). Hardware entropy source for the panel's crypto/keys.
+
+## OTP / nvmem — 🔨 device registers; read fn corrected, re-verify pending
+Mainline `drivers/nvmem/rockchip-otp.c` gains an `rv1106_data` + compatible.
+
+**Delta:**
+```c
+static const char * const rv1106_otp_clocks[] = {
+	"usr", "sbpi", "apb", "phy", "arb", "pmc",   /* matches DT clock-names */
+};
+static const struct rockchip_data rv1106_data = {
+	.size = 0x80,
+	.clks = rv1106_otp_clocks,
+	.num_clks = ARRAY_SIZE(rv1106_otp_clocks),
+	.reg_read = px30_otp_read,     /* user-mode OTPC_USER interface */
+};
+/* OF: { "rockchip,rv1106-otp", &rv1106_data } */
+```
+Kconfig `NVMEM_ROCKCHIP_OTP=y`. **DT:** `&otp { status = "okay"; };` (the dtsi
+`otp@ff3d0000` node already carries compatible + the 6 clocks/resets).
+
+**First try** used `.reg_read = rk3588_otp_read` → `timeout during read setup`
+(rk3588 uses a different addressing path). Corrected to `px30_otp_read` — the
+mainline user-mode OTPC_USER read, the same sequence the vendor 5.10 driver used
+for rv1106 (its `rk3568_otp_read`). Re-verify cell reads on the next _b boot;
+`rockchip-otp0` nvmem device already registers.