Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754202AbcC3VYA (ORCPT ); Wed, 30 Mar 2016 17:24:00 -0400 Received: from muru.com ([72.249.23.125]:49504 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751778AbcC3VX6 (ORCPT ); Wed, 30 Mar 2016 17:23:58 -0400 Date: Wed, 30 Mar 2016 14:23:52 -0700 From: Tony Lindgren To: Jon Hunter Cc: Grygorii Strashko , Thomas Gleixner , Jason Cooper , Marc Zyngier , =?utf-8?Q?Beno=C3=AEt?= Cousson , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Stephen Warren , Thierry Reding , Kevin Hilman , Geert Uytterhoeven , Lars-Peter Clausen , Linus Walleij , linux-tegra@vger.kernel.org, linux-omap@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 02/15] ARM: OMAP: Correct interrupt type for ARM TWD Message-ID: <20160330212352.GF9329@atomide.com> References: <1458224359-32665-1-git-send-email-jonathanh@nvidia.com> <1458224359-32665-3-git-send-email-jonathanh@nvidia.com> <56EC2191.2060800@ti.com> <56FA8AEA.3000208@nvidia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <56FA8AEA.3000208@nvidia.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1513 Lines: 35 * Jon Hunter [160329 07:03]: > Hi Tony, > > On 18/03/16 15:41, Grygorii Strashko wrote: > > On 03/17/2016 04:19 PM, Jon Hunter wrote: > >> The ARM TWD interrupt is a private peripheral interrupt (PPI) and per > >> the ARM GIC documentation, whether the type for PPIs can be set is > >> IMPLEMENTATION DEFINED. For OMAP4 devices the PPI type cannot be set and > >> so when we attempt to set the type for the ARM TWD interrupt it fails. > >> This has done unnoticed because it fails silently and because we cannot > >> re-configure the type it has had no impact. Nevertheless fix the type > >> for the TWD interrupt so that it matches the hardware configuration. > >> > >> Reported-by: Grygorii Strashko > >> Signed-off-by: Jon Hunter > >> > >> --- > >> > >> Tony, Grygorii, > >> Please note that I have not tested this. Can you test this series and > >> see if you see any warnings on OMAP4? I am guessing that the configuration > >> should be LEVEL and not EDGE. This was reported here: > > > > Tested-by: Grygorii Strashko > > > > Tested on PandaBoard. Without this patch I can see below warning: > > I think that you can pick up this fix independently of this series as it > is something that has been broken for sometime and should be fixed. I > included it here for completeness to highlight the issue but if you want > to take it now, please go ahead. OK applying into omap-for-v4.6/fixes thanks. Tony