Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932183AbaFKHwM (ORCPT ); Wed, 11 Jun 2014 03:52:12 -0400 Received: from mailout4.w1.samsung.com ([210.118.77.14]:64497 "EHLO mailout4.w1.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755279AbaFKHwK (ORCPT ); Wed, 11 Jun 2014 03:52:10 -0400 MIME-version: 1.0 Content-type: text/plain; charset=UTF-8 X-AuditID: cbfec7f5-b7f626d000004b39-1e-53980aa7fcfa Content-transfer-encoding: 8BIT Message-id: <1402473139.24049.6.camel@AMDC1943> Subject: Re: [RESEND PATCH] ARM: EXYNOS: Fix the sequence of secondary CPU boot for Exynos3250 From: Krzysztof Kozlowski To: Tomasz Figa Cc: Chanwoo Choi , linux@arm.linux.org.uk, kgene.kim@samsung.com, t.figa@samsung.com, kyungmin.park@samsung.com, linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org Date: Wed, 11 Jun 2014 09:52:19 +0200 In-reply-to: <53979B52.5000902@gmail.com> References: <1402442827-2321-1-git-send-email-cw00.choi@samsung.com> <5397963F.30109@gmail.com> <53979871.2020903@samsung.com> <53979B52.5000902@gmail.com> X-Mailer: Evolution 3.10.4-0ubuntu1 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrCLMWRmVeSWpSXmKPExsVy+t/xy7rLuWYEG9zZI2xx/ctzVoveBVfZ LM42vWG32PT4GqvF5V1z2CxmnN/HZHH7Mq/F+hmvWSxW7frD6MDp0dLcw+axc9Zddo/NS+o9 +rasYvT4vEkugDWKyyYlNSezLLVI3y6BK2ParCOsBS8EKw5N3c/SwHiBr4uRk0NCwETiw9mv 7BC2mMSFe+vZuhi5OIQEljJKfPx3kgkkwSsgKPFj8j2WLkYODmYBeYkjl7JBwswC6hKT5i1i hqj/zCgx5cwqVoh6fYkbc9rZQeqFBRIkNvcqgYTZBIwlNi9fwgZiiwD1fpvSzw7SywzSe+/7 OrAjWARUJVrbtzOC9HIKaEpcPl4AMX8+o8ThLXeZIA5Vlpi3/xjTBEaBWUjOm4Vw3iwk5y1g ZF7FKJpamlxQnJSea6RXnJhbXJqXrpecn7uJERLyX3cwLj1mdYhRgINRiYfXwH9asBBrYllx Ze4hRgkOZiUR3r6304OFeFMSK6tSi/Lji0pzUosPMTJxcEo1MErE277qdbF5ohx39lZpkG2v /ZvVWxIqJM9/8Dt3dv22pVNPnNKYFsH4K0BiQpNwZJTazYvWk7k8liZpTtrZcnxr+x2t2moN ZpejpRJ+AsVxxTOf5TFem3Hvy5YDh4I2T7gQsZyVT/SRTI7Kymjb7Ju3/G9w7bD12hneb/za q75718nncr6c25VYijMSDbWYi4oTAdoWSQFXAgAA Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On śro, 2014-06-11 at 01:57 +0200, Tomasz Figa wrote: > On 11.06.2014 01:44, Chanwoo Choi wrote: > > On 06/11/2014 08:35 AM, Tomasz Figa wrote: > >> Hi Chanwoo, > >> > >> On 11.06.2014 01:27, Chanwoo Choi wrote: > >>> This patch set AUTOWAKEUP_EN bit to ARM_CORE_CONFIGURATION register > >>> because Exynos3250 removes WFE in secure mode so that turn on automatically > >>> after setting CORE_LOCAL_PWR_EN. Also, This patch use dbs_sev() macro > >>> to guarantee the data synchronization of command instead of IPI_WAKEUP > >>> because Exynos3250 don't have WFE mode in secue mode. > >>> > >>> Signed-off-by: Chanwoo Choi > >>> Acked-by: Kyungmin Park > >>> --- > >>> arch/arm/mach-exynos/platsmp.c | 9 ++++++++- > >>> arch/arm/mach-exynos/pm.c | 8 ++++++-- > >>> arch/arm/mach-exynos/regs-pmu.h | 4 ++++ > >>> 3 files changed, 18 insertions(+), 3 deletions(-) > >>> > >> > >> This patch seems to be unneeded with Krzysztof's patch send a while ago > >> [1]. As reported by Krzysztof, that patch apparently fixes SMP support > >> on Exynos3250 and is much smaller and less invasive. > >> > >> [1] - http://thread.gmane.org/gmane.linux.kernel.samsung-soc/32809 > > > > OK, > > But Krzysztof's patch didn't include set S5P_CORE_AUTOWAKEUP_EN in EXYNOS_ARM_CORE_CONFIGURATION(cpu). > > and then use arch_send_wakeup_ipi_mask(cpumask_of(cpu)) command instead of dsb_sev(). Exynos3250 don't need > > send IPI message. > > I don't know technical details about CPU boot-up on Exynos3250 as I > haven't worked too much with this platform. According to my conversation > with Krzysztof, he found S5P_CORE_AUTOWAKEUP_EN and dsb_sev() to be not > needed. Instead S5P_CORE_WAKEUP_FROM_LOCAL_CFG can be set in > EXYNOS_ARM_CORE1_STATUS and then normal arch_send_wakeup_ipi_mask() > used. He might be able to provide more details. I tried to avoid setting S5P_CORE_AUTOWAKEUP_EN because of simple reason: in my SoC documentation this field is not documented. The ARM_CORE_CONFIGURATION register has only "LOCAL_PWR_CFG" field and nothing more. As for the IPI wakeup - I think it makes code cleaner than adding 'if' statement for specific chipset. Best regards, Krzysztof -- 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/