@debian I suggest you use fenix to build you kernel. Buecase fenix will automatically help you solve many environmental problems. The kernel can also be compiled separately using fenix.
I modified ~/fenix/linux/make ARCH=arm64 menuconfig to CONFIG_IIO_SW_TRIGGER = y, CONFIG_IIO_SW_DEVICE = y.
However, if you run ~/fenix/make, linux code is newly imported and initialized to default, and CONFIG_IIO_SW_TRIGGER = y, CONFIG_IIO_SW_DEVICE = y disappear.
@debian You can run thsi in linux dir .ignore-update . And you shuold do this after make ARCH=arm64 menuconfig
$ cd /fenix/linux
$ make ARCH=arm64 kvims_defconfig
$ make ARCH=arm64 menuconfig
$ make ARCH=arm64 savedefconfig
$ cp defconfig arch/arm64/configs/kvims_defconfig
Then, run git diff in linux dir. Confirm whether your changes have taken effect.
Every time you compile, kvims_defconfig will be reloaded to .config. So you should save the changes into kvims_defconfig.
Thank you @numbqq and @Frank.
I will figure out how to setup cross compiler correctly and share it.
On the other hand fenix is really a good choice to make life easier.
So I am trying to use it to build dtb files and use updated dtb files to update my bootimage of vim3 android pie AOSP.
Currently there are two topics in my mind wanted to be clarified :]
I posted it as a reply on VIM3 GPIO’s, SPI, UART, with Android 9 Pie.