From: lauri.hintsala@bluegiga•com (Lauri Hintsala)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v2 2/3] serial: mxs-auart: add the DMA support for mx28
Date: Thu, 15 Nov 2012 13:51:52 +0200 [thread overview]
Message-ID: <50A4D758.8050602@bluegiga.com> (raw)
In-Reply-To: <50A4B1CE.5070203@freescale.com>
Hi,
On 11/15/2012 11:11 AM, Huang Shijie wrote:
>> I tested linux-next-20121114 on apx4devkit (imx28 based device) and I
>> got the same error message:
>>
>> # stty -F /dev/ttyAPP0 crtscts; microcom /dev/ttyAPP0 -s 115200
>> [ 133.710000] mxs-auart 8006a000.serial: step 1 error
>> [ 133.720000] mxs-auart 8006a000.serial: We can not start up the DMA.
> Could you test this patch?
I don't get error messages with your latest patch but the CPU freezes
after it has received first byte. Freezing happens only if flow control
(and of course DMA) is enabled. Sending data doesn't freeze the CPU. Are
you able to send data without freezing?
I used busybox's microcom to transfer data.
Lauri
next prev parent reply other threads:[~2012-11-15 11:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 10:27 [PATCH v2 0/3] serial: mxs-auart: add DMA support for auart in mx28 Huang Shijie
2012-10-24 10:27 ` [PATCH v2 1/3] serial: mxs-auart: distinguish the different SOCs Huang Shijie
2012-10-24 10:27 ` [PATCH v2 2/3] serial: mxs-auart: add the DMA support for mx28 Huang Shijie
2012-10-25 4:18 ` Vinod Koul
2012-10-25 5:50 ` Huang Shijie
2012-10-25 6:07 ` Vinod Koul
2012-10-25 9:15 ` Huang Shijie
2012-10-25 11:08 ` Vinod Koul
2012-11-05 3:16 ` Huang Shijie
2012-11-13 9:42 ` Lauri Hintsala
2012-11-15 3:20 ` Huang Shijie
2012-11-15 7:22 ` Lauri Hintsala
2012-11-15 9:11 ` Huang Shijie
2012-11-15 11:51 ` Lauri Hintsala [this message]
2012-10-24 10:27 ` [PATCH v2 3/3] ARM: dts: enable dma support for auart0 in mx28 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=50A4D758.8050602@bluegiga.com \
--to=lauri.hintsala@bluegiga$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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