hisilicon-osdrv-hi3516cv200: ov2735_i2c_1080p.ini — INPUT_MODE_MIPI + 2-lane

Two fixes to the cv200 OV2735 .ini that prevent it from working
as MIPI on real hardware:

1. input_mode = 4 → 0. The header comment in the same file lists
   INPUT_MODE_MIPI = 0; 4 is the unused successor of LVDS = 2 / DC
   = 3. With input_mode = 4 the ISP driver never configures the
   MIPI RX block, so /proc/driver/hi_mipi keeps its default
   CMOS/4-lane state and no sensor frames reach VI.

2. lane_id = "0|1|2|3|..." → "0|1|...". OV2735 is a 1- or 2-lane
   MIPI sensor — the cv200 hardware here uses 2 lanes (lanes 0 and
   1). Asking for 4 lanes confuses the lane-mapper. Brought in
   line with cv300's already-correct ov2735_i2c_1080p.ini which
   uses "0|1|-1|-1|-1|-1|-1|-1|".

Verified on TP-Link Kasa KC110 (Hi3518EV200 + OV2735 2-lane MIPI):
with these changes /proc/driver/hi_mipi reports LaneNum=2 RAW10
MIPI link 0 1920x1080, ISP IRQ count climbs, VI receives frames.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Author: moontwister

general/package/hisilicon-osdrv-hi3516cv200/files/sensor/config/ov2735_i2c_1080p.ini

@@ -9,7 +9,7 @@ DllFile   =/usr/lib/sensors/libsns_ov2735.so    ;sensor lib path
 
 
 [mode]
-input_mode = 4                          ;INPUT_MODE_MIPI = 0
+input_mode = 0                          ;INPUT_MODE_MIPI = 0
                                         ;INPUT_MODE_SUBLVDS = 1
                                         ;INPUT_MODE_LVDS = 2 ...etc
 
@@ -24,7 +24,7 @@ data_type = 3                           ;raw data type: 8/10/12/14 bit
                                         ;RAW_DATA_10BIT = 2
                                         ;RAW_DATA_12BIT = 3
                                         ;RAW_DATA_14BIT = 4
-lane_id = 0|1|2|3|-1|-1|-1|-1|          ;lane_id: -1 - disable
+lane_id = 0|1|-1|-1|-1|-1|-1|-1|        ;lane_id: -1 - disable
 
 [lvds]
 ;----------only for lvds_dev---------