From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S941693AbcJYKf7 (ORCPT <rfc822;w@1wt.eu>);
        Tue, 25 Oct 2016 06:35:59 -0400
Received: from mga02.intel.com ([134.134.136.20]:37155 "EHLO mga02.intel.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S933825AbcJYKf5 (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 25 Oct 2016 06:35:57 -0400
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.31,545,1473145200"; 
   d="scan'208";a="893695175"
Date: Tue, 25 Oct 2016 13:35:53 +0300
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Christian Steiner <christian.steiner@outlook.de>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: pinctrl_cherryview: massive error messages (handle_bad_irq)
Message-ID: <20161025103553.GH1476@lahna.fi.intel.com>
References: <AM2PR05MB0689F5F3CA848A4CC841184B91D20@AM2PR05MB0689.eurprd05.prod.outlook.com>
 <20161019192222.GQ1722@lahna.fi.intel.com>
 <AM2PR05MB0689B425AE8AC87C4BB047C191D20@AM2PR05MB0689.eurprd05.prod.outlook.com>
 <20161020100801.GV1722@lahna.fi.intel.com>
 <AM2PR05MB0689A3D0B3623EAFF27CC75B91D50@AM2PR05MB0689.eurprd05.prod.outlook.com>
 <CACRpkdYJXYX4QPVpnL-ztLY2VS11rX1AuYf8fXHMfke8zOFrMg@mail.gmail.com>
 <20161024081417.GB24289@lahna.fi.intel.com>
 <CACRpkdY7mV6MXD0Pvv2R0jMDd=3Pj=eFaNDcSSD+z+qyyVAedQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CACRpkdY7mV6MXD0Pvv2R0jMDd=3Pj=eFaNDcSSD+z+qyyVAedQ@mail.gmail.com>
Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
User-Agent: Mutt/1.7.1 (2016-10-04)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue, Oct 25, 2016 at 11:26:48AM +0200, Linus Walleij wrote:
> On Mon, Oct 24, 2016 at 10:14 AM, Mika Westerberg
> <mika.westerberg@linux.intel.com> wrote:
> 
> > It is possible to detect the BIOS version using DMI strings and issue a
> > warning in the driver, if that's what you mean, but currently we don't
> > do that.
> 
> I was more thinking about detecting the old BIOS and if that
> is present, mask off the interrupts on the resume path or something,
> as it is probably a bigger problem to see the warnings than to
> loose these settings.
> 
> Possibly also add a warning at probe() like you describe.

I think we can do masking of these IRQs (0..community->nirqs-1)
unconditionally in probe() because those should belong to the GPIO
driver as far as I understand. But I need to double check that from the
spec.