linux-kernel - RE: [PATCH V2] ARM: tegra: apbio access using dma for tegra20 only

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]

Message-ID: <4B31D3FCDA299E46AB481AFD049E47C97D8A45C1B9@BGMAIL01.nvidia.com>
Date:	Wed, 20 Jun 2012 18:14:24 +0530
From:	Bandi Krishna Chaitanya <bandik@...dia.com>
To:	Laxman Dewangan <ldewangan@...dia.com>,
	"swarren@...dotorg.org" <swarren@...dotorg.org>,
	"ccross@...roid.com" <ccross@...roid.com>,
	"olof@...om.net" <olof@...om.net>
CC:	"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH V2] ARM: tegra: apbio access using dma for tegra20 only

On Wednesday 20 June 2012 06:06 PM, Chaitanya Bandi wrote:
> 
> The Tegra20 HW issue with accessing APBIO registers (such as fuse registers)
> directly from the CPU concurrently with APB DMA accesses has been fixed in
> Tegra30 and later chips.
> 
> Access these registers directly from the CPU on Tegra30 and later, and apply
> the workaround only for Tegra20.
> 
> Signed-off-by: Laxman Dewangan <ldewangan@...dia.com>
>

Tested-by: Chaitanya Bandi <bandik@...dia.com>
Tested on Harmony with non-dt booting and confirmed that it is using the
dma based apbio access.



--
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/