Firefly开源社区

标题: linux 在dts中添加子节点，编译通过 log中找不到节点信息 [打印本页]

作者: 513453733 时间: 2022-5-16 16:04
标题: linux 在dts中添加子节点，编译通过 log中找不到节点信息

对应的dts文件下在ic1下添加了rk628d子节点，编译通过后，烧录固件，打印出来的log中找不到添加的rk628节点信息。
dts修改如下：
&i2c1{
clock-frequency = <400000>;
status = "okay";

rk628: rk628@50{
      reg = <0x50>;
      interrupt-parent = <&gpio3>;
      interrupts = <RK_PA3 IRQ_TYPE_LEVEL_HIGH>;

      reset-gpios = <&gpio3 RK_PA5 GPIO_ACTIVE_LOW>;
      //

      status = "okay";

};
};

#include <arm/rk628.dtsi>

&rk628_combtxphy{
status = "okay";
};

&rk628_combrxphy{
status = "okay";
};

&rk628_csi {
status = "okay";
/** If the hpd output level is inverted on the circuit, * the following configuration needs to be enabled. */
/* hpd-output-inverted; */
//plugin-det-gpios = <&gpio4 RK_PB4 GPIO_ACTIVE_LOW>; //
plugin-det-gpios = <&gpio0 RK_PD6 GPIO_ACTIVE_LOW>; //

//plugin-det-gpios = <&gpio0 RK_PD6 GPIO_ACTIVE_LOW>;
//power-gpios = <&gpio0 17 GPIO_ACTIVE_HIGH>;
rockchip,camera-module-index = <0>;
rockchip,camera-module-facing = "back";
rockchip,camera-module-name = "RK628-CSI";
rockchip,camera-module-lens-name = "NC";

port {
      hdmiin_out0: endpoint {
         remote-endpoint = <&mipi_in>;
         data-lanes = <1 2 3 4>;
      };
};
};

&csi2_dphy_hw {
status = "okay";
};

&csi2_dphy0 {
status = "okay";

ports {
      #address-cells = <1>;
      #size-cells = <0>;
      port@0 {
         reg = <0>;
         #address-cells = <1>;
         #size-cells = <0>;

         mipi_in: endpoint@0 {
            reg = <0>;
            remote-endpoint = <&hdmiin_out0>;
            data-lanes = <1 2 3 4>;
         };
      };

      port@1 {
         reg = <1>;
         #address-cells = <1>;
         #size-cells = <0>;

         csidphy0_out: endpoint@0 {
            reg = <0>;
            remote-endpoint = <&isp0_in>;
         };
      };
};
};

&rkisp {
status = "okay";
};

&rkisp_mmu {
status = "okay";
};

&rkisp_vir0 {
status = "okay";

port {
      #address-cells = <1>;
      #size-cells = <0>;

      isp0_in: endpoint@0 {
         reg = <0>;
         remote-endpoint = <&csidphy0_out>;
      };
};
};

tchip_askquestions

log.zip

25.1 KB, 下载次数: 1, 下载积分: 灯泡 -1 , 经验 -1

作者: 513453733 时间: 2022-5-16 16:11
编译打包过程如下：
litong@ubuntu:~/linux/rk356x_linux_release_20211019$ ./build.sh
processing option: allff
============================================
TARGET_ARCH=arm64
TARGET_PLATFORM=rk356x
TARGET_UBOOT_CONFIG=firefly-rk3568
TARGET_SPL_CONFIG=
TARGET_KERNEL_CONFIG=firefly_linux_defconfig
TARGET_KERNEL_DTS=rk3568-firefly-aioj
TARGET_TOOLCHAIN_CONFIG=
TARGET_BUILDROOT_CONFIG=
TARGET_RECOVERY_CONFIG=
TARGET_PCBA_CONFIG=
TARGET_RAMBOOT_CONFIG=
============================================
============Start building uboot============
TARGET_UBOOT_CONFIG=firefly-rk3568
=========================================
## make firefly-rk3568_defconfig -j4
#
# configuration written to .config
#
scripts/kconfig/conf  --silentoldconfig Kconfig
  CHK    include/config.h
  GEN    include/autoconf.mk.dep
  CFG    u-boot.cfg
  CFG    tpl/u-boot.cfg
  CFG    spl/u-boot.cfg
  GEN    spl/include/autoconf.mk
  GEN    include/autoconf.mk
  GEN    tpl/include/autoconf.mk
  CHK    include/config/uboot.release
  CHK    include/generated/timestamp_autogenerated.h
  UPD    include/generated/timestamp_autogenerated.h
  CHK    include/generated/version_autogenerated.h
  CHK    include/generated/asm-offsets.h
  CHK    include/generated/generic-asm-offsets.h
  CHK    include/config.h
  CFG    u-boot.cfg
  HOSTCC  tools/mkenvimage.o
  HOSTCC  tools/image-host.o
  HOSTCC  tools/fit_image.o
  HOSTCC  tools/dumpimage.o
  HOSTCC  tools/mkimage.o
  HOSTCC  tools/rockchip/boot_merger.o
  HOSTCC  tools/rockchip/loaderimage.o
  HOSTLD  tools/loaderimage
  HOSTLD  tools/mkenvimage
  HOSTLD  tools/dumpimage
  HOSTLD  tools/mkimage
  HOSTLD  tools/boot_merger
  CC    arch/arm/cpu/armv8/fwcall.o
  LD    arch/arm/cpu/armv8/built-in.o
  CC    cmd/version.o
  CC    common/main.o
  LD    cmd/built-in.o
  LD    common/built-in.o
  CC    drivers/usb/gadget/f_fastboot.o
  CC    lib/display_options.o
  LD    drivers/usb/gadget/built-in.o
  LD    lib/built-in.o
  LD    u-boot
  OBJCOPY u-boot.srec
  OBJCOPY u-boot-nodtb.bin
make[2]: 'arch/arm/dts/rk3568-firefly.dtb' is up to date.
  SYM    u-boot.sym
start=$(/home/litong/linux/rk356x_linux_release_20211019/prebuilts/gcc/linux-x86/aarch64/gcc-linaro-6.3.1-2017.05-x86_64_aarch64-linux-gnu/bin/aarch64-linux-gnu-nm u-boot | grep __rel_dyn_start | cut -f 1 -d ' '); end=$(/home/litong/linux/rk356x_linux_release_20211019/prebuilts/gcc/linux-x86/aarch64/gcc-linaro-6.3.1-2017.05-x86_64_aarch64-linux-gnu/bin/aarch64-linux-gnu-nm u-boot | grep __rel_dyn_end | cut -f 1 -d ' '); tools/relocate-rela u-boot-nodtb.bin 0x00a00000 $start $end
  COPY u-boot.dtb
  CAT    u-boot-dtb.bin
  MKIMAGE u-boot.img
  MKIMAGE u-boot-dtb.img
  COPY u-boot.bin
  ALIGN u-boot.bin
  CC    spl/arch/arm/cpu/armv8/fwcall.o
  CC    tpl/arch/arm/mach-rockchip/tpl.o
  CC    tpl/arch/arm/cpu/armv8/fwcall.o
  LD    spl/arch/arm/cpu/armv8/built-in.o
  LD    tpl/arch/arm/cpu/armv8/built-in.o
  LD    tpl/arch/arm/mach-rockchip/built-in.o
  CC    spl/common/spl/spl.o
  LD    tpl/u-boot-tpl
  LD    spl/common/spl/built-in.o
  OBJCOPY tpl/u-boot-tpl-nodtb.bin
  COPY tpl/u-boot-tpl.bin
  COPY spl/u-boot-spl.dtb
  CC    spl/lib/display_options.o
  LD    spl/lib/built-in.o
  LD    spl/u-boot-spl
  OBJCOPY spl/u-boot-spl-nodtb.bin
  CAT    spl/u-boot-spl-dtb.bin
  COPY spl/u-boot-spl.bin
  CFGCHK  u-boot.cfg
SEC=1
pack u-boot.itb okay! Input: /home/litong/linux/rk356x_linux_release_20211019/rkbin/RKTRUST/RK3568TRUST.ini

FIT description: FIT Image with ATF/OP-TEE/U-Boot/MCU
Created:       Mon May 16 00:23:50 2022
Image 0 (uboot)
  Description:  U-Boot
  Created:    Mon May 16 00:23:50 2022
  Type:       Standalone Program
  Compression:  uncompressed
  Data Size: 1210656 Bytes = 1182.28 KiB = 1.15 MiB
  Architecture: AArch64
  Load Address: 0x00a00000
  Entry Point:  unavailable
  Hash algo: sha256
  Hash value: 5febe2d56ca5740b3333366f74bd6e228434dd82cea7f1eebdef61d2a04da190
Image 1 (atf-1)
  Description:  ARM Trusted Firmware
  Created:    Mon May 16 00:23:50 2022
  Type:       Firmware
  Compression:  uncompressed
  Data Size: 155648 Bytes = 152.00 KiB = 0.15 MiB
  Architecture: AArch64
  Load Address: 0x00040000
  Hash algo: sha256
  Hash value: fe4f274c0624c2d7e7b9aa0d5b40a3331801664bf625367702d2116dbe452466
Image 2 (atf-2)
  Description:  ARM Trusted Firmware
  Created:    Mon May 16 00:23:50 2022
  Type:       Firmware
  Compression:  uncompressed
  Data Size: 19531 Bytes = 19.07 KiB = 0.02 MiB
  Architecture: AArch64
  Load Address: 0x00068000
  Hash algo: sha256
  Hash value: 8d440360954c39a1d9a1eb604c0642e7201f4a47679272a9885cfd46205aa418
Image 3 (atf-3)
  Description:  ARM Trusted Firmware
  Created:    Mon May 16 00:23:50 2022
  Type:       Firmware
  Compression:  uncompressed
  Data Size: 8192 Bytes = 8.00 KiB = 0.01 MiB
  Architecture: AArch64
  Load Address: 0xfdcd0000
  Hash algo: sha256
  Hash value: e410275b51692587b5d09c794ae13f2dcd4d187bd6ab1eb2998bf18d44750876
Image 4 (atf-4)
  Description:  ARM Trusted Firmware
  Created:    Mon May 16 00:23:50 2022
  Type:       Firmware
  Compression:  uncompressed
  Data Size: 8192 Bytes = 8.00 KiB = 0.01 MiB
  Architecture: AArch64
  Load Address: 0xfdcc9000
  Hash algo: sha256
  Hash value: 990c53fc0167a7bcd877235f09a3ac6911841c978a4e270d89f6259ec1d36144
Image 5 (atf-5)
  Description:  ARM Trusted Firmware
  Created:    Mon May 16 00:23:50 2022
  Type:       Firmware
  Compression:  uncompressed
  Data Size: 7668 Bytes = 7.49 KiB = 0.01 MiB
  Architecture: AArch64
  Load Address: 0x00066000
  Hash algo: sha256
  Hash value: 315a4195a9f6536f971c695a79fcab4870363fc7fc97f355bd091d8d7092261a
Image 6 (optee)
  Description:  OP-TEE
  Created:    Mon May 16 00:23:50 2022
  Type:       Firmware
  Compression:  uncompressed
  Data Size: 457112 Bytes = 446.40 KiB = 0.44 MiB
  Architecture: AArch64
  Load Address: 0x08400000
  Hash algo: sha256
  Hash value: f3f0302d4cf61565726829783ee08321117a2e409b8933199ce36b3f0ea60677
Image 7 (fdt)
  Description:  U-Boot dtb
  Created:    Mon May 16 00:23:50 2022
  Type:       Flat Device Tree
  Compression:  uncompressed
  Data Size: 15115 Bytes = 14.76 KiB = 0.01 MiB
  Architecture: AArch64
  Hash algo: sha256
  Hash value: 30938731debb4198eb74f983facf8e81a2a52dfccdbac4a0a35ddeccaba3402a
Default Configuration: 'conf'
Configuration 0 (conf)
  Description:  rk3568-firefly
  Kernel:    unavailable
  Firmware:    atf-1
  FDT:       fdt
  Loadables: uboot
            atf-2
            atf-3
            atf-4
            atf-5
            optee
pack loader ok.(rk356x_spl_loader_v1.11.112.bin)(0.02)
pack loader(SPL) okay! Input: /home/litong/linux/rk356x_linux_release_20211019/rkbin/RKBOOT/RK3568MINIALL.ini

/home/litong/linux/rk356x_linux_release_20211019/u-boot
pack loader with new: spl/u-boot-spl.bin

Image(no-signed, version=0):  uboot.img (FIT with uboot, trust...) is ready
Image(no-signed):  rk356x_spl_loader_v1.11.112.bin (with spl, ddr, usbplug) is ready
pack uboot.img okay! Input: /home/litong/linux/rk356x_linux_release_20211019/rkbin/RKTRUST/RK3568TRUST.ini

Platform RK3568 is build OK, with new .config(make firefly-rk3568_defconfig -j4)
/home/litong/linux/rk356x_linux_release_20211019/prebuilts/gcc/linux-x86/aarch64/gcc-linaro-6.3.1-2017.05-x86_64_aarch64-linux-gnu/bin/aarch64-linux-gnu-
Mon May 16 00:23:50 PDT 2022
Image Type: Rockchip RK35 boot image
Init Data Size: 59392 bytes
Boot Data Size: 241664 bytes
Input:
/home/litong/linux/rk356x_linux_release_20211019/rkbin/RKBOOT/RK3568MINIALL.ini
/home/litong/linux/rk356x_linux_release_20211019/rkbin/bin/rk35/rk3568_ddr_1560MHz_v1.11.bin
/home/litong/linux/rk356x_linux_release_20211019/rkbin/bin/rk35/rk356x_spl_v1.12.bin

Pack rk3568 idblock.bin okay!

Running build_uboot succeeded.
Skipping build_loader for missing configs:  RK_LOADER_BUILD_TARGET.
============Start building kernel============
TARGET_ARCH       =arm64
TARGET_KERNEL_CONFIG =firefly_linux_defconfig
TARGET_KERNEL_DTS =rk3568-firefly-aioj
TARGET_KERNEL_CONFIG_FRAGMENT =
==========================================
/home/litong/linux/rk356x_linux_release_20211019
#
# configuration written to .config
#
scripts/kconfig/conf  --syncconfig Kconfig
  DTC    arch/arm64/boot/dts/rockchip/rk3568-firefly-aioj.dtb
  CALL scripts/checksyscalls.sh
  CHK    include/generated/compile.h
  GZIP kernel/config_data.gz
  Image:  kernel.img is ready
  CALL scripts/checksyscalls.sh
  Building modules, stage 2.
  MODPOST 0 modules
found ./arch/arm64/boot/dts/rockchip/.rk3568-firefly-aioj.dtb.dts.tmp
found ./arch/arm64/boot/dts/rockchip/.rk3568-firefly-aioj.dtb.dts.tmp
found ./arch/arm64/boot/dts/rockchip/.rk3568-firefly-aioj.dtb.dts.tmp
found ./arch/arm64/boot/dts/rockchip/.rk3568-firefly-aioj.dtb.dts.tmp
found ./arch/arm64/boot/dts/rockchip/.rk3568-firefly-aioj.dtb.dts.tmp
found ./arch/arm64/boot/dts/rockchip/.rk3568-firefly-aioj.dtb.dts.tmp
found ./arch/arm64/boot/dts/rockchip/.rk3568-firefly-aioj.dtb.dts.tmp
  Image:  resource.img (with rk3568-firefly-aioj.dtb logo.bmp logo_kernel.bmp) is ready
  Image:  boot.img (with Image ramdisk.img resource.img) is ready
  Image:  zboot.img (with Image.lz4 ramdisk.img resource.img) is ready
fdt {
kernel {
ramdisk {
resource {
FIT description: U-Boot FIT source file for arm
Created:       Mon May 16 00:24:11 2022
Image 0 (fdt)
  Description:  unavailable
  Created:    Mon May 16 00:24:11 2022
  Type:       Flat Device Tree
  Compression:  uncompressed
  Data Size: 141421 Bytes = 138.11 KiB = 0.13 MiB
  Architecture: AArch64
  Load Address: 0xffffff00
  Hash algo: sha256
  Hash value: db6ea2523a521ca322006d378709b4e874b9d8d59160e7262ce5780e160654cc
Image 1 (kernel)
  Description:  unavailable
  Created:    Mon May 16 00:24:11 2022
  Type:       Kernel Image
  Compression:  uncompressed
  Data Size: 24252424 Bytes = 23684.01 KiB = 23.13 MiB
  Architecture: AArch64
  OS:          Linux
  Load Address: 0xffffff01
  Entry Point:  0xffffff01
  Hash algo: sha256
  Hash value: d5a1f03c8b4bdca57b51dc8a58352643ec3c444cccd8dd8fd0237763c12bd53d
Image 2 (ramdisk)
  Description:  unavailable
  Created:    Mon May 16 00:24:11 2022
  Type:       RAMDisk Image
  Compression:  uncompressed
  Data Size: 8860887 Bytes = 8653.21 KiB = 8.45 MiB
  Architecture: AArch64
  OS:          Linux
  Load Address: 0xffffff02
  Entry Point:  unavailable
  Hash algo: sha256
  Hash value: 252b580d48d2afa60baba78b73045c9ccc36e894535d5683b9d1d2f4158db7e1
Image 3 (resource)
  Description:  unavailable
  Created:    Mon May 16 00:24:11 2022
  Type:       Multi-File Image
  Compression:  uncompressed
  Data Size: 399872 Bytes = 390.50 KiB = 0.38 MiB
  Hash algo: sha256
  Hash value: 44ce1d1d11f206617d1c788d05ddf77377f3621e69ac1e54c4099203f3c80278
Default Configuration: 'conf'
Configuration 0 (conf)
  Description:  unavailable
  Kernel:    kernel
  Init Ramdisk: ramdisk
  FDT:       fdt
Running build_kernel succeeded.
Skipping build_toolchain for missing configs:  RK_CFG_TOOLCHAIN.
Skipping build_buildroot for missing configs:  RK_CFG_BUILDROOT.
buildroot/output//images/rootfs.ext4 not generated?
Running build_rootfs succeeded.
==========Start building recovery==========
TARGET_RECOVERY_CONFIG=
========================================
config is
use prebuilt rk356x-recovery-arm64.cpio.gz for CPIO image
found kernel image
pack recovery.img...fdt {
kernel {
ramdisk {
resource {
FIT description: U-Boot FIT source file for arm
Created:       Mon May 16 00:24:11 2022
Image 0 (fdt)
  Description:  unavailable
  Created:    Mon May 16 00:24:11 2022
  Type:       Flat Device Tree
  Compression:  uncompressed
  Data Size: 141421 Bytes = 138.11 KiB = 0.13 MiB
  Architecture: AArch64
  Load Address: 0xffffff00
  Hash algo: sha256
  Hash value: db6ea2523a521ca322006d378709b4e874b9d8d59160e7262ce5780e160654cc
Image 1 (kernel)
  Description:  unavailable
  Created:    Mon May 16 00:24:11 2022
  Type:       Kernel Image
  Compression:  uncompressed
  Data Size: 24252424 Bytes = 23684.01 KiB = 23.13 MiB
  Architecture: AArch64
  OS:          Linux
  Load Address: 0xffffff01
  Entry Point:  0xffffff01
  Hash algo: sha256
  Hash value: d5a1f03c8b4bdca57b51dc8a58352643ec3c444cccd8dd8fd0237763c12bd53d
Image 2 (ramdisk)
  Description:  unavailable
  Created:    Mon May 16 00:24:11 2022
  Type:       RAMDisk Image
  Compression:  uncompressed
  Data Size: 6956263 Bytes = 6793.23 KiB = 6.63 MiB
  Architecture: AArch64
  OS:          Linux
  Load Address: 0xffffff02
  Entry Point:  unavailable
  Hash algo: sha256
  Hash value: 848757f81587ca00f60eeb52788b237c9cde5bb2b94663176b2393ad70038702
Image 3 (resource)
  Description:  unavailable
  Created:    Mon May 16 00:24:11 2022
  Type:       Multi-File Image
  Compression:  uncompressed
  Data Size: 399872 Bytes = 390.50 KiB = 0.38 MiB
  Hash algo: sha256
  Hash value: 44ce1d1d11f206617d1c788d05ddf77377f3621e69ac1e54c4099203f3c80278
Default Configuration: 'conf'
Configuration 0 (conf)
  Description:  unavailable
  Kernel:    kernel
  Init Ramdisk: ramdisk
  FDT:       fdt
done.
you take 0:00.86 to build recovery
====Build recovery ok!====
Running build_recovery succeeded.
Skipping build_ramboot for missing configs:  RK_CFG_RAMBOOT.
Running build_all succeeded.
/usr/bin/fakeroot
create rootfs.img...done.
create parameter...done.
/home/litong/linux/rk356x_linux_release_20211019/device/rockchip/rk356x/parameter-ubuntu-fit.txt
0x00002000@0x00004000(uboot),0x00002000@0x00006000(misc),0x00020000@0x00008000(boot),0x00020000@0x00028000(recovery),0x00010000@0x00048000(backup),0x00c00000@0x00058000(rootfs),-@0x00c58000(userdata:grow)
create misc.img...done.
warning: not found!
create uboot.img...done.
create idblock.bin...done.
uboot fotmat type is fit, so ignore trust.img...
create loader...done.
create boot.img...done.
mkupdate.sh will resize the rootfs partition.
Image: image in rockdev is ready
Make image ok!
File name is  AIO-3568J-UBUNTU20.04-GPT
Rename the file? [N|y]n
Make update.img
start to make update.img...
Resize rootfs partition size
dumpe2fs 1.44.1 (24-Mar-2018)
Android Firmware Package Tool v1.66
------ PACKAGE ------
Add file: ./package-file
Add file: ./package-file done,offset=0x800,size=0x11a,userspace=0x1
Add file: ./Image/MiniLoaderAll.bin
Add file: ./Image/MiniLoaderAll.bin done,offset=0x1000,size=0x701c0,userspace=0xe1
Add file: ./Image/parameter.txt
Add file: ./Image/parameter.txt done,offset=0x71800,size=0x1d5,userspace=0x1
Add file: ./Image/uboot.img
Add file: ./Image/uboot.img done,offset=0x72000,size=0x400000,userspace=0x800
Add file: ./Image/misc.img
Add file: ./Image/misc.img done,offset=0x472000,size=0xc000,userspace=0x18
Add file: ./Image/boot.img
Add file: ./Image/boot.img done,offset=0x47e000,size=0x2019800,userspace=0x4033
Add file: ./Image/recovery.img
Add file: ./Image/recovery.img done,offset=0x2497800,size=0x1e48800,userspace=0x3c91
Add file: ./Image/rootfs.img
Add file: ./Image/rootfs.img done,offset=0x42e0000,size=0xa744fc00,userspace=0x14e8a0
Add CRC...
Make firmware OK!
------ OK ------
********RKImageMaker ver 1.66********
Generating new image, please wait...
Writing head info...
Writing boot file...
Writing firmware...
Generating MD5 data...
MD5 data generated successfully!
New image generated successfully!
Making ./Image/update.img OK.
Make update image ok!
/home/litong/linux/rk356x_linux_release_20211019/rockdev/pack/AIO-3568J-UBUNTU20.04-GPT-20220516-0024.img
Running build_updateimg succeeded.

作者: 513453733 时间: 2022-5-18 15:41
之前的问题解决了，是添加模块的问题，现在又遇到了新的问题。

i2c找不到模块信息

作者: zyk 时间: 2022-5-19 09:00
Android调通了，可以对比一下linux相关的差异。内核差别应该不大

作者: 513453733 时间: 2022-5-19 15:11
本帖最后由 513453733 于 2022-5-19 15:12 编辑

zyk 发表于 2022-5-19 09:00
Android调通了，可以对比一下linux相关的差异。内核差别应该不大

贵厂的rk628d什么时候上线呢，你们是适配了那些soc呢

作者: zyk 时间: 2022-5-20 14:44
目前还没具体日期、主要适配RK356x、RK3399

作者: 513453733 时间: 2022-5-25 22:20

zyk 发表于 2022-5-20 14:44
目前还没具体日期、主要适配RK356x、RK3399

您好，我现在遇到了如下问题，之前我用原厂提供的for all版本的代码，修改drivers/media/i2c/Makefile，添加rk628的编译，在i2c1下添加节点，报找不到模块信息。
dts修改如下：
&i2c1 {
clock-frequency = <400000>;
status = "okay";
rk628_csi_v4l2: rk628_csi_v4l2@51 {
         reg = <0x50>;
         compatible = "rockchip,rk628-csi-v4l2";
         interrupt-parent = <&gpio3>;
         interrupts = <RK_PA3 IRQ_TYPE_LEVEL_HIGH>;

         reset-gpios = <&gpio0 RK_PD6 GPIO_ACTIVE_LOW>;
         /* hpd-output-inverted; */
         //plugin-det-gpios = <&gpio0 13 GPIO_ACTIVE_HIGH>;
         //power-gpios = <&gpio0 17 GPIO_ACTIVE_HIGH>;
         //hdcp-enable = <1>;
         status = "okay";
      };
};
log为：

之后我发现linux内核里面带有628d的驱动信息，直接用3568内核里面的驱动。（之前安卓平台验证该方案可行）
dts修改为：
&i2c1{
clock-frequency = <400000>;
status = "okay";

rk628: rk628@50{
      reg = <0x50>;
      interrupt-parent = <&gpio3>;
      interrupts = <RK_PA3 IRQ_TYPE_LEVEL_HIGH>;

      reset-gpios = <&gpio3 RK_PA5 GPIO_ACTIVE_LOW>;
      //

      status = "okay";

};
};

#include <arm/rk628.dtsi>

&rk628_combtxphy{
status = "okay";
};

&rk628_combrxphy{
status = "okay";
};

&rk628_csi {
status = "okay";
/** If the hpd output level is inverted on the circuit, * the following configuration needs to be enabled. */
/* hpd-output-inverted; */
//plugin-det-gpios = <&gpio4 RK_PB4 GPIO_ACTIVE_LOW>; //
plugin-det-gpios = <&gpio0 RK_PD6 GPIO_ACTIVE_LOW>; //

//plugin-det-gpios = <&gpio0 RK_PD6 GPIO_ACTIVE_LOW>;
//power-gpios = <&gpio0 17 GPIO_ACTIVE_HIGH>;
rockchip,camera-module-index = <0>;
rockchip,camera-module-facing = "back";
rockchip,camera-module-name = "RK628-CSI";
rockchip,camera-module-lens-name = "NC";

port {
      hdmiin_out0: endpoint {
         remote-endpoint = <&mipi_in>;
         data-lanes = <1 2 3 4>;
      };
};
};

&csi2_dphy_hw {
status = "okay";
};

&csi2_dphy0 {
status = "okay";

ports {
      #address-cells = <1>;
      #size-cells = <0>;
      port@0 {
         reg = <0>;
         #address-cells = <1>;
         #size-cells = <0>;

         mipi_in: endpoint@0 {
            reg = <0>;
            remote-endpoint = <&hdmiin_out0>;
            data-lanes = <1 2 3 4>;
         };
      };

      port@1 {
         reg = <1>;
         #address-cells = <1>;
         #size-cells = <0>;

         csidphy0_out: endpoint@0 {
            reg = <0>;
            remote-endpoint = <&isp0_in>;
         };
      };
};
};

&rkisp {
status = "okay";
};

&rkisp_mmu {
status = "okay";
};

&rkisp_vir0 {
status = "okay";

port {
      #address-cells = <1>;
      #size-cells = <0>;

      isp0_in: endpoint@0 {
         reg = <0>;
         remote-endpoint = <&csidphy0_out>;
      };
};
};

kernel config 打开如下配置：
CONFIG_MFD_RK628=Y
CONFIG_VIDEO_RK628_CSI=Y

log中找不到rk628的节点信息，即无法调用rk628d驱动

现在怀疑是i2c节点中子节点添加失败，导致以上错误，请问如何检验或者如何解决。

使用固件版本：roc-rk3568-pc-ubuntu

非常感谢。

作者: Liuth 时间: 2022-5-26 09:23
添加的节点中根本没有compatible属性，肯定是匹配不上驱动的啊
你不是安卓调通了吗，dts节点照搬过来应该就可以的吧，安卓和linux的dts基本一致的

作者: 513453733 时间: 2022-5-26 09:56

Liuth 发表于 2022-5-26 09:23
添加的节点中根本没有compatible属性，肯定是匹配不上驱动的啊
你不是安卓调通了吗，dts节点照搬过来应该 ...

compatible信息在3568自带的rk628.dtsi里，不需要在dts里面定义。

作者: 513453733 时间: 2022-5-26 10:00

513453733 发表于 2022-5-26 09:56
compatible信息在3568自带的rk628.dtsi里，不需要在dts里面定义。

之前安卓dts就是这么写的

作者: Liuth 时间: 2022-5-26 17:25
kernel config 打开 rk628 之后有没有保存到 firefly_linux_defconfig ？

作者: 513453733 时间: 2022-5-27 15:12

Liuth 发表于 2022-5-26 17:25
kernel config 打开 rk628 之后有没有保存到 firefly_linux_defconfig ？

有的。所以就很奇怪

作者: Liuth 时间: 2022-5-27 15:58
你把 include <arm/rk628.dtsi> 移到 dts 最开头试试

作者: 513453733 时间: 2022-5-27 16:56

Liuth 发表于 2022-5-27 15:58
你把 include 移到 dts 最开头试试

我之前考虑过这个情况，会报找不到节点，原因是i2c1里面已经定义了rk628d节点，但是#include 放到最前面会导致rk628.dts引用rk628节点找不到定义

MEUI{@5$$TWJGT{L1~9}XFQ.png (90.34 KB, 下载次数: 2255)

作者: Liuth 时间: 2022-5-27 17:05
log提示说 Y 对 MFD_RK628 无效
把大写Y改成小写y

作者: 513453733 时间: 2022-5-30 10:18

Liuth 发表于 2022-5-27 17:05
log提示说 Y 对 MFD_RK628 无效
把大写Y改成小写y

ok了，确实是没注意

作者: 513453733 时间: 2022-5-30 19:36
本帖最后由 513453733 于 2022-5-30 19:37 编辑

Liuth 发表于 2022-5-27 17:05
log提示说 Y 对 MFD_RK628 无效
把大写Y改成小写y

您好，现在我遇到了设备EBUSY这个问题，检查后发现配置的引脚没有被其它模块申请，

总共用到了两个引脚，分别作为中断和复位。

修改的dts为rk3568-firefly-aioj.dts

也尝试过更换其他的配置文件，并对相应的dts进行更改，log报错相同，总共尝试了
aio-3568j-ubuntu.mk
firefly-rk3568-ubuntu.mk
roc-rk3568-pc-ubuntu.mk

$FXWM(IF19G(HH8}4`1BB@T.png (23.25 KB, 下载次数: 2294)

作者: Liuth 时间: 2022-5-31 10:58
给这两个脚设置一下pinctrl，如果有问题，开机打印会有详细说明

作者: 513453733 时间: 2022-5-31 11:09

Liuth 发表于 2022-5-31 10:58
给这两个脚设置一下pinctrl，如果有问题，开机打印会有详细说明

我已经找到问题了

我在rk628_csi中添加了检测hdmi插入的引脚，这个引脚应该是固定的，我看内核里面其他的驱动检测hdmi都用的这个节点

但是我发现，在rk568-firefly-core.dtsi中该引脚已经被使用了

请问vcc5v0_host这个gpio能换别别的引脚吗？

作者: Liuth 时间: 2022-5-31 14:33
你是自己做的底板吗？
官方底板上它已经作为 USB3.0 的电源脚了，不能换

作者: 513453733 时间: 2022-5-31 16:08

Liuth 发表于 2022-5-31 14:33
你是自己做的底板吗？
官方底板上它已经作为 USB3.0 的电源脚了，不能换

换了一个配置文件，现在采用的是firefly-rk3568-ubuntu.mk
dts为rk3568-evb1-ddr4-v10-linux.dts
检查后引脚没有被其他模块申请，但是log日志依旧是ebusy

作者: 513453733 时间: 2022-5-31 16:11

513453733 发表于 2022-5-31 16:08
换了一个配置文件，现在采用的是firefly-rk3568-ubuntu.mk
dts为rk3568-evb1-ddr4-v10-linux.dts
检查 ...

似乎不是引脚被复用的问题，我之前安卓也遇到过这个问题，是直接换了rk3568-user系统就可以了

作者: 513453733 时间: 2022-5-31 16:24

513453733 发表于 2022-5-31 16:08
换了一个配置文件，现在采用的是firefly-rk3568-ubuntu.mk
dts为rk3568-evb1-ddr4-v10-linux.dts
检查 ...

似乎不是引脚被复用的问题，我之前安卓也遇到过这个问题，是直接换了rk3568-user系统就可以了

作者: Liuth 时间: 2022-5-31 16:27
官方底板上引出的GPIO资源只有4A0，3D6，3D7，用这3个试一下

作者: 513453733 时间: 2022-5-31 17:59

Liuth 发表于 2022-5-31 16:27
官方底板上引出的GPIO资源只有4A0，3D6，3D7，用这3个试一下

不行，错误没有变化，理论上讲用firefly-rk3568-ubuntu.mk这个应该就可以了
这是详细的log，麻烦您看下。

image.png (60.45 KB, 下载次数: 2365)

log (2).zip

38.68 KB, 下载次数: 1, 下载积分: 灯泡 -1 , 经验 -1

作者: Liuth 时间: 2022-6-1 09:15
你确定这套驱动是可以用的吗？看起来是驱动本身问题或者硬件问题
Linux 并没有适配过 RK628 ，已经无法提供帮助了

作者: 513453733 时间: 2022-6-1 14:31

Liuth 发表于 2022-6-1 09:15
你确定这套驱动是可以用的吗？看起来是驱动本身问题或者硬件问题
Linux 并没有适配过 RK628 ，已经无法提 ...

驱动本身是ok的，我安卓调通了，linux应该也差不多，就很奇怪。
不管怎么样，多谢了。

作者: wx__KIyr4p 时间: 2022-6-6 17:10
very good

作者: zzt999 时间: 2023-4-13 15:50
借楼，请问RK628驱动是否适配了Linux？

作者: qq2317783075 时间: 2023-4-14 09:39
提示: 作者被禁止或删除内容自动屏蔽

欢迎光临 Firefly开源社区 (https://dev.t-firefly.com/)