linux-kernel - Re: commit 271e1b86e691 is breaking DMA uart on SoCFPGA

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 11 Feb 2016 14:27:51 +0530
From:	Vinod Koul <vinod.koul@...el.com>
To:	Dinh Nguyen <dinguyen@...nsource.altera.com>
Cc:	shawn.lin@...kchips.com, Addy Ke <addy.ke@...k-chips.com>,
	boojin.kim@...sung.com, wxt@...k-chips.com,
	dmaengine@...r.kernel.org, olof Johansson <olof@...om.net>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: commit 271e1b86e691 is breaking DMA uart on SoCFPGA

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