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 S935267AbcJXIOZ (ORCPT <rfc822;w@1wt.eu>);
        Mon, 24 Oct 2016 04:14:25 -0400
Received: from mga03.intel.com ([134.134.136.65]:25384 "EHLO mga03.intel.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S933778AbcJXIOV (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 24 Oct 2016 04:14:21 -0400
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.31,541,1473145200"; 
   d="scan'208";a="776774645"
Date: Mon, 24 Oct 2016 11:14:17 +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: <20161024081417.GB24289@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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CACRpkdYJXYX4QPVpnL-ztLY2VS11rX1AuYf8fXHMfke8zOFrMg@mail.gmail.com>
Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
User-Agent: Mutt/1.7.0 (2016-08-17)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Mon, Oct 24, 2016 at 01:34:05AM +0200, Linus Walleij wrote:
> On Thu, Oct 20, 2016 at 5:36 PM, Christian Steiner
> <christian.steiner@outlook.de> wrote:
> 
> >>> Currently I am using BIOS v1.22. Recently Acer released v1.23. I could
> >>> test if the BIOS update solves the problem.
> >>
> >> Please try that first.
> >
> > Updating the BIOS to v1.23 solved the problem. Thank you very much for
> > your advice!
> 
> Not that I know how the Intel ecosystem works wrt this.
> 
> Do you detect elder BIOS and display a warning? Are regular
> users updating their BIOSes? Or was this some kind of development
> Intel in-house BIOS?

People do upgrade their BIOSes but for Linux users it has some extra
pain if the OEM only provides you a .exe file which you need to run
under Windows.

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.