From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Hilman Subject: Re: [PATCH v11 0/3] Exynos 5410 support Date: Mon, 02 Jun 2014 08:05:10 -0700 Message-ID: <7hzjhvxsgp.fsf@paris.lan> References: <1401074613-29227-1-git-send-email-t.dakhran@samsung.com> <7hr43f9mmn.fsf@paris.lan> <538737CA.4070709@suse.de> <53874862.5080809@samsung.com> <538775AB.3000604@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: (Tarek Dakhran's message of "Fri, 30 May 2014 23:07:01 +0400") Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Tarek Dakhran Cc: Tushar Behera , Andreas =?utf-8?Q?F=C3=A4rber?= , Tarek Dakhran , "linux-kernel@vger.kernel.org" , Kukjin Kim , devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, "linux-arm-kernel@lists.infradead.org" , "linux-samsung-soc@vger.kernel.org" List-Id: devicetree@vger.kernel.org Tarek Dakhran writes: > Hi, > > On Fri, May 30, 2014 at 7:41 AM, Tushar Behera w= rote: >> On Thu, May 29, 2014 at 11:30 PM, Andreas F=C3=A4rber wrote: >>> Hi Tarek, >>> >>> >>> And I reproducibly get failures for CPUs 1-3, resulting in only one= CPU >>> in /proc/cpuinfo (compared to 4 on downstream 3.14): >>> >>> [ 0.045778] CPU: Testing write buffer coherency: ok >>> [ 0.045968] /cpus/cpu@0 missing clock-frequency property >>> [ 0.045993] /cpus/cpu@1 missing clock-frequency property >>> [ 0.046016] /cpus/cpu@2 missing clock-frequency property >>> [ 0.046040] /cpus/cpu@3 missing clock-frequency property >>> [ 0.046059] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 >>> [ 0.046135] Setting up static identity map for 0x403a8920 - 0x40= 3a8978 >>> [ 2.075052] CPU1: failed to come online >>> [ 4.085095] CPU2: failed to come online >>> [ 6.095142] CPU3: failed to come online >>> [ 6.095237] Brought up 1 CPUs >>> [ 6.095269] SMP: Total of 1 processors activated. >>> [ 6.095303] CPU: All CPU(s) started in HYP mode. >>> [ 6.095336] CPU: Virtualization extensions available. >>> >>> I also notice another apparent device tree issue: >>> >>> [ 7.341814] of_get_named_gpiod_flags: can't parse gpios property= of >>> node '/soc/mmc@12220000/slot@0[0]' >>> [ 7.341850] of_get_named_gpiod_flags: can't parse gpios property= of >>> node '/soc/mmc@12220000/slot@0[0]' >>> >>> Are any of those known issues and being worked on? >>> (The CPU failures affected 5420 Arndale Octa as well iirc.) >>> >> >> Can you check after applying following two patches for Arndale-Octa >> ([1],[2])? In other words, a patch similar to [2] might be required >> for this board too if it is booting under secure mode. > > Firmware node already present into exynos5410-smdk5410.dts > So with only patch[1] 4xA15 cores will boot on ODROID-XU and SMDK5410= =2E I also confirm that with 4xA15 cores boot when adding patch [1]. Kevin >> >> [1] http://www.spinics.net/lists/linux-samsung-soc/msg31776.html >> >> [PATCH v2 Resend 1/2] ARM: EXYNOS: Update secondary boot addr for se= cure mode >> >> [2] http://www.spinics.net/lists/linux-samsung-soc/msg31777.html >> >> [PATCH v2 Resend 2/2] ARM: dts: Add secure firmware support for Arnd= ale-octa >> >> >> -- >> Tushar Behera > > Best regards, > Tarek -- To unsubscribe from this list: send the line "unsubscribe devicetree" i= n the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html