linux-kernel - Re: [PATCH v2 3/3] misc: sram: switch to ioremap

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: <1423239007.3864.44.camel@pengutronix.de>
Date:	Fri, 06 Feb 2015 17:10:07 +0100
From:	Philipp Zabel <p.zabel@...gutronix.de>
To:	Abhilash Kesavan <a.kesavan@...sung.com>
Cc:	gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
	hirokazu.takata.wj@...esas.com, catalin.marinas@....com,
	Will.Deacon@....com, heiko@...ech.de, shc_work@...l.ru,
	nicoleotsuka@...il.com, padma.v@...sung.com, arnd@...db.de,
	alsa-devel@...a-project.org, shawn.guo@...aro.org,
	bcousson@...libre.com, tony@...mide.com, kernel@...gutronix.de,
	kgene@...nel.org
Subject: Re: [PATCH v2 3/3] misc: sram: switch to ioremap_wc from ioremap

Am Freitag, den 06.02.2015, 19:15 +0530 schrieb Abhilash Kesavan:
> Currently, the SRAM allocator returns device memory via ioremap.
> This causes issues on ARM64 when the internal SoC SRAM allocated by
> the generic sram driver is used for audio playback. The destination
> buffer address (which is ioremapped SRAM) is not 64-bit aligned for
> certain streams (e.g. 44.1k sampling rate). In such cases we get
> unhandled alignment faults. Use ioremap_wc in place of ioremap which
> gives us normal non-cacheable memory instead of device memory.
> 
> Signed-off-by: Abhilash Kesavan <a.kesavan@...sung.com>
> Tested-by: Tony Lindgren <tony@...mide.com>
> Tested-by: Heiko Stuebner <heiko@...ech.de>

Acked-by: Philipp Zabel <p.zabel@...gutronix.de>

regards
Philipp


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