From: R00091@freescale.com (Nguyen Dinh-R00091)
To: linux-arm-kernel@lists.infradead.org
Subject: SDMA on imx35
Date: Wed, 26 Jan 2011 19:57:04 +0000 [thread overview]
Message-ID: <56132A77AB93C141BF06E6B96CA6CFEA126F19@039-SN1MPN1-005.039d.mgd.msft.net> (raw)
In-Reply-To: <201101261224.37260.alexander.stein@systec-electronic.com>
Hi Alexander,
>-----Original Message-----
From: linux-arm-kernel-bounces@lists.infradead.org [mailto:linux-arm-kernel-
>bounces at lists.infradead.org] On Behalf Of Alexander Stein
>Sent: Wednesday, January 26, 2011 5:25 AM
>To: linux-arm-kernel at lists.infradead.org
>Subject: SDMA on imx35
>
>Hello,
>
>I'm currently fiddling on SDMA support for the uart driver on my imx35 rev2.
>TX is working great, no problems so far. But on RX I never get the SDMA
>interrupt that the request has been processed.
>So I'm wondering if the UART-DMS-Script in ROM is actually working. Has
>anybody get this to work (doesn't matter if linux-2.6 from git or kernel from
>freescale)?
I'm also looking at enabling SDMA support for the imx-uart on MX51. Should be the same driver. Unfortunately, I'm not at your stage of _working_ yet, so I can't comment on your RX problem. I know that internally, we haven't had any issue with RX on uart with SDMA, but FSL's SDMA implementation is quite different(part of my problem is taking the time to understand how to use dmaengine) from kernel.org.
Do you have a patch to share?
Thanks,
Dinh
>
>Best regards,
>Alexander
>
>_______________________________________________
>linux-arm-kernel mailing list
>linux-arm-kernel at lists.infradead.org
>http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2011-01-26 19:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 11:24 SDMA on imx35 Alexander Stein
2011-01-26 19:57 ` Nguyen Dinh-R00091 [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=56132A77AB93C141BF06E6B96CA6CFEA126F19@039-SN1MPN1-005.039d.mgd.msft.net \
--to=r00091@freescale.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.