Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755246Ab3JQNEo (ORCPT ); Thu, 17 Oct 2013 09:04:44 -0400 Received: from mail-lb0-f179.google.com ([209.85.217.179]:57769 "EHLO mail-lb0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753811Ab3JQNEl (ORCPT ); Thu, 17 Oct 2013 09:04:41 -0400 Date: Thu, 17 Oct 2013 16:04:35 +0300 From: Aliaksei Katovich To: Kevin Hilman Cc: Vyacheslav Tyrtov , Mark Rutland , devicetree@vger.kernel.org, Kukjin Kim , Russell King , Ben Dooks , Pawel Moll , Ian Campbell , Stephen Warren , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Rob Herring , Tarek Dakhran , Daniel Lezcano , linux-samsung-soc@vger.kernel.org, Rob Landley , Mike Turquette , Thomas Gleixner , Naour Romain , linux-arm-kernel@lists.infradead.org, Heiko Stuebner Subject: Re: [PATCH v2 0/4] Exynos 5410 Dual cluster support Message-ID: <20131017130435.GG3061@cat.local> References: <1381763305-7085-1-git-send-email-v.tyrtov@samsung.com> <87k3hc3lso.fsf@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <87k3hc3lso.fsf@linaro.org> X-Operating-System: GNU/Linux X-Kernel: Linux 3.12.0-rc1+ User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 4411 Lines: 86 hi Kevin; > Vyacheslav Tyrtov writes: > > > The series of patches represent support of Exynos 5410 SoC > > > > The Exynos 5410 is the first Samsung SoC based on bigLITTLE architecture. > > Patches allow all 8 CPU cores (4 x A7 and 4 x A15) to run at the same time > > > > Patches add new platform description, support of clock controller, > > dual cluster support and device tree for Exynos 5410 > > > > Has been build on v3.12-rc5. > > Has been tested on Exynos 5410 reference board (exynos_defconfig). > > Has anyone tried this on the exynos5410 based odroid-xu yet? > > I tried booting this on my recently arrived odroid-xu, but am not > getting it to boot. I am able to boot my odroid-xu+e to busybox with these patches applied against 3.12-rc5: exynos_defconfig and exynos5410-smdk5410.dtb were used. However there seem to be some issues with virq allocations, like this: Starting kernel ... [ 0.000000] [] (unwind_backtrace+0x0/0xf8) from [] (show_stack+0x10/0x14) [ 0.000000] [] (show_stack+0x10/0x14) from [] (dump_stack+0x6c/0xac) [ 0.000000] [] (dump_stack+0x6c/0xac) from [] (warn_slowpath_common+0x64/0x88) [ 0.000000] [] (warn_slowpath_common+0x64/0x88) from [] (warn_slowpath_fmt+0x30/0x40) [ 0.000000] [] (warn_slowpath_fmt+0x30/0x40) from [] (irq_domain_associate+0x128/0x1a8) [ 0.000000] [] (irq_domain_associate+0x128/0x1a8) from [] (irq_domain_associate_many+0x30/0x3c ) [ 0.000000] [] (irq_domain_associate_many+0x30/0x3c) from [] (irq_domain_add_simple+0x78/0x90) [ 0.000000] [] (irq_domain_add_simple+0x78/0x90) from [] (combiner_of_init+0xb4/0x198) [ 0.000000] [] (combiner_of_init+0xb4/0x198) from [] (of_irq_init+0x278/0x2a0) [ 0.000000] [] (of_irq_init+0x278/0x2a0) from [] (start_kernel+0x18c/0x384) [ 0.000000] [] (start_kernel+0x18c/0x384) from [<40008074>] (0x40008074) [ 0.000000] ---[ end trace 1b75b31a2719edcd ]--- [ 0.000000] ------------[ cut here ]------------ [ 0.000000] WARNING: CPU: 0 PID: 0 at kernel/irq/irqdomain.c:278 irq_domain_associate+0x128/0x1a8() [ 0.000000] error: virq337 is not allocated [ 0.000000] Modules linked in: [ 0.000000] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G W 3.12.0-rc5-00004-g1cb405f #1 [ 0.000000] [] (unwind_backtrace+0x0/0xf8) from [] (show_stack+0x10/0x14) [ 0.000000] [] (show_stack+0x10/0x14) from [] (dump_stack+0x6c/0xac) [ 0.000000] [] (dump_stack+0x6c/0xac) from [] (warn_slowpath_common+0x64/0x88) [ 0.000000] [] (warn_slowpath_common+0x64/0x88) from [] (warn_slowpath_fmt+0x30/0x40) [ 0.000000] [] (warn_slowpath_fmt+0x30/0x40) from [] (irq_domain_associate+0x128/0x1a8) [ 0.000000] [] (irq_domain_associate+0x128/0x1a8) from [] (irq_domain_associate_many+0x30/0x3c ) [ 0.000000] [] (irq_domain_associate_many+0x30/0x3c) from [] (irq_domain_add_simple+0x78/0x90) [ 0.000000] [] (irq_domain_add_simple+0x78/0x90) from [] (combiner_of_init+0xb4/0x198) [ 0.000000] [] (combiner_of_init+0xb4/0x198) from [] (of_irq_init+0x278/0x2a0) [ 0.000000] [] (of_irq_init+0x278/0x2a0) from [] (start_kernel+0x18c/0x384) [ 0.000000] [] (start_kernel+0x18c/0x384) from [<40008074>] (0x40008074) [ 0.000000] ---[ end trace 1b75b31a2719edce ]--- [ 0.000000] ------------[ cut here ]------------ You can check full boot log here http://sprunge.us/NKcU -- Aliaksei > > I'm not yet terribly familiar with this SoC, what are the settings > needed for DEBUG_LL on this board? > > Thanks, > > Kevin > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel > -- 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/