From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Martin Subject: Re: [PATCH 3/6] ARM: EXYNOS: add Exynos Dual Cluster Support Date: Wed, 2 Oct 2013 14:05:50 +0100 Message-ID: <20131002130550.GB3407@localhost.localdomain> References: <1380644227-12244-1-git-send-email-v.tyrtov@samsung.com> <1380644227-12244-4-git-send-email-v.tyrtov@samsung.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Nicolas Pitre Cc: Mark Rutland , devicetree@vger.kernel.org, Kukjin Kim , Russell King , Daniel Lezcano , Pawel Moll , Ian Campbell , Stephen Warren , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Rob Herring , linux-samsung-soc@vger.kernel.org, Vyacheslav Tyrtov , Ben Dooks , Tarek Dakhran , Thomas Gleixner , Rob Landley , Heiko Stuebner , Mike Turquette , linux-arm-kernel@lists.infradead.org, Naour Romain List-Id: devicetree@vger.kernel.org On Tue, Oct 01, 2013 at 03:55:24PM -0400, Nicolas Pitre wrote: > On Tue, 1 Oct 2013, Vyacheslav Tyrtov wrote: > > > From: Tarek Dakhran [...] > > + kfs_use_count[cpu][cluster]++; > > + if (kfs_use_count[cpu][cluster] == 1) { > > + ++core_count[cluster]; > > + if (core_count[cluster] == 1) { > > + ret = exynos_cluster_power_up(cluster); > > + if (ret) { > > + pr_err("%s: cluster %u power up error\n", > > + __func__, cluster); > > + return ret; > > + } > > + __cci_control_port_by_index(MAX_NR_CLUSTERS > > + - cluster, true); > > This is wrong and very racy. The state machine implemented in > mcpm-head.S is there already to handle proper synchronization for you. Maybe this issue didn't make itself obvious yet due to the lack of suspend support. Moving the CCI maintenance to power_up_setup() is essential for suspend/ resume to work, because then CPUs can power up randomly in response to interrupts -- exynos_lock is not sufficient protection in that case. The TC2 code should provide a good example of what to do. [...] Cheers ---Dave