From: Johan Hovold <johan@kernel.org>
To: "Ji-Ze Hong (Peter Hong)" <hpeter@gmail.com>
Cc: johan@kernel.org, gregkh@linuxfoundation.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
tom_tsai@fintek.com.tw, peter_hong@fintek.com.tw,
hpeter+linux_kernel@gmail.com
Subject: Re: [PATCH V1 2/2] usb:serial: Implement Fintek f81534 break on/off
Date: Mon, 9 Jan 2017 16:21:48 +0100 [thread overview]
Message-ID: <20170109152148.GR21536@localhost> (raw)
In-Reply-To: <1481261974-10914-3-git-send-email-hpeter+linux_kernel@gmail.com>
On Fri, Dec 09, 2016 at 01:39:34PM +0800, Ji-Ze Hong (Peter Hong) wrote:
> Implement Fintek f81534 break on/off with LCR register
> It's the same with 16550A LCR register layout
>
> We'll add a shadow LCR variable to save the final LCR we
> had set due to the "read ep0" operations maybe slow down all
> the serial ports performance.
>
> Signed-off-by: Ji-Ze Hong (Peter Hong) <hpeter+linux_kernel@gmail.com>
> ---
> drivers/usb/serial/f81534.c | 40 ++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 40 insertions(+)
>
> diff --git a/drivers/usb/serial/f81534.c b/drivers/usb/serial/f81534.c
> index 8282a6a..1b6ba81 100644
> --- a/drivers/usb/serial/f81534.c
> +++ b/drivers/usb/serial/f81534.c
> @@ -126,8 +126,10 @@ struct f81534_serial_private {
>
> struct f81534_port_private {
> struct mutex mcr_mutex;
> + struct mutex lcr_mutex;
Using a single mutex is preferred.
> unsigned long tx_empty;
> spinlock_t msr_lock;
> + u8 shadow_lcr;
> u8 shadow_mcr;
> u8 shadow_msr;
> u8 phy_num;
> @@ -683,6 +685,7 @@ static void f81534_set_termios(struct tty_struct *tty,
> struct usb_serial_port *port,
> struct ktermios *old_termios)
> {
> + struct f81534_port_private *port_priv = usb_get_serial_port_data(port);
> u8 new_lcr = 0;
> int status;
> u32 baud;
> @@ -721,6 +724,10 @@ static void f81534_set_termios(struct tty_struct *tty,
> break;
> }
>
> + mutex_lock(&port_priv->lcr_mutex);
> + port_priv->shadow_lcr = new_lcr;
> + mutex_unlock(&port_priv->lcr_mutex);
And this is not sufficient to prevent races with break_ctl. Hold the
mutex while updating LCR in set_port_config at least (and honour the
break state).
> +
> baud = tty_get_baud_rate(tty);
> if (!baud)
> return;
> @@ -812,6 +819,35 @@ static int f81534_read_msr(struct usb_serial_port *port)
> return 0;
> }
>
> +static void f81534_set_break(struct usb_serial_port *port, bool enable)
> +{
> + struct f81534_port_private *port_priv = usb_get_serial_port_data(port);
> + int status;
> +
> + mutex_lock(&port_priv->lcr_mutex);
> +
> + if (enable)
> + port_priv->shadow_lcr |= UART_LCR_SBC;
> + else
> + port_priv->shadow_lcr &= ~UART_LCR_SBC;
> +
> + status = f81534_set_port_register(port, F81534_LINE_CONTROL_REG,
> + port_priv->shadow_lcr);
> + if (status) {
> + dev_err(&port->dev, "%s: set break failed: %x\n", __func__,
> + status);
%d, __func__ not needed.
> + }
> +
> + mutex_unlock(&port_priv->lcr_mutex);
> +}
> +
> +static void f81534_break_ctl(struct tty_struct *tty, int break_state)
> +{
> + struct usb_serial_port *port = tty->driver_data;
> +
> + f81534_set_break(port, break_state);
> +}
> +
> static int f81534_open(struct tty_struct *tty, struct usb_serial_port *port)
> {
> struct f81534_serial_private *serial_priv =
> @@ -877,6 +913,8 @@ static void f81534_close(struct usb_serial_port *port)
> }
>
> mutex_unlock(&serial_priv->urb_mutex);
> +
> + f81534_set_break(port, false);
Drop this too, and fold set_break into break_ctl above.
> }
>
> static int f81534_get_serial_info(struct usb_serial_port *port,
> @@ -1244,6 +1282,7 @@ static int f81534_port_probe(struct usb_serial_port *port)
>
> spin_lock_init(&port_priv->msr_lock);
> mutex_init(&port_priv->mcr_mutex);
> + mutex_init(&port_priv->lcr_mutex);
>
> /* Assign logic-to-phy mapping */
> port_priv->phy_num = f81534_logic_to_phy_port(port->serial, port);
> @@ -1389,6 +1428,7 @@ static int f81534_resume(struct usb_serial *serial)
> .dtr_rts = f81534_dtr_rts,
> .process_read_urb = f81534_process_read_urb,
> .ioctl = f81534_ioctl,
> + .break_ctl = f81534_break_ctl,
> .tiocmget = f81534_tiocmget,
> .tiocmset = f81534_tiocmset,
> .write_bulk_callback = f81534_write_usb_callback,
Thanks,
Johan
prev parent reply other threads:[~2017-01-09 15:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 5:39 [PATCH V1 0/2] Implement break control for F81232/F81534 Ji-Ze Hong (Peter Hong)
2016-12-09 5:39 ` [PATCH V1 1/2] usb:serial: Implement Fintek F81232 break on/off Ji-Ze Hong (Peter Hong)
2017-01-09 15:14 ` Johan Hovold
2016-12-09 5:39 ` [PATCH V1 2/2] usb:serial: Implement Fintek f81534 " Ji-Ze Hong (Peter Hong)
2017-01-09 15:21 ` Johan Hovold [this message]
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=20170109152148.GR21536@localhost \
--to=johan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hpeter+linux_kernel@gmail.com \
--cc=hpeter@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter_hong@fintek.com.tw \
--cc=tom_tsai@fintek.com.tw \
/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;
as well as URLs for NNTP newsgroup(s).