Re: [PATCH v2] platform/x86: intel_cht_int33fe: Work around BIOS bug on some devices

2017-09-04 Thread Andy Shevchenko
On Mon, Sep 4, 2017 at 3:47 PM, Hans de Goede wrote: > Hi, > > On 04-09-17 14:23, Andy Shevchenko wrote: >> >> On Sat, 2017-09-02 at 18:20 +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

Re: [PATCH v2] platform/x86: intel_cht_int33fe: Work around BIOS bug on some devices

2017-09-04 Thread Hans de Goede
Hi, On 04-09-17 14:23, Andy Shevchenko wrote: On Sat, 2017-09-02 at 18:20 +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

Re: [PATCH v2] platform/x86: intel_cht_int33fe: Work around BIOS bug on some devices

2017-09-04 Thread Andy Shevchenko
On Sat, 2017-09-02 at 18:20 +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

Re: [PATCH v2] platform/x86: intel_cht_int33fe: Work around BIOS bug on some devices

2017-09-04 Thread Mika Westerberg
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 enumer

[PATCH v2] platform/x86: intel_cht_int33fe: Work around BIOS bug on some devices

2017-09-02 Thread Hans de Goede
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-cl