From: Philipp Zabel <p.zabel@pengutronix.de>
To: Martin Kepplinger <martink@posteo.de>
Cc: mchehab@kernel.org, linux-media@vger.kernel.org
Subject: Re: platform: coda: how to use firmware-imx binary releases?
Date: Thu, 05 Oct 2017 10:19:38 +0200 [thread overview]
Message-ID: <1507191578.8473.1.camel@pengutronix.de> (raw)
In-Reply-To: <7dd05afd338e81d293d0424e0b8e6b6a@posteo.de>
Hi Martin,
On Thu, 2017-10-05 at 09:43 +0200, Martin Kepplinger wrote:
> I'm running a little off-topic here, but with the newest firmware too,
> my
> coda driver says "Video Data Order Adapter: Disabled" when started
> by video playback via v4l2.
This message is most likely just a result of the VDOA not supporting the
selected capture format. In vdoa_context_configure, you can see that the
VDOA only writes YUYV or NV12.
> (imx6, running linux 4.14-rc3, imx-vdoa is probed and never removed,
> a dev_info "probed" would maybe be useful for others too?)
>
> It supsequently fails with
>
> cma: cma_alloc: alloc failed, req-size: 178 pages, ret: -12
That is -ENOMEM. Is CMA enabled and sufficiently large? For example,
CONFIG_CMA=y
CONFIG_CMA_DEBUGFS=y
CONFIG_DMA_CMA=y
CONFIG_CMA_SIZE_MBYTES=256
CONFIG_CMA_SIZE_SEL_MBYTES=y
> which may or may not be related to having the vdoa (is it?), but
> shouldn't the VDOA module be active by default?
>
> # cat /sys/module/coda/parameters/disable_vdoa
> 0
I think it is not related to VDOA at all. Yes, by default the VDOA
should be activated automatically for any supported format.
regards
Philipp
next prev parent reply other threads:[~2017-10-05 8:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 8:44 platform: coda: how to use firmware-imx binary releases? Martin Kepplinger
2017-10-04 9:22 ` Philipp Zabel
2017-10-05 7:43 ` Martin Kepplinger
2017-10-05 8:19 ` Philipp Zabel [this message]
2017-10-05 11:54 ` platform: coda: how to use firmware-imx binary releases? / how to use VDOA on imx6? Martin Kepplinger
2017-10-05 14:10 ` Nicolas Dufresne
2017-10-05 14:30 ` Martin Kepplinger
2017-10-05 15:45 ` platform: coda: how to use firmware-imx binary releases? Philipp Zabel
2017-10-05 16:00 ` Martin Kepplinger
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=1507191578.8473.1.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=linux-media@vger.kernel.org \
--cc=martink@posteo.de \
--cc=mchehab@kernel.org \
/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