dv1394.h 12 KB
Newer Older
1
/*
2
 * DV input/output over IEEE 1394 on OHCI chips
3 4 5 6 7 8 9 10
 *   Copyright (C)2001 Daniel Maas <dmaas@dcine.com>
 *     receive, proc_fs by Dan Dennedy <dan@dennedy.org>
 *
 * based on:
 *   video1394.h - driver for OHCI 1394 boards
 *   Copyright (C)1999,2000 Sebastien Rougeaux <sebastien.rougeaux@anu.edu.au>
 *                          Peter Schlaile <udbz@rz.uni-karlsruhe.de>
 *
11
 * This file is part of Libav.
12
 *
13
 * Libav is free software; you can redistribute it and/or
14 15
 * modify it under the terms of the GNU Lesser General Public
 * License as published by the Free Software Foundation; either
16
 * version 2.1 of the License, or (at your option) any later version.
17
 *
18
 * Libav is distributed in the hope that it will be useful,
19
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
20 21
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
 * Lesser General Public License for more details.
22
 *
23
 * You should have received a copy of the GNU Lesser General Public
24
 * License along with Libav; if not, write to the Free Software
25
 * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
26 27
 */

28 29
#ifndef AVDEVICE_DV1394_H
#define AVDEVICE_DV1394_H
30

31
#define DV1394_DEFAULT_CHANNEL 63
32 33 34 35
#define DV1394_DEFAULT_CARD    0
#define DV1394_RING_FRAMES     20

#define DV1394_WIDTH  720
Alex Beregszaszi's avatar
1000l  
Alex Beregszaszi committed
36 37
#define DV1394_NTSC_HEIGHT 480
#define DV1394_PAL_HEIGHT 576
38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61

/* This is the public user-space interface. Try not to break it. */

#define DV1394_API_VERSION 0x20011127

/* ********************
   **                **
   **   DV1394 API   **
   **                **
   ********************

   There are two methods of operating the DV1394 DV output device.

   1)

   The simplest is an interface based on write(): simply write
   full DV frames of data to the device, and they will be transmitted
   as quickly as possible. The FD may be set for non-blocking I/O,
   in which case you can use select() or poll() to wait for output
   buffer space.

   To set the DV output parameters (e.g. whether you want NTSC or PAL
   video), use the DV1394_INIT ioctl, passing in the parameters you
   want in a struct dv1394_init.
62

63 64
   Example 1:
         To play a raw .DV file:   cat foo.DV > /dev/dv1394
65
         (cat will use write() internally)
66 67 68

   Example 2:
           static struct dv1394_init init = {
69
              0x63,        (broadcast channel)
70
              4,           (four-frame ringbuffer)
71 72
              DV1394_NTSC, (send NTSC video)
              0, 0         (default empty packet rate)
73 74
           }

75
           ioctl(fd, DV1394_INIT, &init);
76

77 78 79
           while(1) {
                  read( <a raw DV file>, buf, DV1394_NTSC_FRAME_SIZE );
                  write( <the dv1394 FD>, buf, DV1394_NTSC_FRAME_SIZE );
80 81 82 83 84
           }

   2)

   For more control over buffering, and to avoid unnecessary copies
85 86 87
   of the DV data, you can use the more sophisticated the mmap() interface.
   First, call the DV1394_INIT ioctl to specify your parameters,
   including the number of frames in the ringbuffer. Then, calling mmap()
88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108
   on the dv1394 device will give you direct access to the ringbuffer
   from which the DV card reads your frame data.

   The ringbuffer is simply one large, contiguous region of memory
   containing two or more frames of packed DV data. Each frame of DV data
   is 120000 bytes (NTSC) or 144000 bytes (PAL).

   Fill one or more frames in the ringbuffer, then use the DV1394_SUBMIT_FRAMES
   ioctl to begin I/O. You can use either the DV1394_WAIT_FRAMES ioctl
   or select()/poll() to wait until the frames are transmitted. Next, you'll
   need to call the DV1394_GET_STATUS ioctl to determine which ringbuffer
   frames are clear (ready to be filled with new DV data). Finally, use
   DV1394_SUBMIT_FRAMES again to send the new data to the DV output.


   Example: here is what a four-frame ringbuffer might look like
            during DV transmission:


         frame 0   frame 1   frame 2   frame 3

109
        *--------------------------------------*
110 111
        | CLEAR   | DV data | DV data | CLEAR  |
        *--------------------------------------*
112
                   <ACTIVE>
113

114
        transmission goes in this direction --->>>
115 116 117 118 119 120 121 122


   The DV hardware is currently transmitting the data in frame 1.
   Once frame 1 is finished, it will automatically transmit frame 2.
   (if frame 2 finishes before frame 3 is submitted, the device
   will continue to transmit frame 2, and will increase the dropped_frames
   counter each time it repeats the transmission).

123

124 125
   If you called DV1394_GET_STATUS at this instant, you would
   receive the following values:
126

127
                  n_frames          = 4
128 129 130
                  active_frame      = 1
                  first_clear_frame = 3
                  n_clear_frames    = 2
131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156

   At this point, you should write new DV data into frame 3 and optionally
   frame 0. Then call DV1394_SUBMIT_FRAMES to inform the device that
   it may transmit the new frames.

   ERROR HANDLING

   An error (buffer underflow/overflow or a break in the DV stream due
   to a 1394 bus reset) can be detected by checking the dropped_frames
   field of struct dv1394_status (obtained through the
   DV1394_GET_STATUS ioctl).

   The best way to recover from such an error is to re-initialize
   dv1394, either by using the DV1394_INIT ioctl call, or closing the
   file descriptor and opening it again. (note that you must unmap all
   ringbuffer mappings when closing the file descriptor, or else
   dv1394 will still be considered 'in use').

   MAIN LOOP

   For maximum efficiency and robustness against bus errors, you are
   advised to model the main loop of your application after the
   following pseudo-code example:

   (checks of system call return values omitted for brevity; always
   check return values in your code!)
157

158
   while( frames left ) {
159

160 161 162 163 164 165 166
    struct pollfd *pfd = ...;

    pfd->fd = dv1394_fd;
    pfd->revents = 0;
    pfd->events = POLLOUT | POLLIN; (OUT for transmit, IN for receive)

    (add other sources of I/O here)
167

168 169 170 171
    poll(pfd, 1, -1); (or select(); add a timeout if you want)

    if(pfd->revents) {
         struct dv1394_status status;
172

173 174
         ioctl(dv1394_fd, DV1394_GET_STATUS, &status);

175 176
         if(status.dropped_frames > 0) {
              reset_dv1394();
177
         } else {
178 179
              int i;
              for (i = 0; i < status.n_clear_frames; i++) {
180
                  copy_DV_frame();
181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196
              }
         }
    }
   }

   where copy_DV_frame() reads or writes on the dv1394 file descriptor
   (read/write mode) or copies data to/from the mmap ringbuffer and
   then calls ioctl(DV1394_SUBMIT_FRAMES) to notify dv1394 that new
   frames are availble (mmap mode).

   reset_dv1394() is called in the event of a buffer
   underflow/overflow or a halt in the DV stream (e.g. due to a 1394
   bus reset). To guarantee recovery from the error, this function
   should close the dv1394 file descriptor (and munmap() all
   ringbuffer mappings, if you are using them), then re-open the
   dv1394 device (and re-map the ringbuffer).
197

198 199 200 201 202 203 204
*/


/* maximum number of frames in the ringbuffer */
#define DV1394_MAX_FRAMES 32

/* number of *full* isochronous packets per DV frame */
205 206
#define DV1394_NTSC_PACKETS_PER_FRAME 250
#define DV1394_PAL_PACKETS_PER_FRAME  300
207 208 209

/* size of one frame's worth of DV data, in bytes */
#define DV1394_NTSC_FRAME_SIZE (480 * DV1394_NTSC_PACKETS_PER_FRAME)
210
#define DV1394_PAL_FRAME_SIZE  (480 * DV1394_PAL_PACKETS_PER_FRAME)
211 212 213 214 215


/* ioctl() commands */

enum {
216 217
        /* I don't like using 0 as a valid ioctl() */
        DV1394_INVALID = 0,
218 219


220 221 222 223
        /* get the driver ready to transmit video.
           pass a struct dv1394_init* as the parameter (see below),
           or NULL to get default parameters */
        DV1394_INIT,
224 225


226 227
        /* stop transmitting video and free the ringbuffer */
        DV1394_SHUTDOWN,
228 229


230 231 232 233 234
        /* submit N new frames to be transmitted, where
           the index of the first new frame is first_clear_buffer,
           and the index of the last new frame is
           (first_clear_buffer + N) % n_frames */
        DV1394_SUBMIT_FRAMES,
235 236


237 238 239 240
        /* block until N buffers are clear (pass N as the parameter)
           Because we re-transmit the last frame on underrun, there
           will at most be n_frames - 1 clear frames at any time */
        DV1394_WAIT_FRAMES,
241

242 243 244 245 246
        /* capture new frames that have been received, where
           the index of the first new frame is first_clear_buffer,
           and the index of the last new frame is
           (first_clear_buffer + N) % n_frames */
        DV1394_RECEIVE_FRAMES,
247 248


249
        DV1394_START_RECEIVE,
250 251


252 253
        /* pass a struct dv1394_status* as the parameter (see below) */
        DV1394_GET_STATUS,
254 255 256 257 258
};



enum pal_or_ntsc {
259 260
        DV1394_NTSC = 0,
        DV1394_PAL
261 262 263 264 265 266 267
};




/* this is the argument to DV1394_INIT */
struct dv1394_init {
268 269
        /* DV1394_API_VERSION */
        unsigned int api_version;
270

271 272
        /* isochronous transmission channel to use */
        unsigned int channel;
273

274 275 276
        /* number of frames in the ringbuffer. Must be at least 2
           and at most DV1394_MAX_FRAMES. */
        unsigned int n_frames;
277

278 279
        /* send/receive PAL or NTSC video format */
        enum pal_or_ntsc format;
280

281
        /* the following are used only for transmission */
282

283 284 285 286
        /* set these to zero unless you want a
           non-default empty packet rate (see below) */
        unsigned long cip_n;
        unsigned long cip_d;
287

288 289 290
        /* set this to zero unless you want a
           non-default SYT cycle offset (default = 3 cycles) */
        unsigned int syt_offset;
291 292 293 294 295 296 297 298
};

/* NOTE: you may only allocate the DV frame ringbuffer once each time
   you open the dv1394 device. DV1394_INIT will fail if you call it a
   second time with different 'n_frames' or 'format' arguments (which
   would imply a different size for the ringbuffer). If you need a
   different buffer size, simply close and re-open the device, then
   initialize it with your new settings. */
299

300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315
/* Q: What are cip_n and cip_d? */

/*
  A: DV video streams do not utilize 100% of the potential bandwidth offered
  by IEEE 1394 (FireWire). To achieve the correct rate of data transmission,
  DV devices must periodically insert empty packets into the 1394 data stream.
  Typically there is one empty packet per 14-16 data-carrying packets.

  Some DV devices will accept a wide range of empty packet rates, while others
  require a precise rate. If the dv1394 driver produces empty packets at
  a rate that your device does not accept, you may see ugly patterns on the
  DV output, or even no output at all.

  The default empty packet insertion rate seems to work for many people; if
  your DV output is stable, you can simply ignore this discussion. However,
  we have exposed the empty packet rate as a parameter to support devices that
316
  do not work with the default rate.
317 318 319 320 321

  The decision to insert an empty packet is made with a numerator/denominator
  algorithm. Empty packets are produced at an average rate of CIP_N / CIP_D.
  You can alter the empty packet rate by passing non-zero values for cip_n
  and cip_d to the INIT ioctl.
322

323 324 325 326 327
 */



struct dv1394_status {
328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353
        /* this embedded init struct returns the current dv1394
           parameters in use */
        struct dv1394_init init;

        /* the ringbuffer frame that is currently being
           displayed. (-1 if the device is not transmitting anything) */
        int active_frame;

        /* index of the first buffer (ahead of active_frame) that
           is ready to be filled with data */
        unsigned int first_clear_frame;

        /* how many buffers, including first_clear_buffer, are
           ready to be filled with data */
        unsigned int n_clear_frames;

        /* how many times the DV stream has underflowed, overflowed,
           or otherwise encountered an error, since the previous call
           to DV1394_GET_STATUS */
        unsigned int dropped_frames;

        /* N.B. The dropped_frames counter is only a lower bound on the actual
           number of dropped frames, with the special case that if dropped_frames
           is zero, then it is guaranteed that NO frames have been dropped
           since the last call to DV1394_GET_STATUS.
        */
354 355 356
};


357
#endif /* AVDEVICE_DV1394_H */