| 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
| ||
|
Message-ID: <4F27CA58.2020809@nvidia.com> Date: Tue, 31 Jan 2012 16:32:48 +0530 From: Laxman Dewangan <ldewangan@...dia.com> To: Stephen Warren <swarren@...dia.com> CC: "ccross@...roid.com" <ccross@...roid.com>, "olof@...om.net" <olof@...om.net>, "linux@....linux.org.uk" <linux@....linux.org.uk>, "linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [PATCH V1] arm: tegra: dma: not required to move requestor when stopping. On Wednesday 25 January 2012 02:27 AM, Stephen Warren wrote: > Laxman Dewangan wrote at Tuesday, January 24, 2012 1:11 AM: >> It is not require to move the requestor of dma to INVALID >> option before stopping dma. >> >> Signed-off-by: Laxman Dewangan<ldewangan@...dia.com> > Acked-by: Stephen Warren<swarren@...dia.com> > Tested-by: Stephen Warren<swarren@...dia.com> > > I know that Laxman has checked with the HW engineers, and they see no > reason to do this. I was originally worried about hung FIFOs preventing > an in-progress DMA from completely without the removed code, but according > to HW, that isn't a concern. > Olaf, Can it be applied if it is OK to you? Thanks, Laxman -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists