From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753528AbdIDL76 (ORCPT ); Mon, 4 Sep 2017 07:59:58 -0400 Received: from mga04.intel.com ([192.55.52.120]:35341 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753424AbdIDL74 (ORCPT ); Mon, 4 Sep 2017 07:59:56 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.41,474,1498546800"; d="scan'208";a="896914269" Date: Mon, 4 Sep 2017 14:53:22 +0300 From: Mika Westerberg To: Hans de Goede Cc: "Rafael J . Wysocki" , Andy Shevchenko , Darren Hart , Andy Shevchenko , linux-acpi@vger.kernel.org, platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2] platform/x86: intel_cht_int33fe: Work around BIOS bug on some devices Message-ID: <20170904115322.GB2477@lahna.fi.intel.com> References: <20170902162040.18565-1-hdegoede@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170902162040.18565-1-hdegoede@redhat.com> User-Agent: Mutt/1.8.3 (2017-05-23) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Sep 02, 2017 at 06:20:40PM +0200, Hans de Goede wrote: > At least one BIOS enumerates the max17047 both through the INT33FE ACPI > device (it is right there in the resources table) as well as through a > separate MAX17047 device. > > This commit checks for the max17047 already being enumerated through > a separate MAX17047 ACPI device and if so it uses the i2c-client > instantiated for this and attaches the device-props for the max17047 to > that i2c-client. > > Signed-off-by: Hans de Goede I won't say this looks good to me, but since this seems to be the only sane way to deal with the crappy BIOS, Acked-by: Mika Westerberg