docs: ASCII typography and style normalization across all repo text
Replace every em dash with real punctuation (rewrites, not hyphen swaps) in docs, code comments, scripts, configs, and the port records; convert en dashes, curly quotes, ellipsis glyphs, arrows, and section signs to ASCII; drop machine-writing tell phrases from living docs. ADR titles now use a colon. The M2 bring-up DTS model string carried an em dash into the patch series and its record echoes; fixed at both, and the full series re-verified to apply cleanly onto pristine 6.18.46. One comment in freshness.h deliberately names the em dash glyph the UI renders as the unknown mark; that is data, kept as prose naming it. Verified: cargo tests (sim, config-lint, rs485-bridge), shellcheck, both driver MC/DC harnesses, patches-apply.
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# TRNG + OTP port (batch A) — 6.18
|
||||
# TRNG + OTP port (batch A): 6.18
|
||||
|
||||
## TRNG (hardware RNG) — VERIFIED on warden-c8a3 (2026-08-25)
|
||||
## 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.
|
||||
|
||||
@@ -12,18 +12,18 @@ register map). Mainline `drivers/char/hw_random/rockchip-rng.c` already drives i
|
||||
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 —
|
||||
**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
|
||||
`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 — VERIFIED on warden-c8a3 (2026-08-25)
|
||||
Reads real data: `dd .../rockchip-otp0/nvmem bs=1 count=16 | xxd` →
|
||||
`5211 02fe 084d 5231 0000 0000 3b15 0000` (contains "MR1" chip id) — no timeout.
|
||||
## OTP / nvmem: VERIFIED on warden-c8a3 (2026-08-25)
|
||||
Reads real data: `dd .../rockchip-otp0/nvmem bs=1 count=16 | xxd` ->
|
||||
`5211 02fe 084d 5231 0000 0000 3b15 0000` (contains "MR1" chip id), no timeout.
|
||||
Mainline `drivers/nvmem/rockchip-otp.c` gains an `rv1106_data` + compatible.
|
||||
|
||||
**Delta:**
|
||||
@@ -42,7 +42,7 @@ static const struct rockchip_data 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
|
||||
**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`). Confirmed: cell reads return real data.
|
||||
|
||||
Reference in New Issue
Block a user