gpu & vpu probe issue

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

gpu & vpu probe issue

ソリューションへジャンプ
2,233件の閲覧回数
zohanlin
Contributor IV

Dear guys,

 

I have one OS yocto 2.4 rock (kernel 4.9.88) which runs in imx6q, the gpu and vpu work well.

So I try another OS yocto 3.1 Zeus(kernel 5.4.47)which runs in imx6q, the gpu and vpu don't work.

Log as below

 

[    3.850835] galcore 130000.gpu: ignoring dependency for device, assuming no driver
[    3.858990] mxc_vpu 2040000.vpu_fsl: ignoring dependency for device, assuming no driver

 

 

 

Could somebody help me?

 

 

 

ラベル(4)
0 件の賞賛
返信
1 解決策
2,174件の閲覧回数
zohanlin
Contributor IV

Hi igor,

I found the reason that is my custom board remove the pmic.

So I comment some dts item as below

/*
&reg_arm {
       vin-supply = <&sw1a_reg>;
};

&reg_pu {
       vin-supply = <&sw1c_reg>;
};

&reg_soc {
       vin-supply = <&sw1c_reg>;
};
*/

 

Now the GPU & VPU can work well.

元の投稿で解決策を見る

5 返答(返信)
2,226件の閲覧回数
igorpadykov
NXP Employee
NXP Employee

Hi zohanlin

 

one can try to test vpu,gpu on nxp sabresd reference board with Demo Image

i.MX 6QuadPlus, i.MX 6Quad, i.MX 6DualLite, i.MX 6SoloX Boards​

https://www.nxp.com/design/software/embedded-software/i-mx-software/embedded-linux-for-i-mx-applicat...

 

Best regards
igor

0 件の賞賛
返信
2,175件の閲覧回数
zohanlin
Contributor IV

Hi igor,

I found the reason that is my custom board remove the pmic.

So I comment some dts item as below

/*
&reg_arm {
       vin-supply = <&sw1a_reg>;
};

&reg_pu {
       vin-supply = <&sw1c_reg>;
};

&reg_soc {
       vin-supply = <&sw1c_reg>;
};
*/

 

Now the GPU & VPU can work well.

2,199件の閲覧回数
zohanlin
Contributor IV

I found a post about the issue.

https://community.nxp.com/t5/i-MX-Processors/Problem-with-galcore-GPU-module-on-imx6-Solo/td-p/10560... 

 

Bio_TICFSL said : Sorry and yes the issue is on DTBs.

Is it really?

 

0 件の賞賛
返信
2,207件の閲覧回数
zohanlin
Contributor IV

Hi igor,

My board is not EVK, so I could not test the demo image.

I downloaded linux-imx 5.4.70, and the version has the same problem.

Could you have other suggestions?

 

0 件の賞賛
返信
2,227件の閲覧回数
zohanlin
Contributor IV

I tried to modify dts and set #power-domain-cells by <1>

--------------------------------------------------------------------------

pd_pu: power-domain@1 {
reg = <1>;
#power-domain-cells = <1>;
power-supply = <&reg_pu>;
clocks = <&clks IMX6QDL_CLK_GPU3D_CORE>,
<&clks IMX6QDL_CLK_GPU3D_SHADER>,
<&clks IMX6QDL_CLK_GPU2D_CORE>,
<&clks IMX6QDL_CLK_GPU2D_AXI>,
<&clks IMX6QDL_CLK_OPENVG_AXI>,
<&clks IMX6QDL_CLK_VPU_AXI>;
};

 

Now the log is

root@imx6qsabresd:~# dmesg | grep -i "gpu"
[ 3.628942] OF: /soc/gpu@00130000: #power-domain-cells = 1 found -1
[ 4.328302] galcore: probe of 130000.gpu failed with error -22


root@imx6qsabresd:~# dmesg | grep -i "gal"
[ 3.291714] egalax_ts 1-0004: Failed to switch to I2C interface
[ 3.298098] egalax_ts 2-0004: Failed to switch to I2C interface
[ 3.636502] Galcore version 6.4.3.p0.286725
[ 4.291168] [galcore]: Feature database is not found,chipModel=0x0, chipRevision=0x0, productID=0x0, ecoID=0x0, customerID=0x0
[ 4.328302] galcore: probe of 130000.gpu failed with error -22

root@imx6qsabresd:~# dmesg | grep -i "vpu"
[ 4.334554] OF: /soc/aips-bus@2000000/vpu_fsl@2040000: #power-domain-cells = 1 found -1
[ 4.343296] mxc_vpu 2040000.vpu_fsl: VPU initialized

0 件の賞賛
返信