All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Yoshihiro YUNOMAE <yoshihiro.yunomae.ez@hitachi.com>
Cc: linux-kernel@vger.kernel.org,
	Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com>,
	Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Subject: Re: [PATCH] serial/uart: Add tunable RX interrupt trigger I/F of FIFO buffers
Date: Thu, 13 Feb 2014 10:10:07 -0800	[thread overview]
Message-ID: <20140213181007.GA24155@kroah.com> (raw)
In-Reply-To: <20140206021655.8613.52786.stgit@yunodevel>

On Thu, Feb 06, 2014 at 11:16:55AM +0900, Yoshihiro YUNOMAE wrote:
> Add tunable RX interrupt trigger I/F of FIFO buffers.
> Serial devices are used as not only message communication devices but control
> or sending communication devices. For the latter uses, normally small data
> will be exchanged, so user applications want to receive data unit as soon as
> possible for real-time tendency. If we have a sensor which sends a 1 byte data
> each time and must control a device based on the sensor feedback, the RX
> interrupt should be triggered for each data.
> 
> According to HW specification of serial UART devices, RX interrupt trigger
> can be changed, but the trigger is hard-coded. For example, RX interrupt trigger
> in 16550A can be set to 1, 4, 8, or 14 bytes for HW, but current driver sets
> the trigger to only 8bytes.
> 
> This patch makes a 16550A device change RX interrupt trigger from userland.
> 
> <How to use>
> unsigned char rx_trig_byte = 1;
> fd = open(TTY_PASS, O_RDWR | O_NONBLOCK);
> ioctl(fd, TIOCSFIFOTRIG, &rx_trig_byte);
> read(fd, buf, size);
> 
> <Support uart device>
> - 16550A (1, 4, 8, or 14 bytes)
> 
> Signed-off-by: Yoshihiro YUNOMAE <yoshihiro.yunomae.ez@hitachi.com>
> ---
>  drivers/tty/serial/8250/8250_core.c |   63 +++++++++++++++++++++++++++++++++++
>  include/uapi/asm-generic/ioctls.h   |    2 +
>  2 files changed, 65 insertions(+)
> 
> diff --git a/drivers/tty/serial/8250/8250_core.c b/drivers/tty/serial/8250/8250_core.c
> index 61ecd70..f51637a 100644
> --- a/drivers/tty/serial/8250/8250_core.c
> +++ b/drivers/tty/serial/8250/8250_core.c
> @@ -2699,6 +2699,68 @@ serial8250_verify_port(struct uart_port *port, struct serial_struct *ser)
>  	return 0;
>  }
>  
> +static int convert_val2rxtrig(struct uart_8250_port *up, unsigned char val)
> +{
> +	switch (up->port.type) {
> +	case PORT_16550A:
> +		if (val == 1)
> +			return UART_FCR_R_TRIG_00;
> +		else if (val == 4)
> +			return UART_FCR_R_TRIG_01;
> +		else if (val == 8)
> +			return UART_FCR_R_TRIG_10;
> +		else if (val == 14)
> +			return UART_FCR_R_TRIG_11;
> +		break;
> +	default:
> +		pr_info("Not support RX-trigger setting for this serial %u\n",
> +			up->port.type);
> +	}
> +	return -EINVAL;
> +}
> +
> +static int set_fifo_rx_trigger(struct uart_8250_port *up,
> +			       unsigned char __user *uval)
> +{
> +	unsigned char fcr, val;
> +	int rx_trig;
> +
> +	if (copy_from_user(&val, uval, sizeof(unsigned char)))
> +		return -EFAULT;
> +
> +	rx_trig = convert_val2rxtrig(up, val);
> +	if (rx_trig < 0)
> +		return rx_trig;
> +
> +	fcr = uart_config[up->port.type].fcr;
> +	serial8250_clear_fifos(up);
> +	fcr &= ~UART_FCR_TRIGGER_MASK;
> +	fcr |= (unsigned char)rx_trig;
> +	serial_out(up, UART_FCR, fcr);
> +	return 0;
> +}
> +
> +static int
> +serial8250_ioctl(struct uart_port *port, unsigned int cmd, unsigned long arg)
> +{
> +	struct uart_8250_port *up =
> +		container_of(port, struct uart_8250_port, port);
> +	void __user *uarg = (void __user *)arg;
> +	int ret;
> +
> +	if (!(up->capabilities & UART_CAP_FIFO) || port->fifosize <= 1)
> +		return -EINVAL;
> +
> +	switch (cmd) {
> +	case TIOCSFIFORTRIG:
> +		ret = set_fifo_rx_trigger(up, uarg);
> +		break;
> +	default:
> +		ret = -ENOIOCTLCMD;
> +	}
> +	return ret;
> +}
> +
>  static const char *
>  serial8250_type(struct uart_port *port)
>  {
> @@ -2728,6 +2790,7 @@ static struct uart_ops serial8250_pops = {
>  	.request_port	= serial8250_request_port,
>  	.config_port	= serial8250_config_port,
>  	.verify_port	= serial8250_verify_port,
> +	.ioctl		= serial8250_ioctl,
>  #ifdef CONFIG_CONSOLE_POLL
>  	.poll_get_char = serial8250_get_poll_char,
>  	.poll_put_char = serial8250_put_poll_char,
> diff --git a/include/uapi/asm-generic/ioctls.h b/include/uapi/asm-generic/ioctls.h
> index 143dacb..d2e56a4 100644
> --- a/include/uapi/asm-generic/ioctls.h
> +++ b/include/uapi/asm-generic/ioctls.h
> @@ -78,6 +78,8 @@
>  #define TIOCGPTLCK	_IOR('T', 0x39, int) /* Get Pty lock state */
>  #define TIOCGEXCL	_IOR('T', 0x40, int) /* Get exclusive mode state */
>  
> +#define TIOCSFIFORTRIG	0x5441

Please define this as a "proper" ioctl command by using the correct IO*
macros.

Also, why pass a pointer to a variable, and not just the value itself?

And are you sure there's no other way to do this already?  It's odd that
no one else has ever hit this before...

thanks,

greg k-h

  reply	other threads:[~2014-02-13 18:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-06  2:16 [PATCH] serial/uart: Add tunable RX interrupt trigger I/F of FIFO buffers Yoshihiro YUNOMAE
2014-02-13 18:10 ` Greg Kroah-Hartman [this message]
2014-02-14  8:31   ` Yoshihiro YUNOMAE
2014-02-17 15:37     ` One Thousand Gnomes

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=20140213181007.GA24155@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=hidehiro.kawai.ez@hitachi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=yoshihiro.yunomae.ez@hitachi.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.