On Wed, Dec 10, 2014 at 7:54 PM, Pierluigi Passaro
<pierluigi.passaro@xxxxxxxxxxxxxxxxxx> wrote:
> Hi all,
> I'm trying to use VPU code driver on iMX51 with kernel 3.18, following these
> steps:
> - disabled DVI interface
> - enabled LCD interface
> - configured and enabled VPU
> - copied iMX51 vpu firmware without header and renamed
> v4l-coda7541-imx53.bin in /lib/firmware
>
> Attached you can find the patch and the defconfig I used.
>
> The boot process hangs after loading the firmware at the first attempt of
> writing in VPU address space in the function coda_write of file
> driver/media/platform/coda/coda-common.c
>
> Is there anything preventing the coda driver to work with iMX51?
> Could anyone provide any suggestion on how investigate the problem?
I have only tested the coda driver on mx6, but looking at the
mx51.dtsi you would need this:
--- a/arch/arm/boot/dts/imx51.dtsi
+++ b/arch/arm/boot/dts/imx51.dtsi
@@ -121,6 +121,7 @@
iram: iram@1ffe0000 {
compatible = "mmio-sram";
reg = <0x1ffe0000 0x20000>;
+ clocks = <&clks IMX5_CLK_OCRAM>;
};
ipu: ipu@40000000 {
@@ -584,6 +585,18 @@
clock-names = "ipg", "ahb", "ptp";
status = "disabled";
};
+
+ vpu: vpu@83ff4000 {
+ compatible = "fsl,imx53-vpu";
+ reg = <0x83ff4000 0x1000>;
+ interrupts = <9>;
+ clocks = <&clks IMX5_CLK_VPU_REFERENCE_GATE>,
+ <&clks IMX5_CLK_VPU_GATE>;
+ clock-names = "per", "ahb";
+ resets = <&src 1>;
+ iram = <&iram>;
+ };
};
+
};
};
Also, not sure if all the required coda patches are available in
3.18, so I tried it on linux-next 20141210 on a imx51-babbage (I had
to disable USB, otherwise linux-next will hang on this board):
[ 1.368454] coda 83ff4000.vpu: Initialized CODA7541.
[ 1.373572] coda 83ff4000.vpu: Firmware version: 1.4.50
[ 1.396695] coda 83ff4000.vpu: codec registered as /dev/video[0-3]
Also, no sure if we need to distinguish mx51 versus mx53 in the coda driver.
Adding Philipp in case he can comment.
Regards,
Fabio Estevam
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
