duplicate drivers in the linux-fslc/linux-imx tree

--15sqJrNEWSgvqtG5OmVO
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Top of the morning,

I am busy trying to move an imx6q device from 4.9 to 6.1. This has largely =
been a straight forwards process, but I have hit major hiccups trying to ge=
t my attached camera sensor (ov7251) brought up.

Part of the problem with this is that there are 2 discrete ipu-v3 implement=
ations. There is the one under:

./drivers/gpu/imx/ipu-v3

which is required by:

drivers/staging/media/imx/imx-media-dev.c:=C2=A0 =C2=A0 =C2=A0 { .compatibl=
e =3D "fsl,imx-capture-subsystem" },

(which I believe is required for me to grab an image from my attached senso=
r)

and

./drivers/mxc/ipu3

which is required by the framebuffer device (mxc_ipuv3_fb).

this can be succinctly shown here:

=E2=94=94=E2=94=80[0] <git:(cc983d0c5a23 cc983d0c5a23=E2=9C=88) > git grep =
imx6q-ipu

arch/arm/boot/dts/imx6q.dtsi:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0compatible =3D "fsl,imx6q-ipu";

arch/arm/boot/dts/imx6qdl.dtsi:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0compatible =3D "fsl,imx6q-ipu";

arch/arm/boot/dts/imx6qp.dtsi:=C2=A0 compatible =3D "fsl,imx6qp-ipu", "fsl,=
imx6q-ipu";

arch/arm/boot/dts/imx6qp.dtsi:=C2=A0 compatible =3D "fsl,imx6qp-ipu", "fsl,=
imx6q-ipu";

drivers/gpu/drm/imx/imx-drm-core.c:=C2=A0 =C2=A0 =C2=A0"fsl,imx6q-ipu",

drivers/gpu/imx/ipu-v3/ipu-common.c:=C2=A0 =C2=A0 { .compatible =3D "fsl,im=
x6q-ipu", .data =3D &ipu_type_imx6q, },

drivers/mxc/ipu3/ipu_common.c:=C2=A0 { .compatible =3D "fsl,imx6q-ipu", .da=
ta =3D &ipu_type_imx6q, },

please note both ipu commons can not be in play simultaneously and I have t=
hus far failed to get a working compromise.

Any help/insight as to what the path of least resistance is would be greatl=
y appreciated.

Yours sincerely,
Donald

--15sqJrNEWSgvqtG5OmVO
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<p>Top of the morning,<br /><br />I am busy trying to move an imx6q device =
from 4.9 to 6.1. This has largely been a straight forwards process, but I h=
ave hit major hiccups trying to get my attached camera sensor (ov7251) brou=
ght up.<br /><br />Part of the problem with this is that there are 2 discre=
te ipu-v3 implementations. There is the one under:<br /><br />./drivers/gpu=
/imx/ipu-v3<br /><br />which is required by:<br /><br />drivers/staging/med=
ia/imx/imx-media-dev.c:&nbsp; &nbsp; &nbsp; { .compatible =3D "fsl,imx-capt=
ure-subsystem" },</p>
<p>(which I believe is required for me to grab an image from my attached se=
nsor)<br /><br />and<br /><br />./drivers/mxc/ipu3<br /><br />which is requ=
ired by the framebuffer device (mxc_ipuv3_fb).<br /><br />this can be succi=
nctly shown here:</p>
<p>=E2=94=94=E2=94=80[0] &lt;git:(cc983d0c5a23 cc983d0c5a23=E2=9C=88) &gt; =
git grep imx6q-ipu</p>
<p>arch/arm/boot/dts/imx6q.dtsi:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &=
nbsp; &nbsp; &nbsp; &nbsp;compatible =3D "fsl,imx6q-ipu";</p>
<p>arch/arm/boot/dts/imx6qdl.dtsi:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 &nbsp; &nbsp; &nbsp;compatible =3D "fsl,imx6q-ipu";</p>
<p>arch/arm/boot/dts/imx6qp.dtsi:&nbsp; compatible =3D "fsl,imx6qp-ipu", "f=
sl,imx6q-ipu";</p>
<p>arch/arm/boot/dts/imx6qp.dtsi:&nbsp; compatible =3D "fsl,imx6qp-ipu", "f=
sl,imx6q-ipu";</p>
<p>drivers/gpu/drm/imx/imx-drm-core.c:&nbsp; &nbsp; &nbsp;"fsl,imx6q-ipu",<=
/p>
<p>drivers/gpu/imx/ipu-v3/ipu-common.c:&nbsp; &nbsp; { .compatible =3D "fsl=
,imx6q-ipu", .data =3D &amp;ipu_type_imx6q, },</p>
<p>drivers/mxc/ipu3/ipu_common.c:&nbsp; { .compatible =3D "fsl,imx6q-ipu", =
.data =3D &amp;ipu_type_imx6q, },<br /><br />please note both ipu commons c=
an not be in play simultaneously and I have thus far failed to get a workin=
g compromise.<br /><br />Any help/insight as to what the path of least resi=
stance is would be greatly appreciated.<br /><br />Yours sincerely,<br />Do=
nald&nbsp;</p>

--15sqJrNEWSgvqtG5OmVO--