From: Vinod Koul <vinod.koul@intel.com>
To: Caesar Wang <wxt@rock-chips.com>
Cc: Heiko Stuebner <heiko@sntech.de>,
Sonny Rao <sonnyrao@chromium.org>,
shawn.lin@rock-chips.com, dianders@chromium.org,
linux-rockchip@lists.infradead.org,
Addy Ke <addy.ke@rock-chips.com>, Olof Johansson <olof@lixom.net>,
Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v7 9/9] spi: rockchip: modify DMA max burst to 1
Date: Tue, 9 Feb 2016 09:04:29 +0530 [thread overview]
Message-ID: <20160209033428.GJ19598@localhost> (raw)
In-Reply-To: <1453460812-8498-10-git-send-email-wxt@rock-chips.com>
On Fri, Jan 22, 2016 at 07:06:52PM +0800, Caesar Wang wrote:
> From: Addy Ke <addy.ke@rock-chips.com>
>
> Generic dma controller on Rockchips' platform cannot support
> DMAFLUSHP instruction which make dma to flush the req of non-aligned
> or non-multiple of what we need. That will cause an unrecoverable
> dma bus error. The saftest way is to set dma max burst to 1.
Applied, thanks
--
~Vinod
next prev parent reply other threads:[~2016-02-09 3:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 11:06 [PATCH v7 0/9] Fix broken DMAFLUSHP on Rockchips platform Caesar Wang
[not found] ` <1453460812-8498-1-git-send-email-wxt-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-01-22 11:06 ` [PATCH v7 9/9] spi: rockchip: modify DMA max burst to 1 Caesar Wang
2016-02-09 3:34 ` Vinod Koul [this message]
2016-02-01 6:56 ` [PATCH v7 0/9] Fix broken DMAFLUSHP on Rockchips platform Caesar Wang
[not found] ` <56AF01B6.6030204-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-02-08 3:11 ` Vinod Koul
2016-02-08 9:27 ` Heiko Stuebner
2016-02-08 13:14 ` Vinod Koul
2016-02-08 14:02 ` Mark Brown
2016-02-08 22:21 ` Heiko Stuebner
2016-02-09 3:21 ` Vinod Koul
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=20160209033428.GJ19598@localhost \
--to=vinod.koul@intel.com \
--cc=addy.ke@rock-chips.com \
--cc=broonie@kernel.org \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=olof@lixom.net \
--cc=shawn.lin@rock-chips.com \
--cc=sonnyrao@chromium.org \
--cc=wxt@rock-chips.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).