Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752675AbaFFWqo (ORCPT ); Fri, 6 Jun 2014 18:46:44 -0400 Received: from mail-vc0-f174.google.com ([209.85.220.174]:49922 "EHLO mail-vc0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752476AbaFFWqm (ORCPT ); Fri, 6 Jun 2014 18:46:42 -0400 MIME-Version: 1.0 In-Reply-To: References: <1402090985-8061-1-git-send-email-dianders@chromium.org> Date: Fri, 6 Jun 2014 15:46:41 -0700 X-Google-Sender-Auth: 7wMajYJZSyuMfYJ-NDeMvtR8mAY Message-ID: Subject: Re: [PATCH] ARM: EXYNOS: mcpm: Don't rely on firmware's secondary_cpu_start From: Andrew Bresticker To: Doug Anderson Cc: Nicolas Pitre , Kukjin Kim , Abhilash Kesavan , Inderpal Singh , Thomas Abraham , Olof Johansson , Tushar Behera , Kevin Hilman , 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 >> If this is all that is needed to solve the problem being discussed in >> the other thread I have absolutely no issue with such a workaround going >> into mainline. > > This plus the CCI fix that Andrew is planning to post. Right - we'll need a patch to enable the CCI port for the cluster we booted on at boot and resume time since the first CPU up won't enter through exynos_pm_power_up_setup(). I'll try to post something later today or Monday. -- 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/