From: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
To: Jiri Slaby <jirislaby@kernel.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>
Subject: RE: [PATCH v2] serial: sh-sci: Stop dmaengine transfer in sci_stop_tx()
Date: Fri, 4 Jun 2021 10:28:19 +0000 [thread overview]
Message-ID: <TY2PR01MB3692BB5BFDA1C8C305992330D83B9@TY2PR01MB3692.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <19b2a786-0b32-f26c-efd9-2f5dbd9894aa@kernel.org>
Hi Jiri,
Thank you for your review!
> From: Jiri Slaby, Sent: Friday, June 4, 2021 7:22 PM
>
> On 04. 06. 21, 11:57, Yoshihiro Shimoda wrote:
> > Stop dmaengine transfer in sci_stop_tx(). Otherwise, the following
> > message is possible output when system enters suspend and while
> > transferring data, because clearing TIE bit in SCSCR is not able to
> > stop any dmaengine transfer.
> >
> > sh-sci e6550000.serial: ttySC1: Unable to drain transmitter
> >
> > Notes:
> > - sci_dma_stop_tx() is a macro in the .h file because struct sci_port
> > is declared in the .c file and #ifdef should be in the .h file.
> > - This patch uses dmaengine_terminate_async() so that we can apply
> > this into longterm kernel v4.9.x or later.
> >
> > Fixes: 73a19e4c0301 ("serial: sh-sci: Add DMA support.")
> > Signed-off-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
> > ---
<snip>
> > diff --git a/drivers/tty/serial/sh-sci.c b/drivers/tty/serial/sh-sci.c
> > index 4baf1316ea72..3793cf9f352c 100644
> > --- a/drivers/tty/serial/sh-sci.c
> > +++ b/drivers/tty/serial/sh-sci.c
> > @@ -610,6 +610,8 @@ static void sci_stop_tx(struct uart_port *port)
> > ctrl &= ~SCSCR_TIE;
> >
> > serial_port_out(port, SCSCR, ctrl);
> > +
> > + sci_dma_stop_tx(port);
> > }
> >
> > static void sci_start_rx(struct uart_port *port)
> > diff --git a/drivers/tty/serial/sh-sci.h b/drivers/tty/serial/sh-sci.h
> > index c0dfe4382898..435c674af1ce 100644
> > --- a/drivers/tty/serial/sh-sci.h
> > +++ b/drivers/tty/serial/sh-sci.h
> > @@ -174,3 +174,19 @@ enum {
> > (((port)->type == PORT_SCI) ? SCI_TDxE_CLEAR : SCIF_TDxE_CLEAR)
> > #define SCxSR_BREAK_CLEAR(port) \
> > (((port)->type == PORT_SCI) ? SCI_BREAK_CLEAR : SCIF_BREAK_CLEAR)
> > +
> > +#ifdef CONFIG_SERIAL_SH_SCI_DMA
> > +#define sci_dma_stop_tx(port) \
>
> Ouch. First, why this needs to be in a header?
The v1 patch [1] putted #ifdef in .c file, so that I got feedback from Greg like below:
"Please do not put #ifdef in .c files, this should be possible without that."
[1]
https://lore.kernel.org/linux-renesas-soc/TY2PR01MB3692C545672195370487FA60D83C9@TY2PR01MB3692.jpnprd01.prod.outlook.com/T/#md5b58540e26a28ef1acddfc326c62bfde73e8e8a
> Second, please don't do this by a macro.
I got it. I'll try to fix this issue somehow...
Best regards,
Yoshihiro Shimoda
next prev parent reply other threads:[~2021-06-04 10:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 9:57 [PATCH v2] serial: sh-sci: Stop dmaengine transfer in sci_stop_tx() Yoshihiro Shimoda
2021-06-04 10:21 ` Jiri Slaby
2021-06-04 10:28 ` Yoshihiro Shimoda [this message]
2021-06-04 11:38 ` gregkh
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=TY2PR01MB3692BB5BFDA1C8C305992330D83B9@TY2PR01MB3692.jpnprd01.prod.outlook.com \
--to=yoshihiro.shimoda.uh@renesas.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--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 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).