From: Biju Das <biju.das.jz@bp.renesas.com>
To: Biju Das <biju.das.jz@bp.renesas.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Jiri Slaby <jirislaby@kernel.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: RE: [PATCH v3 3/5] tty: serial: sh-sci: Fix TE setting on SCI IP
Date: Wed, 12 Apr 2023 07:38:25 +0000 [thread overview]
Message-ID: <OS0PR01MB592262FFD02CB9E095A057DB869B9@OS0PR01MB5922.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20230331113346.170602-4-biju.das.jz@bp.renesas.com>
Hi All,
> -----Original Message-----
> From: Biju Das <biju.das.jz@bp.renesas.com>
> Sent: Friday, March 31, 2023 12:34 PM
> To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Biju Das <biju.das.jz@bp.renesas.com>; Jiri Slaby
> <jirislaby@kernel.org>; Geert Uytterhoeven <geert+renesas@glider.be>;
> Yoshinori Sato <ysato@users.sourceforge.jp>; linux-serial@vger.kernel.org;
> Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>; linux-
> renesas-soc@vger.kernel.org; stable@vger.kernel.org
> Subject: [PATCH v3 3/5] tty: serial: sh-sci: Fix TE setting on SCI IP
>
> As per the RZ/G2L users hardware manual (Rev.1.20 Sep, 2022), section
> 23.3.7 Serial Data Transmission (Asynchronous Mode) it is mentioned that the
> TE (transmit enable) must be set after setting TIE (transmit interrupt
> enable) or these 2 bits are set to 1 simultaneously by a single instruction.
> So set these 2 bits in single instruction.
>
> Fixes: 93bcefd4c6ba ("serial: sh-sci: Fix setting SCSCR_TIE while
> transferring data")
> Cc: stable@vger.kernel.org
I rechecked and the fixes tag is wrong. So, I would like to remove fixes
tag for this patch in next version.
Cheers,
Biju
> Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
> ---
> v3:
> * New patch moved here from Renesas SCI fixes patch series
> * Updated commit description
> * Moved handling of clearing TE bit as separate patch#5.
> ---
> drivers/tty/serial/sh-sci.c | 19 +++++++++++++++++--
> 1 file changed, 17 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/tty/serial/sh-sci.c b/drivers/tty/serial/sh-sci.c index
> 15743c2f3d3d..32f5c1f7d697 100644
> --- a/drivers/tty/serial/sh-sci.c
> +++ b/drivers/tty/serial/sh-sci.c
> @@ -601,6 +601,15 @@ static void sci_start_tx(struct uart_port *port)
> port->type == PORT_SCIFA || port->type == PORT_SCIFB) {
> /* Set TIE (Transmit Interrupt Enable) bit in SCSCR */
> ctrl = serial_port_in(port, SCSCR);
> +
> + /*
> + * For SCI, TE (transmit enable) must be set after setting TIE
> + * (transmit interrupt enable) or in the same instruction to
> start
> + * the transmit process.
> + */
> + if (port->type == PORT_SCI)
> + ctrl |= SCSCR_TE;
> +
> serial_port_out(port, SCSCR, ctrl | SCSCR_TIE);
> }
> }
> @@ -2600,8 +2609,14 @@ static void sci_set_termios(struct uart_port *port,
> struct ktermios *termios,
> sci_set_mctrl(port, port->mctrl);
> }
>
> - scr_val |= SCSCR_RE | SCSCR_TE |
> - (s->cfg->scscr & ~(SCSCR_CKE1 | SCSCR_CKE0));
> + /*
> + * For SCI, TE (transmit enable) must be set after setting TIE
> + * (transmit interrupt enable) or in the same instruction to
> + * start the transmitting process. So skip setting TE here for SCI.
> + */
> + if (port->type != PORT_SCI)
> + scr_val |= SCSCR_TE;
> + scr_val |= SCSCR_RE | (s->cfg->scscr & ~(SCSCR_CKE1 | SCSCR_CKE0));
> serial_port_out(port, SCSCR, scr_val | s->hscif_tot);
> if ((srr + 1 == 5) &&
> (port->type == PORT_SCIFA || port->type == PORT_SCIFB)) {
> --
> 2.25.1
prev parent reply other threads:[~2023-04-12 7:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230331113346.170602-1-biju.das.jz@bp.renesas.com>
2023-03-31 11:33 ` [PATCH v3 3/5] tty: serial: sh-sci: Fix TE setting on SCI IP Biju Das
2023-04-12 7:38 ` Biju Das [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=OS0PR01MB592262FFD02CB9E095A057DB869B9@OS0PR01MB5922.jpnprd01.prod.outlook.com \
--to=biju.das.jz@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=stable@vger.kernel.org \
--cc=ysato@users.sourceforge.jp \
/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).