From: sylvain.rochet@finsecur.com (Sylvain Rochet)
To: linux-arm-kernel@lists.infradead.org
Subject: at91: serial: Can't use DMA on 4.x kernels in RS-485 mode on at91sam9x5
Date: Tue, 4 Apr 2017 22:32:50 +0200 [thread overview]
Message-ID: <20170404203249.GA4416@gradator.net> (raw)
In-Reply-To: <DM5PR05MB2954D56C2E266AF16B250ACCBB0B0@DM5PR05MB2954.namprd05.prod.outlook.com>
Hi Bryan,
On Tue, Apr 04, 2017 at 08:28:34PM +0000, Bryan Evenson wrote:
>
> With the 3.10 kernel, I had to use the TX DMA only. For some reason
> receive wouldn't work for me with the DMA. Now with the latest on the
> linux-4.4-at91 branch I can't use the TX DMA. The data is transmitted
> correctly out the USART (verified on a receiving device), but then the
> return message is not received. I verified the same results when both
> RX&TX DMA was enabled and only when the TX DMA was enabled. If I use
> only the RX DMA, everything works fine if I have only one device on
> the RS-485 port. As soon as I daisy chain more than one device on an
> RS-485 port, then I start dropping messages. If I turn off both the
> RX and TX DMA, then all data transfers work just fine.
>
> I'd like to get both TX and RX DMA working for all three RS-485 ports.
> Anyone have any suggestions for what to look at to get DMA working
> while in RS-485 mode? I'm planning to start trying a git bisect, but
> given these are different branches I wasn't sure how well that was
> going to work.
Did you check that you didn't run out of available DMA channels on each
DMA controller ? AT91SAM9G25 unfortunately doesn't have much of them.
Sylvain
next prev parent reply other threads:[~2017-04-04 20:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 20:28 at91: serial: Can't use DMA on 4.x kernels in RS-485 mode on at91sam9x5 Bryan Evenson
2017-04-04 20:32 ` Sylvain Rochet [this message]
2017-04-04 20:47 ` Bryan Evenson
2017-04-07 14:22 ` Bryan Evenson
2017-04-11 18:32 ` Bryan Evenson
2017-04-11 18:59 ` Alexandre Belloni
2017-04-11 20:13 ` Bryan Evenson
2017-04-11 20:25 ` Alexandre Belloni
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=20170404203249.GA4416@gradator.net \
--to=sylvain.rochet@finsecur.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox