From: Dirk Behme <dirk.behme@de.bosch.com>
To: Huang Shijie <b32955@freescale.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>
Subject: Re: [PATCH 2/2] serial: imx: disable the receiver ready interrupt for imx_stop_rx
Date: Fri, 23 May 2014 08:10:36 +0200 [thread overview]
Message-ID: <537EE65C.5010700@de.bosch.com> (raw)
In-Reply-To: <1400819575-20435-2-git-send-email-b32955@freescale.com>
On 23.05.2014 06:32, Huang Shijie wrote:
> This patch disables the receiver ready interrupt for imx_stop_rx.
> It reduces the interrupt numbers when the uart is going to close
> or suspend.
>
> Signed-off-by: Huang Shijie <b32955@freescale.com>
> ---
> drivers/tty/serial/imx.c | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/tty/serial/imx.c b/drivers/tty/serial/imx.c
> index ed6cdf7..6026101 100644
> --- a/drivers/tty/serial/imx.c
> +++ b/drivers/tty/serial/imx.c
> @@ -440,6 +440,10 @@ static void imx_stop_rx(struct uart_port *port)
>
> temp = readl(sport->port.membase + UCR2);
> writel(temp & ~UCR2_RXEN, sport->port.membase + UCR2);
> +
> + /* disable the `Receiver Ready Interrrupt` */
> + temp = readl(sport->port.membase + UCR1);
> + writel(temp & ~UCR1_RRDYEN, sport->port.membase + UCR1);
> }
While this is about the RX irq, I've a slightly off-topic general
question regarding the usage of the *TX* irq in TX DMA mode:
It seems to me that the TX irq is kept enabled while the TX DMA is
running/enabled? Looking e.g. into the amba-pl011.c there it seems there
the logic is:
- Set up/start the TX DMA
- Disable the TX irq while the TX DMA is running (only waiting for the
TX DMA callback, then)
- Re-enable the TX irq in the TX DMA callback
- Let the TX irq fire, then. And if there are still data, set up the TX
DMA again.
This sounds quite more logical than the implementation in imx.c.
Or is my understanding completely wrong, here?
Thanks
Dirk
next prev parent reply other threads:[~2014-05-23 6:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 4:32 [PATCH 1/2] serial: imx: remove the DMA wait queue Huang Shijie
2014-05-23 4:32 ` [PATCH 2/2] serial: imx: disable the receiver ready interrupt for imx_stop_rx Huang Shijie
2014-05-23 6:10 ` Dirk Behme [this message]
2014-05-23 8:04 ` Huang Shijie
2014-05-30 5:52 ` Dirk Behme
2014-05-30 4:53 ` Huang Shijie
2014-05-23 4:40 ` [PATCH 1/2 rebased] serial: imx: remove the DMA wait queue Huang Shijie
2014-05-30 9:27 ` [PATCH 1/2] " Wang, Jiada (ESD)
2014-05-30 9:01 ` Huang Shijie
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=537EE65C.5010700@de.bosch.com \
--to=dirk.behme@de.bosch.com \
--cc=b32955@freescale.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@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