From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751724Ab3KRRPK (ORCPT ); Mon, 18 Nov 2013 12:15:10 -0500 Received: from caramon.arm.linux.org.uk ([78.32.30.218]:43116 "EHLO caramon.arm.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751373Ab3KRRPE (ORCPT ); Mon, 18 Nov 2013 12:15:04 -0500 Date: Mon, 18 Nov 2013 17:14:45 +0000 From: Russell King - ARM Linux To: Catalin Marinas Cc: Alexandre Courbot , Kukjin Kim , Kyungmin Park , Tomasz Figa , Olof Johansson , Alexandre Courbot , linux-samsung-soc@vger.kernel.org, Linux Kernel Mailing List , "linux-arm-kernel@lists.infradead.org" Subject: Re: [PATCH] ARM: move firmware_ops to drivers/firmware Message-ID: <20131118171445.GI16735@n2100.arm.linux.org.uk> References: <1384678169-28228-1-git-send-email-acourbot@nvidia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.19 (2009-01-05) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Nov 17, 2013 at 03:59:04PM +0000, Catalin Marinas wrote: > No L2x0 (L210, L220, PL310) cache on ARMv8. And here I strongly > recommend the hardware people to make proper external caches which can > be flushed by standard CPU instructions, not MMIO. Any such caches > must be enabled by firmware before Linux starts. Yea, and we've seen what a trainwreck that causes on 32-bit ARM with the kernel exploding at boot time because of a dirty L2 cache.