From: Alexander Holler <holler@ahsoftware.de>
To: Robin Gong <b38343@freescale.com>,
shawn.guo@freescale.com, kernel@pengutronix.de,
robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
linux@arm.linux.org.uk
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ARM: dts: imx6dl: disable dma support for spi on i.mx6dl
Date: Mon, 15 Sep 2014 13:50:02 +0200 [thread overview]
Message-ID: <5416D26A.4080707@ahsoftware.de> (raw)
In-Reply-To: <1410327012-31185-1-git-send-email-b38343@freescale.com>
Am 10.09.2014 07:30, schrieb Robin Gong:
> There is one weird data in rxfifo after one full rx/tx transfer
> done sometimes. It looks a design issue and hard to workaround
> totally, so disable dma functhion here. And will re-enable it
> once the root cause found.
Hmm, I experience problems with DMA too but on uart3. I'm using the same
workaround for the uart (I've just commented out the dma entries in the DT).
The problem manifests itself here such, that brcm_patchram_plus hangs
while uploading the firmware to a BCM4330 connected at uart3 (reproducible).
So maybe there is a bug in the DMA-engine which not only effects SPI. Or
both drivers contain the same error in handling DMA (maybe through c&p).
But that's just specualtion from me, I haven't looked further into that
problem.
Regards,
Alexander Holler
next prev parent reply other threads:[~2014-09-15 11:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 5:30 [PATCH v2] ARM: dts: imx6dl: disable dma support for spi on i.mx6dl Robin Gong
2014-09-11 8:02 ` Shawn Guo
2014-09-15 9:41 ` Lucas Stach
2014-09-16 1:43 ` Shawn Guo
2014-09-16 3:41 ` Robin Gong
2014-09-16 9:50 ` Lucas Stach
2014-09-17 8:41 ` Robin Gong
2014-09-17 8:55 ` Lucas Stach
2014-09-17 9:19 ` Robin Gong
2014-09-17 9:19 ` Lucas Stach
2014-09-17 9:28 ` Robin Gong
2014-09-15 11:50 ` Alexander Holler [this message]
2014-09-16 3:52 ` Robin Gong
2014-09-16 9:41 ` Alexander Holler
2014-09-17 8:51 ` Robin Gong
2014-09-17 10:56 ` Alexander Holler
-- strict thread matches above, loose matches on Subject: below --
2014-10-21 1:06 Robin Gong
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=5416D26A.4080707@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=b38343@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=shawn.guo@freescale.com \
/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).