Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752490AbbGFEpP (ORCPT ); Mon, 6 Jul 2015 00:45:15 -0400 Received: from mail-wg0-f49.google.com ([74.125.82.49]:35054 "EHLO mail-wg0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750728AbbGFEpH (ORCPT ); Mon, 6 Jul 2015 00:45:07 -0400 MIME-Version: 1.0 In-Reply-To: References: <20150703024044.GB24695@verge.net.au> <20150703105441.GF1521@katana> <20150703133245.GA19284@katana> <20150703143703.GB19284@katana> Date: Mon, 6 Jul 2015 13:45:05 +0900 Message-ID: Subject: Re: Possible regression due to "tick: broadcast: Prevent livelock from event handler" From: Magnus Damm To: Geert Uytterhoeven Cc: Wolfram Sang , Thomas Gleixner , Simon Horman , Kevin Hilman , Tyler Baker , Borislav Petkov , Geert Uytterhoeven , Linux-sh list , "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 Content-Length: 1189 Lines: 31 Hi Geert, On Sat, Jul 4, 2015 at 2:02 AM, Geert Uytterhoeven wrote: > Hi Wolfram, > > On Fri, Jul 3, 2015 at 4:37 PM, Wolfram Sang wrote: >>> So this is a single core machine and uses the em_sti timer w/o the >>> broadcast nonsense. In Simons case it looks like em_sti is used as >>> broadcast device. >> >> We use the same board. Just my kernel has SMP=n. > > Unlike our other multi-core A9 SoCs, emev2.dtsi doesn't have a node > for the arm,cortex-a9-twd-timer? That's right, the TWD was never enabled on upstream EMEV2. I believe it is documented in the data sheet though, however the actual vendor-specific glue is a bit different compared to other SoCs from Renesas Electronics - this most likely since EMEV2 was initially made by NEC Electronics instead of Renesas. I've been told that it was one of the earlier Cortex-A9 designs around so some special surprises may exist! Cheers, / magnus -- 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/