From: holler@ahsoftware.de (Alexander Holler)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: dts: imx6dl: disable dma support for spi on i.mx6dl
Date: Wed, 17 Sep 2014 12:56:24 +0200 [thread overview]
Message-ID: <541968D8.2060609@ahsoftware.de> (raw)
In-Reply-To: <20140917085106.GB6369@Robin-OptiPlex-780>
Am 17.09.2014 10:51, schrieb Robin Gong:
> On Tue, Sep 16, 2014 at 11:41:55AM +0200, Alexander Holler wrote:
>> Am 16.09.2014 05:52, schrieb Robin Gong:
>>> On Mon, Sep 15, 2014 at 01:50:02PM +0200, Alexander Holler wrote:
>>>> 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).
(...)
> Yes, we just have fixed the BT issue over high speed UART last month. Suggest
> you trying our patches based on v3.10.
Thanks for the pointer. Will look if I will find these patches.
Regards,
Alexander Holler
prev parent reply other threads:[~2014-09-17 10:56 UTC|newest]
Thread overview: 16+ 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
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 [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=541968D8.2060609@ahsoftware.de \
--to=holler@ahsoftware.de \
--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;
as well as URLs for NNTP newsgroup(s).