Jump to content

mangokid

  • Posts

    3
  • Joined

  • Last visited

  1. Hey JMCC what else would be helpful to provide? - Hardware: Nanopi-m4 + OV4689 (i2c2 + CSI1) - Build: Armbian Latest (no patching beyond existing Armbian patches for this platform) - RK3399.dtsi modified to add isp1 (isp0 already in mainline) rk3399.dtsi rk3399-nanopi-m4.dts
  2. I am trying to get a camera going on the Nanopi-m4 (I have tried another board as well with similar results). The sensor is setup in the device tree correctly and gets probed on boot. However there are some issues when loading rkisp1. [ 5.645127] rkisp1 ff920000.isp1: Adding to iommu group 5 [ 5.645695] rkisp1 ff920000.isp1: Failed to get clk 'clk_isp': -2 [ 5.645814] rkisp1: probe of ff920000.isp1 failed with error -2 My understanding with Failed to get is because it is either being used by another resource or was not defined correctly. Below are my entries in the device tree for the isp. I am using `isp1` in this case, I am assuming as well that `ispl` is locked to `csi1` where my camera is located. isp1: isp1@ff920000 { compatible = "rockchip,rk3399-cif-isp"; reg = <0x0 0xff920000 0x0 0x4000>; interrupts = <GIC_SPI 44 IRQ_TYPE_LEVEL_HIGH 0>; clocks = <&cru SCLK_ISP1>, <&cru ACLK_ISP1_WRAPPER>, <&cru HCLK_ISP1_WRAPPER>; clock-names = "isp", "aclk", "hclk"; iommus = <&isp1_mmu>; phys = <&mipi_dsi1>; phy-names = "dphy"; power-domains = <&power RK3399_PD_ISP1>; status = "okay"; ports { #address-cells = <1>; #size-cells = <0>; port@0 { reg = <0>; #address-cells = <1>; #size-cells = <0>; }; }; }; isp1_mmu: iommu@ff924000 { compatible = "rockchip,iommu"; reg = <0x0 0xff924000 0x0 0x100>, <0x0 0xff925000 0x0 0x100>; interrupts = <GIC_SPI 44 IRQ_TYPE_LEVEL_HIGH 0>; interrupt-names = "isp1_mmu"; clocks = <&cru ACLK_ISP1_WRAPPER>, <&cru HCLK_ISP1_WRAPPER>; clock-names = "aclk", "iface"; #iommu-cells = <0>; power-domains = <&power RK3399_PD_ISP1>; rockchip,disable-mmu-reset; }; &isp1_mmu { status = "okay"; }; &isp1 { status = "okay"; ports { port@0 { mipi_in_ucam1a: endpoint@0 { reg = <0>; remote-endpoint = <&ucam_out1a>; data-lanes = <1 2>; }; }; }; }; Currently I am disabling unused devices in order to make sure that this isn't related to some conflict. Any help or references would be great. I am still in the process of getting an understanding of rkisp.
  3. I am working on getting the MCP251x device running in mainline. So far the SPI and other entries in the device tree are fine. However when I bring the bus up it fails to acquire the interrupt. I think the way I am defining the interupt is incorrect. I had this working in 4.4 so i know the hardware is functioning correctly. Does anyone know how to properly define the interupt and interupt parent in this case? spi1: spi@ff1d0000 { compatible = "rockchip,rk3399-spi", "rockchip,rk3066-spi"; reg = <0x0 0xff1d0000 0x0 0x1000>; clocks = <&cru SCLK_SPI1>, <&cru PCLK_SPI1>; clock-names = "spiclk", "apb_pclk"; interrupts = <GIC_SPI 53 IRQ_TYPE_LEVEL_HIGH 0>; dmas = <&dmac_peri 12>, <&dmac_peri 13>; dma-names = "tx", "rx"; pinctrl-names = "default"; pinctrl-0 = <&spi1_clk &spi1_tx &spi1_rx &spi1_cs0>; #address-cells = <1>; #size-cells = <0>; status = "okay"; can@0 { #address-cells = <0x1>; #size-cells = <0x0>; compatible = "microchip,mcp2515"; reg = <0x0>; clocks = <&clk8m>; interupt-parent = <@gpio>; interrupts = <1 RK_PC7 2 @pcfg_pull_up>; spi-max-frequency = <10000000>; //vdd-supply = <&spmic_ldo5>; //xceiver-supply = <&spmic_ldo5>; }; };
×
×
  • Create New...