public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: linux-media@vger.kernel.org
Subject: Getting started with OMAP3 ISP
Date: Thu, 25 Aug 2011 10:07:38 -0600	[thread overview]
Message-ID: <4E56734A.3080001@mlbassoc.com> (raw)

Background:  I have working video capture drivers based on the
TI PSP codebase from 2.6.32.  In particular, I managed to get
a driver for the TVP5150 (analogue BT656) working with that kernel.

Now I need to update to Linux 3.0, so I'm trying to get a driver
working with the rewritten ISP code.  Sadly, I'm having a hard
time with this - probably just missing something basic.

I've tried to clone the TVP514x driver which says that it works
with the OMAP3 ISP code.  I've updated it to use my decoder device,
but I can't even seem to get into that code from user land.

Here are the problems I've had so far:
   * udev doesn't create any video devices although they have been
     registered.  I see a full set in /sys/class/video4linux
        # ls /sys/class/video4linux/
        v4l-subdev0  v4l-subdev3  v4l-subdev6  video1       video4
        v4l-subdev1  v4l-subdev4  v4l-subdev7  video2       video5
        v4l-subdev2  v4l-subdev5  video0       video3       video6

     Indeed, if I create /dev/videoX by hand, I can get somewhere, but
     I don't really understand how this is supposed to work.  e.g.
       # v4l2-dbg --info /dev/video3
       Driver info:
           Driver name   : ispvideo
           Card type     : OMAP3 ISP CCP2 input
           Bus info      : media
           Driver version: 1
           Capabilities  : 0x04000002
                   Video Output
                   Streaming

   * If I try to grab video, the ISP layer gets a ton of warnings, but
     I never see it call down into my driver, e.g. to check the current
     format, etc.  I have some of my own code from before which fails
     miserably (not a big surprise given the hack level of those programs).
     I tried something off-the-shelf which also fails pretty bad:
       # ffmpeg -t 10 -f video4linux2 -s 720x480 -r 30 -i /dev/video2 junk.mp4

I've read through Documentation/video4linux/omap3isp.txt without learning
much about what might be wrong.

Can someone give me some ideas/guidance, please?

Thanks

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

             reply	other threads:[~2011-08-25 16:15 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-25 16:07 Gary Thomas [this message]
2011-08-29 10:49 ` Getting started with OMAP3 ISP Laurent Pinchart
2011-08-30 14:08   ` Gary Thomas
2011-08-30 14:18     ` Gary Thomas
2011-08-30 14:20       ` Laurent Pinchart
2011-08-30 14:56         ` Gary Thomas
2011-08-30 15:48           ` Laurent Pinchart
2011-08-30 16:07           ` Enrico
2011-08-30 16:23             ` Gary Thomas
2011-08-30 16:36               ` Enrico
2011-08-30 16:48                 ` Gary Thomas
2011-08-30 21:19               ` Sakari Ailus
2011-08-30 22:45   ` Gary Thomas
2011-08-30 22:50     ` Laurent Pinchart
2011-08-31  0:07       ` Gary Thomas
2011-08-31  8:13         ` Laurent Pinchart
2011-08-31 10:56           ` Gary Thomas
2011-08-31 11:00             ` Laurent Pinchart
2011-08-31 12:01               ` Gary Thomas
2011-08-31 15:15                 ` Laurent Pinchart
2011-08-31 15:19                   ` Gary Thomas
2011-08-31 16:25                   ` Enrico
2011-08-31 16:33                     ` Laurent Pinchart
2011-08-31 22:34                       ` Gary Thomas
2011-09-01  8:11                         ` Laurent Pinchart
2011-09-01  9:51                       ` Enrico
2011-09-01  9:55                         ` Laurent Pinchart
2011-09-01 10:24                           ` Enrico
2011-09-01 14:12                             ` Enrico
2011-09-01 14:24                               ` Laurent Pinchart
2011-09-01 12:50                         ` Gary Thomas
2011-09-01 13:26                           ` Laurent Pinchart
2011-09-01 15:16                             ` Gary Thomas
2011-09-01 16:14                               ` Enrico
2011-09-01 17:24                                 ` Enrico
2011-09-01 18:14                                   ` Laurent Pinchart
2011-09-01 18:18                                     ` Gary Thomas
2011-09-02  8:09                                       ` Laurent Pinchart
2011-09-02  9:02                                     ` Enrico
2011-09-02 11:27                                       ` Laurent Pinchart
2011-09-05 16:37                                         ` Enrico
2011-09-06  8:48                                           ` Laurent Pinchart
2011-09-06  9:04                                             ` Enrico
     [not found]                                           ` <201109061049.32114.laurent.pinchart@ideasonboard.com>
2011-09-06  9:10                                             ` Enrico
  -- strict thread matches above, loose matches on Subject: below --
2011-10-05 10:46 Adam Pledger

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=4E56734A.3080001@mlbassoc.com \
    --to=gary@mlbassoc.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