From: Thierry Reding <thierry.reding@gmail.com>
To: Krishna Yarlagadda <kyarlagadda@nvidia.com>
Cc: gregkh@linuxfoundation.org, robh+dt@kernel.org,
mark.rutland@arm.com, jonathanh@nvidia.com, ldewangan@nvidia.com,
jslaby@suse.com, linux-serial@vger.kernel.org,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org,
Shardar Shariff Md <smohammed@nvidia.com>
Subject: Re: [PATCH 08/14] serial: tegra: check for FIFO mode enabled status
Date: Tue, 13 Aug 2019 12:03:57 +0200 [thread overview]
Message-ID: <20190813100357.GM1137@ulmo> (raw)
In-Reply-To: <1565609303-27000-9-git-send-email-kyarlagadda@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 4831 bytes --]
On Mon, Aug 12, 2019 at 04:58:17PM +0530, Krishna Yarlagadda wrote:
> Chips prior to Tegra186 needed delay of 3 UART clock cycles to avoid
> data loss. This issue is fixed in Tegra186 and a new flag is added to
> check if fifo mode is enabled. chip data updated to check if this flag
> is available for a chip. Tegra186 has new compatible to enable this
> flag.
>
> Signed-off-by: Shardar Shariff Md <smohammed@nvidia.com>
> Signed-off-by: Krishna Yarlagadda <kyarlagadda@nvidia.com>
> ---
> drivers/tty/serial/serial-tegra.c | 52 ++++++++++++++++++++++++++++++++++-----
> 1 file changed, 46 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/tty/serial/serial-tegra.c b/drivers/tty/serial/serial-tegra.c
> index 7ab81bb..e0379d9 100644
> --- a/drivers/tty/serial/serial-tegra.c
> +++ b/drivers/tty/serial/serial-tegra.c
> @@ -72,6 +72,8 @@
> #define TEGRA_TX_PIO 1
> #define TEGRA_TX_DMA 2
>
> +#define TEGRA_UART_FCR_IIR_FIFO_EN 0x40
> +
> /**
> * tegra_uart_chip_data: SOC specific data.
> *
> @@ -84,6 +86,7 @@ struct tegra_uart_chip_data {
> bool tx_fifo_full_status;
> bool allow_txfifo_reset_fifo_mode;
> bool support_clk_src_div;
> + bool fifo_mode_enable_status;
> };
>
> struct tegra_uart_port {
> @@ -263,6 +266,22 @@ static void tegra_uart_wait_sym_time(struct tegra_uart_port *tup,
> tup->current_baud));
> }
>
> +static int tegra_uart_is_fifo_mode_enabled(struct tegra_uart_port *tup)
I think this is a bad name. "is" makes it sound like this will return a
boolean value. Also, this doesn't really check whether FIFO mode is
enabled, but rather it waits for the FIFO mode to become enabled.
Perhaps, then, a better name would be
tegra_uart_wait_fifo_mode_enabled()
?
> +{
> + unsigned long iir;
> + unsigned int tmout = 100;
> +
> + do {
> + iir = tegra_uart_read(tup, UART_IIR);
> + if (iir & TEGRA_UART_FCR_IIR_FIFO_EN)
> + return 0;
> + udelay(1);
> + } while (--tmout);
> + dev_err(tup->uport.dev, "FIFO mode not enabled\n");
I'd push this out to callers. That way this function becomes useful in
situations where you don't want to output an error.
> +
> + return -EIO;
-ETIMEDOUT?
Thierry
> +}
> +
> static void tegra_uart_fifo_reset(struct tegra_uart_port *tup, u8 fcr_bits)
> {
> unsigned long fcr = tup->fcr_shadow;
> @@ -282,6 +301,8 @@ static void tegra_uart_fifo_reset(struct tegra_uart_port *tup, u8 fcr_bits)
> tegra_uart_write(tup, fcr, UART_FCR);
> fcr |= UART_FCR_ENABLE_FIFO;
> tegra_uart_write(tup, fcr, UART_FCR);
> + if (tup->cdata->fifo_mode_enable_status)
> + tegra_uart_is_fifo_mode_enabled(tup);
> }
>
> /* Dummy read to ensure the write is posted */
> @@ -918,12 +939,19 @@ static int tegra_uart_hw_init(struct tegra_uart_port *tup)
> /* Dummy read to ensure the write is posted */
> tegra_uart_read(tup, UART_SCR);
>
> - /*
> - * For all tegra devices (up to t210), there is a hardware issue that
> - * requires software to wait for 3 UART clock periods after enabling
> - * the TX fifo, otherwise data could be lost.
> - */
> - tegra_uart_wait_cycle_time(tup, 3);
> + if (tup->cdata->fifo_mode_enable_status) {
> + ret = tegra_uart_is_fifo_mode_enabled(tup);
> + if (ret < 0)
> + return ret;
> + } else {
> + /*
> + * For all tegra devices (up to t210), there is a hardware
> + * issue that requires software to wait for 3 UART clock
> + * periods after enabling the TX fifo, otherwise data could
> + * be lost.
> + */
> + tegra_uart_wait_cycle_time(tup, 3);
> + }
>
> /*
> * Initialize the UART with default configuration
> @@ -1294,12 +1322,21 @@ static struct tegra_uart_chip_data tegra20_uart_chip_data = {
> .tx_fifo_full_status = false,
> .allow_txfifo_reset_fifo_mode = true,
> .support_clk_src_div = false,
> + .fifo_mode_enable_status = false,
> };
>
> static struct tegra_uart_chip_data tegra30_uart_chip_data = {
> .tx_fifo_full_status = true,
> .allow_txfifo_reset_fifo_mode = false,
> .support_clk_src_div = true,
> + .fifo_mode_enable_status = false,
> +};
> +
> +static struct tegra_uart_chip_data tegra186_uart_chip_data = {
> + .tx_fifo_full_status = true,
> + .allow_txfifo_reset_fifo_mode = false,
> + .support_clk_src_div = true,
> + .fifo_mode_enable_status = true,
> };
>
> static const struct of_device_id tegra_uart_of_match[] = {
> @@ -1310,6 +1347,9 @@ static const struct of_device_id tegra_uart_of_match[] = {
> .compatible = "nvidia,tegra20-hsuart",
> .data = &tegra20_uart_chip_data,
> }, {
> + .compatible = "nvidia,tegra186-hsuart",
> + .data = &tegra186_uart_chip_data,
> + }, {
> },
> };
> MODULE_DEVICE_TABLE(of, tegra_uart_of_match);
> --
> 2.7.4
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-08-13 10:03 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 11:28 [PATCH 00/14] serial: tegra: Tegra186 support and fixes Krishna Yarlagadda
2019-08-12 11:28 ` Krishna Yarlagadda
2019-08-12 11:28 ` [PATCH 01/14] serial: tegra: add internal loopback functionality Krishna Yarlagadda
2019-08-12 11:28 ` Krishna Yarlagadda
2019-08-13 9:38 ` Thierry Reding
2019-08-12 11:28 ` [PATCH 02/14] serial: tegra: add support to ignore read Krishna Yarlagadda
2019-08-12 11:28 ` Krishna Yarlagadda
2019-08-13 9:42 ` Thierry Reding
2019-08-27 9:29 ` Krishna Yarlagadda
2019-08-12 11:28 ` [PATCH 03/14] serial: tegra: avoid reg access when clk disabled Krishna Yarlagadda
2019-08-12 11:28 ` Krishna Yarlagadda
2019-08-13 9:45 ` Thierry Reding
2019-08-27 9:29 ` Krishna Yarlagadda
2019-08-12 11:28 ` [PATCH 04/14] serial: tegra: protect IER against LCR.DLAB Krishna Yarlagadda
2019-08-12 11:28 ` Krishna Yarlagadda
2019-08-13 9:46 ` Thierry Reding
2019-08-12 11:28 ` [PATCH 05/14] serial: tegra: flush the RX fifo on frame error Krishna Yarlagadda
2019-08-12 11:28 ` Krishna Yarlagadda
2019-08-13 9:48 ` Thierry Reding
2019-08-27 9:29 ` Krishna Yarlagadda
2019-08-12 11:28 ` [PATCH 06/14] serial: tegra: report error to upper tty layer Krishna Yarlagadda
2019-08-12 11:28 ` Krishna Yarlagadda
2019-08-13 9:52 ` Thierry Reding
2019-08-27 9:29 ` Krishna Yarlagadda
2019-08-12 11:28 ` [PATCH 07/14] serial: tegra: add compatible for new chips Krishna Yarlagadda
2019-08-12 11:28 ` Krishna Yarlagadda
2019-08-13 9:55 ` Thierry Reding
2019-08-27 9:29 ` Krishna Yarlagadda
2019-08-12 11:28 ` [PATCH 08/14] serial: tegra: check for FIFO mode enabled status Krishna Yarlagadda
2019-08-12 11:28 ` Krishna Yarlagadda
2019-08-13 10:03 ` Thierry Reding [this message]
2019-08-27 9:29 ` Krishna Yarlagadda
2019-08-12 11:28 ` [PATCH 09/14] serial: tegra: set maximum num of uart ports to 8 Krishna Yarlagadda
2019-08-12 11:28 ` Krishna Yarlagadda
2019-08-13 10:19 ` Thierry Reding
2019-08-27 9:30 ` Krishna Yarlagadda
2019-08-12 11:28 ` [PATCH 10/14] serial: tegra: add support to use 8 bytes trigger Krishna Yarlagadda
2019-08-12 11:28 ` Krishna Yarlagadda
2019-08-19 20:29 ` Jon Hunter
2019-08-19 20:29 ` Jon Hunter
2019-08-27 9:31 ` Krishna Yarlagadda
2019-08-12 11:28 ` [PATCH 11/14] serial: tegra: DT for Adjusted baud rates Krishna Yarlagadda
2019-08-12 11:28 ` Krishna Yarlagadda
2019-08-13 10:24 ` Thierry Reding
2019-08-27 9:31 ` Krishna Yarlagadda
2019-08-12 11:28 ` [PATCH 12/14] serial: tegra: add support to adjust baud rate Krishna Yarlagadda
2019-08-12 11:28 ` Krishna Yarlagadda
2019-08-12 11:28 ` [PATCH 13/14] serial: tegra: report clk rate errors Krishna Yarlagadda
2019-08-12 11:28 ` Krishna Yarlagadda
2019-08-12 11:28 ` [PATCH 14/14] serial: tegra: Add PIO mode support Krishna Yarlagadda
2019-08-12 11:28 ` Krishna Yarlagadda
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=20190813100357.GM1137@ulmo \
--to=thierry.reding@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=jslaby@suse.com \
--cc=kyarlagadda@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=smohammed@nvidia.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.