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,
peter_hong@fintek.com.tw,
"Ji-Ze Hong (Peter Hong)" <hpeter+linux_kernel@gmail.com>
Subject: Re: [PATCH V1 4/6] USB: serial: f81232: Add tx_empty function
Date: Wed, 28 Aug 2019 17:16:06 +0200 [thread overview]
Message-ID: <20190828151606.GK13017@localhost> (raw)
In-Reply-To: <1559789656-15847-5-git-send-email-hpeter+linux_kernel@gmail.com>
On Thu, Jun 06, 2019 at 10:54:14AM +0800, Ji-Ze Hong (Peter Hong) wrote:
> Add tx_empty() function for F81232 & F81534A series.
>
> Signed-off-by: Ji-Ze Hong (Peter Hong) <hpeter+linux_kernel@gmail.com>
> ---
> drivers/usb/serial/f81232.c | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/drivers/usb/serial/f81232.c b/drivers/usb/serial/f81232.c
> index e9470fb0d691..7d1ec8f9d168 100644
> --- a/drivers/usb/serial/f81232.c
> +++ b/drivers/usb/serial/f81232.c
> @@ -850,6 +850,24 @@ static void f81232_dtr_rts(struct usb_serial_port *port, int on)
> f81232_set_mctrl(port, 0, TIOCM_DTR | TIOCM_RTS);
> }
>
> +static bool f81232_tx_empty(struct usb_serial_port *port)
> +{
> + int status;
> + u8 tmp;
> + u8 both_empty = UART_LSR_TEMT | UART_LSR_THRE;
Doesn't TEMT being set imply that THRE is set? So you only need to check
the former?
> +
> + status = f81232_get_register(port, LINE_STATUS_REGISTER, &tmp);
> + if (status) {
> + dev_err(&port->dev, "get LSR status failed: %d\n", status);
> + return false;
> + }
> +
> + if ((tmp & both_empty) != both_empty)
> + return false;
> +
> + return true;
> +}
> +
> static int f81232_carrier_raised(struct usb_serial_port *port)
> {
> u8 msr;
> @@ -1279,6 +1297,7 @@ static struct usb_serial_driver f81232_device = {
> .tiocmget = f81232_tiocmget,
> .tiocmset = f81232_tiocmset,
> .tiocmiwait = usb_serial_generic_tiocmiwait,
> + .tx_empty = f81232_tx_empty,
> .process_read_urb = f81232_read_urb_proxy,
> .read_int_callback = f81232_read_int_callback,
> .port_probe = f81232_port_probe,
Johan
next prev parent reply other threads:[~2019-08-28 15:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 2:54 [PATCH V1 0/6] USB: serial: f81232: Add F81534A support Ji-Ze Hong (Peter Hong)
2019-06-06 2:54 ` [PATCH V1 1/6] " Ji-Ze Hong (Peter Hong)
2019-08-28 14:56 ` Johan Hovold
2019-06-06 2:54 ` [PATCH V1 2/6] USB: serial: f81232: Force F81534A with RS232 mode Ji-Ze Hong (Peter Hong)
2019-08-28 14:58 ` Johan Hovold
2019-06-06 2:54 ` [PATCH V1 3/6] USB: serial: f81232: Add generator for F81534A Ji-Ze Hong (Peter Hong)
2019-08-28 15:02 ` Johan Hovold
2019-09-02 2:59 ` Ji-Ze Hong (Peter Hong)
2019-09-20 8:15 ` Johan Hovold
2019-06-06 2:54 ` [PATCH V1 4/6] USB: serial: f81232: Add tx_empty function Ji-Ze Hong (Peter Hong)
2019-08-28 15:16 ` Johan Hovold [this message]
2019-06-06 2:54 ` [PATCH V1 5/6] USB: serial: f81232: Use devm_kzalloc Ji-Ze Hong (Peter Hong)
2019-06-06 2:54 ` [PATCH V1 6/6] USB: serial: f81232: Add gpiolib to GPIO device Ji-Ze Hong (Peter Hong)
2019-08-28 15:37 ` Johan Hovold
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=20190828151606.GK13017@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 \
/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).