Kernel startup warning

Hello, I have a question now, there is a warning when I start the kernel:

[    3.216639] ------------[ cut here ]------------
[    3.216650] WARNING: CPU: 6 PID: 1 at drivers/regulator/core.c:2157 _regulator_put+0x34/0xc8
[    3.216654] Modules linked in:
[    3.216663] CPU: 6 PID: 1 Comm: swapper/0 Not tainted 5.10.110 #5
[    3.216667] Hardware name: armsom w3 (DT)
[    3.216673] pstate: 80c00009 (Nzcv daif +PAN +UAO -TCO BTYPE=--)
[    3.216678] pc : _regulator_put+0x34/0xc8
[    3.216683] lr : regulator_put+0x3c/0x54
[    3.216687] sp : ffffffc011f3b690
[    3.216691] x29: ffffffc011f3b690 x28: 0000000000000000 
[    3.216698] x27: ffffff82fefc8c18 x26: 0000000000000000 
[    3.216705] x25: ffffffc011d30628 x24: ffffffc0112d194b 
[    3.216711] x23: ffffff810302a200 x22: 0000000000000003 
[    3.216718] x21: ffffff8101053020 x20: ffffff810302a500 
[    3.216724] x19: ffffff810302a500 x18: 0000000000000000 
[    3.216730] x17: 000000000000000e x16: 0000000000000007 
[    3.216737] x15: 000000000000000a x14: 0000000000034e20 
[    3.216743] x13: 0000000000000006 x12: ffffffffffffffff 
[    3.216750] x11: 0000000000000010 x10: ffffff81010b9638 
[    3.216757] x9 : ffffffc0106000c4 x8 : ffffff810302a200 
[    3.216763] x7 : ffffff8101053328 x6 : ffffffc0107d89a8 
[    3.216769] x5 : ffffff8101053328 x4 : 0000000000000000 
[    3.216776] x3 : 0000000000000000 x2 : ffffff81003d8000 
[    3.216782] x1 : 0000000000000000 x0 : 0000000000000001 
[    3.216789] Call trace:
[    3.216794]  _regulator_put+0x34/0xc8
[    3.216799]  regulator_put+0x3c/0x54
[    3.216806]  devm_regulator_release+0x20/0x2c
[    3.216814]  release_nodes+0x1f4/0x224
[    3.216820]  devres_release_all+0x5c/0x60
[    3.216825]  really_probe+0x218/0x46c
[    3.216830]  driver_probe_device+0x138/0x148
[    3.216835]  __device_attach_driver+0xd8/0x114
[    3.216842]  bus_for_each_drv+0xa4/0xcc
[    3.216847]  __device_attach+0xdc/0x170
[    3.216851]  device_initial_probe+0x20/0x2c
[    3.216856]  bus_probe_device+0x3c/0xa0
[    3.216863]  device_add+0x544/0x6e4
[    3.216868]  device_register+0x2c/0x3c
[    3.216876]  i2c_new_client_device+0x21c/0x2b4
[    3.216881]  of_i2c_register_devices+0x140/0x1c0
[    3.216887]  i2c_register_adapter+0x490/0x5fc
[    3.216893]  __i2c_add_numbered_adapter+0x98/0xa0
[    3.216899]  i2c_add_numbered_adapter+0x38/0x3c
[    3.216905]  rk3x_i2c_probe+0x424/0x474
[    3.216910]  platform_drv_probe+0x60/0xb0
[    3.216914]  really_probe+0x2dc/0x46c
[    3.216919]  driver_probe_device+0x138/0x148
[    3.216924]  device_driver_attach+0x50/0x7c
[    3.216930]  __driver_attach+0x150/0x154
[    3.216935]  bus_for_each_dev+0x7c/0xc8
[    3.216940]  driver_attach+0x30/0x3c
[    3.216945]  bus_add_driver+0x1b4/0x1fc
[    3.216950]  driver_register+0xc0/0xf8
[    3.216955]  __platform_driver_register+0x58/0x64
[    3.216963]  rk3x_i2c_driver_init+0x28/0x34
[    3.216969]  do_one_initcall+0xa0/0x1e8
[    3.216975]  kernel_init_freeable+0x2a8/0x2b0
[    3.216981]  kernel_init+0x20/0x11c
[    3.216987]  ret_from_fork+0x10/0x30

The system is not stuck, but is there anything wrong with this phenomenon

Hello, this is because this firmware supports mipi-dsi and you do not have a mipi-dsi screen connected.

You can choose to burn firmware that does not support mipi-dsi screens