From: Vinod Koul <vinod.koul@intel.com>
To: Dinh Nguyen <dinguyen@opensource.altera.com>
Cc: shawn.lin@rockchips.com, Addy Ke <addy.ke@rock-chips.com>,
boojin.kim@samsung.com, wxt@rock-chips.com,
dmaengine@vger.kernel.org, olof Johansson <olof@lixom.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: commit 271e1b86e691 is breaking DMA uart on SoCFPGA
Date: Thu, 11 Feb 2016 14:27:51 +0530 [thread overview]
Message-ID: <20160211085748.GW19598@localhost> (raw)
In-Reply-To: <56BBB201.7060004@opensource.altera.com>
On Wed, Feb 10, 2016 at 03:56:17PM -0600, Dinh Nguyen wrote:
> Hi Vinod,
>
> It appears that commit 271e1b86e691 "dmaengine: pl330: add quirk for
> broken no flushp" is breaking uart dma on SoCFPGA. This commit is in
> linux-next(next-20160210).
>
> Doing a bisect pointed to commit 271e1b86e691, but I had to also revert
> the following commits (86a8ce7d4103 "dmaengine: pl330: add max burst for
> dmaengine") and (848e9776fee4 "dmaengine: pl330: support burst mode for
> dev-to-mem and mem-to-dev transmit") as well because the build would
> fail if I only revert 271e1b86e691.
>
> The SoCFPGA platform is being tested on Olof's board farm and is failing
> multi_v7_defconfig build because the PL330 DMA is enabled in this defconfig.
>
> After doing reverts of those 3 commits, the socfpga platform is able
> boot completely again with multi_v7_defconfig.
Okay I am removing this topic from next. Also I can drop the series unless
someone sends me a fix in couple of days..
Thanks
--
~Vinod
next prev parent reply other threads:[~2016-02-11 8:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 21:56 commit 271e1b86e691 is breaking DMA uart on SoCFPGA Dinh Nguyen
2016-02-11 8:57 ` Vinod Koul [this message]
2016-02-17 11:12 ` Bartlomiej Zolnierkiewicz
2016-02-18 16:07 ` Alexander Kochetkov
2016-02-23 15:14 ` Dinh Nguyen
2016-02-24 6:01 ` Caesar Wang
2016-02-24 13:24 ` Bartlomiej Zolnierkiewicz
2016-02-25 0:29 ` Caesar Wang
2016-02-24 13:20 ` Bartlomiej Zolnierkiewicz
2016-02-19 6:51 ` Alexander Kochetkov
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=20160211085748.GW19598@localhost \
--to=vinod.koul@intel.com \
--cc=addy.ke@rock-chips.com \
--cc=boojin.kim@samsung.com \
--cc=dinguyen@opensource.altera.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=shawn.lin@rockchips.com \
--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 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.