linux-imx

/*                                              -*- linux-c -*-

 * dtlk.c - DoubleTalk PC driver for Linux

 *

 * Original author: Chris Pallotta <chris@allmedia.com>

 * Current maintainer: Jim Van Zandt <jrv@vanzandt.mv.com>

 * 

 * 2000-03-18 Jim Van Zandt: Fix polling.

 *  Eliminate dtlk_timer_active flag and separate dtlk_stop_timer

 *  function.  Don't restart timer in dtlk_timer_tick.  Restart timer

 *  in dtlk_poll after every poll.  dtlk_poll returns mask (duh).

 *  Eliminate unused function dtlk_write_byte.  Misc. code cleanups.

 */

​

/* This driver is for the DoubleTalk PC, a speech synthesizer

   manufactured by RC Systems (http://www.rcsys.com/).  It was written

   based on documentation in their User's Manual file and Developer's

   Tools disk.

​

   The DoubleTalk PC contains four voice synthesizers: text-to-speech

   (TTS), linear predictive coding (LPC), PCM/ADPCM, and CVSD.  It

   also has a tone generator.  Output data for LPC are written to the

   LPC port, and output data for the other modes are written to the

   TTS port.

​

   Two kinds of data can be read from the DoubleTalk: status

   information (in response to the "\001?" interrogation command) is

   read from the TTS port, and index markers (which mark the progress

   of the speech) are read from the LPC port.  Not all models of the

   DoubleTalk PC implement index markers.  Both the TTS and LPC ports

   can also display status flags.

​

   The DoubleTalk PC generates no interrupts.

​

   These characteristics are mapped into the Unix stream I/O model as

   follows:

​

   "write" sends bytes to the TTS port.  It is the responsibility of

   the user program to switch modes among TTS, PCM/ADPCM, and CVSD.

   This driver was written for use with the text-to-speech

   synthesizer.  If LPC output is needed some day, other minor device

   numbers can be used to select among output modes.

​

   "read" gets index markers from the LPC port.  If the device does

   not implement index markers, the read will fail with error EINVAL.

​

   Status information is available using the DTLK_INTERROGATE ioctl.

​

 */

​

#include <linux/module.h>

​

#define KERNEL

#include <linux/types.h>

#include <linux/fs.h>

#include <linux/mm.h>

#include <linux/errno.h>    /* for -EBUSY */

#include <linux/ioport.h>   /* for request_region */

#include <linux/delay.h>    /* for loops_per_jiffy */

#include <linux/sched.h>

#include <linux/mutex.h>

#include <asm/io.h>     /* for inb_p, outb_p, inb, outb, etc. */

#include <linux/uaccess.h>  /* for get_user, etc. */

#include <linux/wait.h>     /* for wait_queue */