From: Greg KH <gregkh@linuxfoundation.org>
To: adriana@arista.com
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.rg,
ilpo.jarvinnen@linux.intel.com,
andriy.shevchenko@linux.intel.com, jirislaby@kernel.org,
john.ogness@linutronix.de
Subject: Re: [PATCH v2] serial: 8250 dw: clear FIFO before writting LCR
Date: Wed, 20 Aug 2025 07:59:01 +0200 [thread overview]
Message-ID: <2025082028-lagging-finalize-c2e3@gregkh> (raw)
In-Reply-To: <20250819191314.3452283-1-adriana@arista.com>
On Tue, Aug 19, 2025 at 12:13:14PM -0700, adriana@arista.com wrote:
> The USR register may report that UART is busy even if TX/TX FIFO is already
> empty so we will loop until all USR[0] (UART busy status) is cleared and USR[1]
> TX FIFO is empty (RX FIFO bits should be 0 in this case).
> Keeping the same timeout of 20ms as measurements with the 9600 baud when
> the console was busy it took max 1.9ms to get the UART free state.
>
> ---
> Changes in v2:
> - Updated the mailing list.
>
> Signed-off-by: Adriana Nicolae <adriana@arista.com>
> ---
Your signed-off-by needs to be above the --- line. Take a look at a few
of the thousands of examples on the mailing list for how to get this
right.
One tiny comment:
> diff --git a/include/uapi/linux/serial_core.h b/include/uapi/linux/serial_core.h
> index 9c007a106330..8386436b813f 100644
> --- a/include/uapi/linux/serial_core.h
> +++ b/include/uapi/linux/serial_core.h
> @@ -231,6 +231,9 @@
> /* Sunplus UART */
> #define PORT_SUNPLUS 123
>
> +/* Synopsys DesignWare */
> +#define PORT_DWAPB 124
Why do you need to export this value to userspace?
thanks,
greg k-h
next prev parent reply other threads:[~2025-08-20 5:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 19:13 [PATCH v2] serial: 8250 dw: clear FIFO before writting LCR adriana
2025-08-20 4:01 ` Jiri Slaby
2025-08-20 4:06 ` Jiri Slaby
2025-08-20 5:59 ` Greg KH [this message]
2025-08-20 6:33 ` kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2025-08-19 19:06 adriana
2025-08-20 6:00 ` Greg KH
2025-08-20 6:10 ` Greg KH
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=2025082028-lagging-finalize-c2e3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=adriana@arista.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ilpo.jarvinnen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.rg \
--cc=linux-serial@vger.kernel.org \
/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.