Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932388AbaFIUFW (ORCPT ); Mon, 9 Jun 2014 16:05:22 -0400 Received: from mail-vc0-f171.google.com ([209.85.220.171]:49222 "EHLO mail-vc0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932333AbaFIUFS (ORCPT ); Mon, 9 Jun 2014 16:05:18 -0400 MIME-Version: 1.0 In-Reply-To: <7htx7uq7k1.fsf@paris.lan> References: <1402090985-8061-1-git-send-email-dianders@chromium.org> <1402096465-13218-1-git-send-email-dianders@chromium.org> <7htx7uq7k1.fsf@paris.lan> Date: Mon, 9 Jun 2014 13:05:17 -0700 X-Google-Sender-Auth: apyZNToQdjlgBWcuko729VyFpMY Message-ID: Subject: Re: [PATCH v2] ARM: EXYNOS: mcpm: Don't rely on firmware's secondary_cpu_start From: Andrew Bresticker To: Kevin Hilman , Nicolas Pitre Cc: Doug Anderson , Kukjin Kim , Abhilash Kesavan , Inderpal Singh , Thomas Abraham , Olof Johansson , Tushar Behera , Javier Martinez Canillas , linux-samsung-soc , Russell King , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > [1] While waiting for the forth-coming patch from Andrew to enable the > CCI port for the boot cluster), I do this from u-boot before starting > the kernel (based on earlier email from Doug): > > mw.l 10d25000 3 # Enable CCI from U-Boot >From the other thread, it sounds like Nicolas wants enabling of the boot cluster's CCI port to be done unconditionally for all MCPM platforms. Nicolas, are you preparing a patch for this or should I? The only issue I see with making the MCPM loopback generic is that although all current mainline MCPM platforms have the same cache flush procedure, a future platform could be different. Thanks, Andrew -- 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/