linux 驱动中调用串口,linux 串口驱动（三）

三、串口的打开

在用户空间执行open操作的时候,就会执行uart_ops->open. Uart_ops的定义如下:

tty_open=>init_dev=>initialize_tty_struct=>tty_ldisc_assign=>

将tty_ldisc_N_TTY复制给该dev

然后tty->driver->open(tty, filp);

tty->driver为上面uart_register_driver时注册的tty_driver驱动,它的操作方法集为uart_ops.

tty_fops.tty_open=>

tty->driver->open就是uart_ops.uart_open=>uart_startup=>

port->ops->startup(port)这里port的ops就是serial_pxa_pops;也这就是该物理uart口,struct uart_port的操作函数

serial_pxa_pops.startup就是serial_pxa_startup

static const struct tty_operations uart_ops = {

.open         = uart_open,

.close        = uart_close,

.write        = uart_write,

.put_char = uart_put_char,

.flush_chars  = uart_flush_chars,

.write_room   = uart_write_room,

.chars_in_buffer= uart_chars_in_buffer,

.flush_buffer = uart_flush_buffer,

.ioctl        = uart_ioctl,

.throttle = uart_throttle,

.unthrottle   = uart_unthrottle,

.send_xchar   = uart_send_xchar,

.set_termios  = uart_set_termios,

.stop         = uart_stop,

.start        = uart_start,

.hangup       = uart_hangup,

.break_ctl    = uart_break_ctl,

.wait_until_sent= uart_wait_until_sent,

#ifdef CONFIG_PROC_FS

.read_proc    = uart_read_proc,

#endif

.tiocmget = uart_tiocmget,

.tiocmset = uart_tiocmset,

};

对应open的操作接口为uart_open.代码如下:

static int uart_open(struct tty_struct *tty, struct file *filp)

{

struct uart_driver *drv = (struct uart_driver *)tty->driver->driver_state;

struct uart_state *state;

int retval, line = tty->index;

BUG_ON(!kernel_locked());

pr_debug("uart_open(%d) called\n", line);

/*

* tty->driver->num won't change, so we won't fail here with

* tty->driver_data set to something non-NULL (and therefore

* we won't get caught by uart_close()).

*/

retval = -ENODEV;

if (line >= tty->driver->num)

goto fail;

/*

* We take the semaphore inside uart_get to guarantee that we won't

* be re-entered while allocating the info structure, or while we

* request any IRQs that the driver may need.  This also has the nice

* side-effect that it delays the action of uart_hangup, so we can

* guarantee that info->tty will always contain something reasonable.

*/

state = uart_get(drv, line);

if (IS_ERR(state)) {

retval = PTR_ERR(state);

goto fail;

}

/*

* Once we set tty->driver_data here, we are guaranteed that

* uart_close() will decrement the driver module use count.

* Any failures from here onwards should not touch the count.

*/

tty->driver_d