Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752770AbbEKWRk (ORCPT ); Mon, 11 May 2015 18:17:40 -0400 Received: from bhuna.collabora.co.uk ([93.93.135.160]:43552 "EHLO bhuna.collabora.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751853AbbEKWRg (ORCPT ); Mon, 11 May 2015 18:17:36 -0400 From: Sjoerd Simons To: Rob Herring , Russell King , Tony Lindgren Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Javier Martinez Canillas Subject: [PATCH 0/3] Fix boot on Calxeda highbank Date: Tue, 12 May 2015 00:17:28 +0200 Message-Id: <1431382651-15894-1-git-send-email-sjoerd.simons@collabora.co.uk> X-Mailer: git-send-email 2.1.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1409 Lines: 31 When upgrading our trusted Calxeda server to Debian Jessie recently the machine wedged during booting the installer. Upon further investigation, this happens due to the transition to the generic L2C infrastructure introduced in 3.16. The generic l2x0 code unlocks the cache during setup, however the Caldexa SMC interface doesn't seem to allow the kernel to enable enable non-secure access to the lock registers.. Queue Imprecise aborts and a fairly unhappy machine. First patch in this series adds a flag to indicate to the l2x0 code the unlocking should be skipped, second patch turns that flag on for mach-highbank, fixing this issue. Third patch adds a (empty) configure callback for the highbank l2c, reflecting the fact that there seeminglyisn't anything to configured via an SMC on these maches. Sjoerd Simons (3): ARM: cache-l2c: Add flag to skip cache unlocking ARM: l2c: highbank: Skip l2c unlocking ARM: l2c: highbank: Add dummy configure function arch/arm/include/asm/outercache.h | 1 + arch/arm/mach-highbank/highbank.c | 9 +++++++++ arch/arm/mm/cache-l2x0.c | 4 +++- 3 files changed, 13 insertions(+), 1 deletion(-) -- 2.1.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/