From: Hugo Villeneuve <hugo@hugovil.com>
To: Vijaya Krishna Nivarthi <quic_vnivarth@quicinc.com>
Cc: agross@kernel.org, bjorn.andersson@kernel.org,
konrad.dybcio@linaro.org, gregkh@linuxfoundation.org,
jirislaby@kernel.org, bartosz.golaszewski@linaro.org,
linux-arm-msm@vger.kernel.org, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org, quic_msavaliy@quicinc.com,
dianders@chromium.org, mka@chromium.org, swboyd@chromium.org,
quic_vtanuku@quicinc.com
Subject: Re: [PATCH RESEND] tty: serial: qcom-geni-serial: Poll primary sequencer irq status after cancel_tx
Date: Wed, 9 Aug 2023 09:19:51 -0400 [thread overview]
Message-ID: <20230809091951.fbcc682d00deacd4d7b55b44@hugovil.com> (raw)
In-Reply-To: <1691583100-15689-1-git-send-email-quic_vnivarth@quicinc.com>
On Wed, 9 Aug 2023 17:41:40 +0530
Vijaya Krishna Nivarthi <quic_vnivarth@quicinc.com> wrote:
> TX is handled by primary sequencer. After cancelling primary command, poll
> primary sequencer's irq status instead of that of secondary.
Hi,
it is not clear to me if this is a bug fix or an improvement?
> While at it, also remove a couple of redundant lines that read from IRQ_EN
> register and write back same.
This should go into a separate patch.
Hugo Villeneuve.
> Fixes: 2aaa43c70778 ("tty: serial: qcom-geni-serial: add support for serial engine DMA")
> Signed-off-by: Vijaya Krishna Nivarthi <quic_vnivarth@quicinc.com>
> ---
> drivers/tty/serial/qcom_geni_serial.c | 7 ++-----
> 1 file changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/tty/serial/qcom_geni_serial.c b/drivers/tty/serial/qcom_geni_serial.c
> index 3ca5db2..b8aa4c1 100644
> --- a/drivers/tty/serial/qcom_geni_serial.c
> +++ b/drivers/tty/serial/qcom_geni_serial.c
> @@ -591,7 +591,6 @@ static void qcom_geni_serial_stop_tx_dma(struct uart_port *uport)
> {
> struct qcom_geni_serial_port *port = to_dev_port(uport);
> bool done;
> - u32 m_irq_en;
>
> if (!qcom_geni_serial_main_active(uport))
> return;
> @@ -603,12 +602,10 @@ static void qcom_geni_serial_stop_tx_dma(struct uart_port *uport)
> port->tx_remaining = 0;
> }
>
> - m_irq_en = readl(uport->membase + SE_GENI_M_IRQ_EN);
> - writel(m_irq_en, uport->membase + SE_GENI_M_IRQ_EN);
> geni_se_cancel_m_cmd(&port->se);
>
> - done = qcom_geni_serial_poll_bit(uport, SE_GENI_S_IRQ_STATUS,
> - S_CMD_CANCEL_EN, true);
> + done = qcom_geni_serial_poll_bit(uport, SE_GENI_M_IRQ_STATUS,
> + M_CMD_CANCEL_EN, true);
> if (!done) {
> geni_se_abort_m_cmd(&port->se);
> done = qcom_geni_serial_poll_bit(uport, SE_GENI_M_IRQ_STATUS,
> --
> 2.7.4
>
next prev parent reply other threads:[~2023-08-09 13:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 12:11 Vijaya Krishna Nivarthi
2023-08-09 13:19 ` Hugo Villeneuve [this message]
2023-08-09 17:21 ` Vijaya Krishna Nivarthi
2023-08-10 14:36 ` Bjorn Andersson
2023-08-14 17:44 ` Vijaya Krishna Nivarthi
2023-08-09 19:40 ` Bryan O'Donoghue
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=20230809091951.fbcc682d00deacd4d7b55b44@hugovil.com \
--to=hugo@hugovil.com \
--cc=agross@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=bjorn.andersson@kernel.org \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mka@chromium.org \
--cc=quic_msavaliy@quicinc.com \
--cc=quic_vnivarth@quicinc.com \
--cc=quic_vtanuku@quicinc.com \
--cc=swboyd@chromium.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
all inboxes | Powered by JetHome®