From: Frank Rowand <frowand.list@gmail.com>
To: ivan.ivanov@linaro.org
Cc: agross@codeaurora.org, David Brown <davidb@codeaurora.org>,
srinivas.kandagatla@linaro.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
jslaby@suse.com, Rob Herring <robh+dt@kernel.org>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
linux-soc@vger.kernel.org, linux-serial@vger.kernel.org
Subject: regression: 3a878c430fd6 ("tty: serial: msm: Add TX DMA support") drops data
Date: Tue, 19 Apr 2016 16:23:29 -0700 [thread overview]
Message-ID: <5716BDF1.1010407@gmail.com> (raw)
Hi Ivan,
It appears that I have found a regression caused by
3a878c430fd6 ("tty: serial: msm: Add TX DMA support").
When I cat a file slightly larger than 126000 bytes on
the console, viewed via minicom connected to the serial
port, I am losing random chunks of data, almost always
three bytes in length. I have also seen a lost chunk
of two bytes.
I am using the 8074 dragonboard, with the dts of
arch/arm/boot/dts/qcom-apq8074-dragonboard.dts.
The dts node is serial@f991e000, which has a
compatible of "qcom,msm-uartdm-v1.4", so is_uartdm
should be UARTDM_1P4.
Do you have any thoughts on what might be going
wrong, or what I can do to debug this?
Thanks,
Frank
next reply other threads:[~2016-04-19 23:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 23:23 Frank Rowand [this message]
2016-04-20 6:07 ` regression: 3a878c430fd6 ("tty: serial: msm: Add TX DMA support") drops data 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
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=5716BDF1.1010407@gmail.com \
--to=frowand.list@gmail.com \
--cc=agross@codeaurora.org \
--cc=davidb@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=ivan.ivanov@linaro.org \
--cc=jslaby@suse.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--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).