meta-freescale.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
* duplicate drivers in the linux-fslc/linux-imx tree
@ 2023-08-16 18:03 Donald Carr
  2023-08-17 13:27 ` [meta-freescale] " Fabio Estevam
  0 siblings, 1 reply; 2+ messages in thread
From: Donald Carr @ 2023-08-16 18:03 UTC (permalink / raw)
  To: meta-freescale

[-- Attachment #1: Type: text/plain, Size: 1626 bytes --]

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 get my attached camera sensor (ov7251) brought up.

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

./drivers/gpu/imx/ipu-v3

which is required by:

drivers/staging/media/imx/imx-media-dev.c:      { .compatible = "fsl,imx-capture-subsystem" },

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

and

./drivers/mxc/ipu3

which is required by the framebuffer device (mxc_ipuv3_fb).

this can be succinctly shown here:

└─[0] <git:(cc983d0c5a23 cc983d0c5a23✈) > git grep imx6q-ipu

arch/arm/boot/dts/imx6q.dtsi:                   compatible = "fsl,imx6q-ipu";

arch/arm/boot/dts/imx6qdl.dtsi:                 compatible = "fsl,imx6q-ipu";

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

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

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

drivers/gpu/imx/ipu-v3/ipu-common.c:    { .compatible = "fsl,imx6q-ipu", .data = &ipu_type_imx6q, },

drivers/mxc/ipu3/ipu_common.c:  { .compatible = "fsl,imx6q-ipu", .data = &ipu_type_imx6q, },

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

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

Yours sincerely,
Donald

[-- Attachment #2: Type: text/html, Size: 1918 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [meta-freescale] duplicate drivers in the linux-fslc/linux-imx tree
  2023-08-16 18:03 duplicate drivers in the linux-fslc/linux-imx tree Donald Carr
@ 2023-08-17 13:27 ` Fabio Estevam
  0 siblings, 0 replies; 2+ messages in thread
From: Fabio Estevam @ 2023-08-17 13:27 UTC (permalink / raw)
  To: Donald Carr; +Cc: meta-freescale

Hi Donald,

On Wed, Aug 16, 2023 at 3:03 PM Donald Carr <sirspudd@gmail.com> wrote:
>
> 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 get my attached camera sensor (ov7251) brought up.
>
> Part of the problem with this is that there are 2 discrete ipu-v3 implementations. There is the one under:
>
> ./drivers/gpu/imx/ipu-v3
>
> which is required by:
>
> drivers/staging/media/imx/imx-media-dev.c:      { .compatible = "fsl,imx-capture-subsystem" },
>
> (which I believe is required for me to grab an image from my attached sensor)

Correct.

>
> and
>
> ./drivers/mxc/ipu3
>
> which is required by the framebuffer device (mxc_ipuv3_fb).

This is a custom NXP driver.

I suggest you use the standard driver provided by the mainline kernel.

imx6qdl-sabresd has camera supported:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/arch/arm/boot/dts/imx6qdl-sabresd.dtsi?h=v6.1.46#n318

Here is the documentation for it:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/Documentation/admin-guide/media/imx.rst?h=v6.1.46

Hope this helps.


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2023-08-17 13:27 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-08-16 18:03 duplicate drivers in the linux-fslc/linux-imx tree Donald Carr
2023-08-17 13:27 ` [meta-freescale] " Fabio Estevam

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).