[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2754889.4x1EiTEaaZ@aspire.rjw.lan>
Date: Thu, 29 Jun 2017 23:13:33 +0200
From: "Rafael J. Wysocki" <rjw@...ysocki.net>
To: Alan Cox <gnomes@...rguk.ukuu.org.uk>,
Linus Walleij <linus.walleij@...aro.org>
Cc: Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@...ux.intel.com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Andy Shevchenko <andy.shevchenko@...il.com>,
Hans de Goede <hdegoede@...hat.com>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Sathyanarayanan Kuppuswamy Natarajan <sathyaosid@...il.com>,
Graeme Gregory <graeme.gregory@...aro.org>
Subject: Re: [PATCH v2 1/1] gpio: gpio-wcove: Fix GPIO control register offset calculation
On Thursday, June 29, 2017 08:28:57 PM Alan Cox wrote:
> > So where can I get a handle on the people inside Intel who are obviously
> > using ACPI GPIO class for shoehorning what we in the linux kernel call
> > syscon or register bit misc access into the GPIO ACPI container just
> > because they feel it is convenient?
>
> It's a Windowsism and since Windows is the primary OS shipped the vendors
> of client platforms do what is needed to make Windows work nicely.
Yes, we are pretty much on the receiving end here and unfortunately we need to
deal with stuff already manufactured and shipped.
Thanks,
Rafael
Powered by blists - more mailing lists