From 9ea182a0263d2a67aebd7de7183fc6f372c0ef62 Mon Sep 17 00:00:00 2001
From: ArthurKoba <61914203+ArthurKoba@users.noreply.github.com>
Date: Mon, 21 Sep 2026 12:26:40 +0300
Subject: [PATCH] svi-252b: record that the IR illuminator is switched
 autonomously (#165)

The profile already left backlightPin unset, but the comment still described
the IR illuminator control as unresolved, which read as unfinished work rather
than as a board fact.

Hardware confirms the illuminator is driven by the board's own daylight-sensor
circuitry. The SoC only observes the resulting light state on GPIO3_0 and
drives the bistable IR-cut filter on GPIO34/33, so there is no SoC-controlled
backlight GPIO to configure here.

Documentation only; runtime configuration is unchanged. This retires the last
caveat the original SVI-252B K202 profile shipped with.
---
 .../general/overlay/usr/share/openipc/customizer.sh          | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/devices/hi3516cv200_lite_spezvision-svi-252b-k202/general/overlay/usr/share/openipc/customizer.sh b/devices/hi3516cv200_lite_spezvision-svi-252b-k202/general/overlay/usr/share/openipc/customizer.sh
index 04d2d2e..b391512 100644
--- a/devices/hi3516cv200_lite_spezvision-svi-252b-k202/general/overlay/usr/share/openipc/customizer.sh
+++ b/devices/hi3516cv200_lite_spezvision-svi-252b-k202/general/overlay/usr/share/openipc/customizer.sh
@@ -16,8 +16,9 @@
 # The board pinmux is reapplied on every boot by /usr/share/openipc/muxes.sh,
 # independently of the selected streamer.
 #
-# The IR illuminator control is still unresolved, so backlightPin remains
-# intentionally unset.
+# The IR illuminator is switched autonomously by the board's daylight-sensor
+# circuitry. The SoC only observes that light state on GPIO3_0 and controls
+# the IR-cut filter, so there is no backlightPin to configure.
 #
 
 fw_setenv upgrade 'https://github.com/OpenIPC/builder/releases/download/latest/hi3516cv200_lite_spezvision-svi-252b-k202-nor.tgz'