From: Fabio Estevam <festevam@gmail.com>
To: Donald Carr <sirspudd@gmail.com>
Cc: meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] duplicate drivers in the linux-fslc/linux-imx tree
Date: Thu, 17 Aug 2023 10:27:00 -0300 [thread overview]
Message-ID: <CAOMZO5Bp8UMOdk-uWOuiGcJOaEg58N9U6cDLBobiKNH5oX0qxA@mail.gmail.com> (raw)
In-Reply-To: <6viu.1692209029563173467.BqIX@lists.yoctoproject.org>
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.
prev parent reply other threads:[~2023-08-17 13:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 18:03 duplicate drivers in the linux-fslc/linux-imx tree Donald Carr
2023-08-17 13:27 ` Fabio Estevam [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOMZO5Bp8UMOdk-uWOuiGcJOaEg58N9U6cDLBobiKNH5oX0qxA@mail.gmail.com \
--to=festevam@gmail.com \
--cc=meta-freescale@lists.yoctoproject.org \
--cc=sirspudd@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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 read-only IMAP folder(s) and NNTP newsgroup(s).