From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mika Westerberg Subject: Re: [PATCH] i2c: i801: Allow ACPI SystemIO OpRegion to conflict with PCI BAR Date: Mon, 2 May 2016 15:40:45 +0300 Message-ID: <20160502124045.GA1717@lahna.fi.intel.com> References: <1461839010-110231-1-git-send-email-mika.westerberg@linux.intel.com> <577f885f-b54d-cf55-b1a3-0b04358271d8@kernel.org> <20160429085615.GK32610@lahna.fi.intel.com> <20160502101218.GM32610@lahna.fi.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mga02.intel.com ([134.134.136.20]:4068 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752231AbcEBMlE (ORCPT ); Mon, 2 May 2016 08:41:04 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-i2c-owner@vger.kernel.org List-Id: linux-i2c@vger.kernel.org To: "Rafael J. Wysocki" Cc: Andy Lutomirski , Andy Lutomirski , Jean Delvare , Wolfram Sang , Jarkko Nikula , "Rafael J. Wysocki" , "linux-i2c@vger.kernel.org" , Linux ACPI , Pali =?iso-8859-1?Q?Roh=E1r?= , Mario Limonciello On Mon, May 02, 2016 at 01:42:41PM +0200, Rafael J. Wysocki wrote: > > So what we are currently doing (preventing the driver from loading) is > > the right thing to do according the above. > > In general, that is the right thing to do. That's why we do it as a rule. :-) > > However, in this particular case we actually know that the opregion > declaration is bogus at least on some systems. So, this is a > workaround for a known defect in some systems' ACPI tables. Fair enough :)