Messages in this thread | | | From | David Brownell <> | Subject | Re: [PATCH v3 3/3] gpio: add Intel SCH GPIO controller driver | Date | Sun, 21 Feb 2010 11:12:48 -0800 |
| |
On Sunday 21 February 2010, Denis Turischev wrote: > v2: there is no acpi_check_region, it will be implemented in mfd-core > v3: patch refreshed against the latest Linus tree
Could such call really address the GPIO conflict issue I mentioned?
The AML bytecodes I looked at were writing directly to Southbridge GPIO registers (or reading them), or relying on ACPI to mediate the GPIO interrupts. ISTR that button drivers, and code to switch into or out of low power states, were good sources of such bad examples.
Calls like that should clearly be able to handle cases where ACPI has a "Real" Driver (tm) ... e.g. for SMBus hardware.
I'm not sure what a good solution for this would be, short of just not using ACPI ... which may not be practical, given the limited degree of x86 board/system support for Linux.
I mention this mostly because when I looked at the issue in the context of an ICHx GPIO driver, I didn't see a good solution to the problem then ... and nothing seems to have changed meanwhile.
- Dave
| |