From: Troy Kisky <troy.kisky@boundarydevices.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>,
Carlos Rafael Giani <dv@pseudoterminal.org>,
Ian Coolidge <ian@boundarydevices.com>
Cc: meta-freescale Mailing List <meta-freescale@yoctoproject.org>
Subject: Re: PxP support in nitrogen6x lite boards
Date: Tue, 27 Oct 2015 14:47:01 -0700 [thread overview]
Message-ID: <562FF0D5.3010806@boundarydevices.com> (raw)
In-Reply-To: <CAP9ODKpn0p6DU9L5yjUYOrLXi7OiFC_8Oan6x6W2OHctFDxxqQ@mail.gmail.com>
On 10/27/2015 1:09 PM, Otavio Salvador wrote:
> On Tue, Oct 27, 2015 at 5:41 PM, Carlos Rafael Giani
> <dv@pseudoterminal.org> wrote:
>> I noticed that nitrogen6x lite boards are based on mx6 solo / duallite SoCs.
>> So, they should support PxP.
>> Yet, PxP didn't work last time I tried it (a month ago approximately). Any
>> reason for this?
>
> Adding Troy and Ian in Cc.
>
Maybe this patch would help
commit 2ad5d6ae18000d18ca484582ef48a40637d53072
Author: Troy Kisky <troy.kisky@boundarydevices.com>
Date: Tue Oct 27 14:38:05 2015 -0700
nit6xlite_defconfig: add CONFIG_VIDEO_MXC_PXP_V4L2
Signed-off-by: Troy Kisky <troy.kisky@boundarydevices.com>
diff --git a/arch/arm/configs/nit6xlite_defconfig b/arch/arm/configs/nit6xlite_defconfig
index f558156..7fabe62 100644
--- a/arch/arm/configs/nit6xlite_defconfig
+++ b/arch/arm/configs/nit6xlite_defconfig
@@ -149,6 +149,7 @@ CONFIG_MEDIA_CAMERA_SUPPORT=y
CONFIG_V4L_PLATFORM_DRIVERS=y
CONFIG_VIDEO_MXC_OUTPUT=y
CONFIG_VIDEO_MXC_IPU_OUTPUT=y
+CONFIG_VIDEO_MXC_PXP_V4L2=y
# CONFIG_MEDIA_SUBDRV_AUTOSELECT is not set
# CONFIG_DVB_AU8522_V4L is not set
# CONFIG_DVB_TUNER_DIB0070 is not set
prev parent reply other threads:[~2015-10-27 21:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 19:41 PxP support in nitrogen6x lite boards Carlos Rafael Giani
2015-10-27 20:09 ` Otavio Salvador
2015-10-27 21:47 ` Troy Kisky [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=562FF0D5.3010806@boundarydevices.com \
--to=troy.kisky@boundarydevices.com \
--cc=dv@pseudoterminal.org \
--cc=ian@boundarydevices.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio.salvador@ossystems.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.