From: Frank Rowand <frowand.list@gmail.com>
To: Ivan Ivanov <iivanov.xz@gmail.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Peter Hurley <peter@hurleysoftware.com>,
"Krogerus, Heikki" <heikki.krogerus@linux.intel.com>,
Andy Gross <agross@codeaurora.org>,
David Brown <davidb@codeaurora.org>,
srinivas.kandagatla@linaro.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>
Subject: Re: regression: 3a878c430fd6 ("tty: serial: msm: Add TX DMA support") drops data
Date: Sat, 23 Apr 2016 10:24:00 -0700 [thread overview]
Message-ID: <571BAFB0.1080303@gmail.com> (raw)
In-Reply-To: <CAHp75Vdu6+qLHe9tTK5BE3ec5Mvz5Z0e4DvLc8ewjjVbSs-BdQ@mail.gmail.com>
On 4/21/2016 1:42 PM, Andy Shevchenko wrote:
> On Thu, Apr 21, 2016 at 4:00 AM, Frank Rowand <frowand.list@gmail.com> wrote:
>> On 4/20/2016 9:48 AM, Frank Rowand wrote:
< snip >
>> I'm not sure if the driver was in DMA or PIO mode, both
>> before the change and after. This seems like a rather
>> important question to answer, so I'll try to verify
>> that tonight.
I was in PIO mode.
I found the problem and submitted a fix.
[PATCH 0/2] tty: serial: msm_serial regression and add info message
[PATCH 1/2] tty: serial: msm_serial regression fix data corruption
[PATCH 2/2] tty: serial: msm_serial add info message
< snip >
-Frank
prev parent reply other threads:[~2016-04-23 17:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 23:23 regression: 3a878c430fd6 ("tty: serial: msm: Add TX DMA support") drops data Frank Rowand
2016-04-20 6:07 ` Ivan Ivanov
[not found] ` <EEBBF78A-33BB-4ACD-8CBF-285E1149FB9F-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-04-20 16:48 ` Frank Rowand
2016-04-21 1:00 ` Frank Rowand
2016-04-21 20:42 ` Andy Shevchenko
2016-04-23 17:24 ` Frank Rowand [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=571BAFB0.1080303@gmail.com \
--to=frowand.list@gmail.com \
--cc=agross@codeaurora.org \
--cc=andy.shevchenko@gmail.com \
--cc=davidb@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=iivanov.xz@gmail.com \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=peter@hurleysoftware.com \
--cc=srinivas.kandagatla@linaro.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).