From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] tty: serial: msm: Disable restoring Rx interrupts for DMA Mode
Date: Thu, 2 Jun 2016 11:37:18 -0700 [thread overview]
Message-ID: <20160602183718.GL28218@codeaurora.org> (raw)
In-Reply-To: <9c627293b1a13f5e71ba1a61c3bc2bfa@codeaurora.org>
On 06/02, charanya at codeaurora.org wrote:
> On 2016-05-26 04:16, Stephen Boyd wrote:
> >
> >Ok, but what's the exact sequence of events that happens? I think
> >we unlock the spinlock in the dma completion handler and then the
> >txlev interrupt runs? At that point we may have more data to push
> >out and then rx stale handling runs and corrupts the fifo state?
> >
> >I was hoping for some sort of CPU sequence of events like:
> >
> > CPU0 CPU1
> > ---- ----
> >
> > msm_start_rx_dma()
> > msm_complete_rx_dma()
> > spin_unlock_irqrestore(&port->lock)
> > msm_uart_irq()
> > msm_handle_rx_dm()
> > <Read from FIFO and breaks>
> >
> >This patch seems correct, but the commit text isn't fully
> >describing the sequence of events that causes this to happen, so
> >it's taking a while to convince myself that this patch fixes
> >anything.
>
>
> The sequence of events is as mentioned. When the TXLEV interrupt
> occurs after the
> spinlock is unlocked, the rx stale handling runs since the
> interrupts are restored
> and hence it corrupts the fifo state.
Ok, care to put such information into the commit text of the
patch and resend then please? It will help us later to recall
what the actual problem was.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2016-06-02 18:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 16:09 [PATCH] tty: serial: msm: Disable restoring Rx interrupts for DMA Mode Abhishek Sahu
2016-05-12 1:41 ` Stephen Boyd
2016-05-12 5:02 ` Andy Gross
2016-05-13 9:18 ` charanya at codeaurora.org
2016-05-25 22:46 ` Stephen Boyd
2016-06-02 9:07 ` charanya at codeaurora.org
2016-06-02 18:37 ` Stephen Boyd [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=20160602183718.GL28218@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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).