From: Darryl <ddegraff@licor.com>
To: <linux-media@vger.kernel.org>,
<davinci-linux-open-source@linux.davincidsp.com>
Subject: davinci vpif_capture
Date: Fri, 30 Aug 2013 11:39:59 -0500 [thread overview]
Message-ID: <5220CADF.5050805@licor.com> (raw)
I am working on an application involving the davinci using the vpif. My
board file has the inputs configured to use VPIF_IF_RAW_BAYER if_type.
When my application starts up, I have it enumerate the formats
(VIDIOC_ENUM_FMT) and it indicates that the only available format is
"YCbCr4:2:2 YC Planar" (from vpif_enum_fmt_vid_cap). It looks to me
that the culprit is vpif_open().
struct channel_obj.vpifparams.iface is initialized at vpif_probe() time
in the function vpif_set_input. Open the device file (/dev/video0)
overwrites this. I suspect that it is __not__ supposed to do this,
since I don't see any method for restoring the iface.
I'm using linux-3.10.4, but the problem appears in 3.10.9, 3.11.rc7 and
a version I checked out at
https://git.kernel.org/cgit/linux/kernel/git/nsekhar/linux-davinci.git.
I have supplied a patch for 3.10.9.
diff -pubwr
linux-3.10.9-pristine/drivers/media/platform/davinci/vpif_capture.c
linux-3.10.9/drivers/media/platform/davinci/vpif_capture.c
--- linux-3.10.9-pristine/drivers/media/platform/davinci/vpif_capture.c
2013-08-20 17:40:47.000000000 -0500
+++ linux-3.10.9/drivers/media/platform/davinci/vpif_capture.c
2013-08-30 11:18:29.000000000 -0500
@@ -914,9 +914,11 @@ static int vpif_open(struct file *filep)
fh->initialized = 0;
/* If decoder is not initialized. initialize it */
if (!ch->initialized) {
+ struct vpif_interface iface = ch->vpifparams.iface;
fh->initialized = 1;
ch->initialized = 1;
memset(&(ch->vpifparams), 0, sizeof(struct vpif_params));
+ ch->vpifparams.iface = iface;
}
/* Increment channel usrs counter */
ch->usrs++;
next reply other threads:[~2013-08-30 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 16:39 Darryl [this message]
2013-08-31 11:15 ` davinci vpif_capture Prabhakar Lad
2013-09-03 11:31 ` Darryl
2013-09-04 2:46 ` Prabhakar Lad
2013-09-04 14:08 ` Darryl
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=5220CADF.5050805@licor.com \
--to=ddegraff@licor.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=linux-media@vger.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