linux-kernel - Re: [PATCH v3 3/3] gpio: add Intel SCH GPIO controller driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 21 Feb 2010 11:12:48 -0800
From:	David Brownell <david-b@...bell.net>
To:	Denis Turischev <denis@...pulab.co.il>
Cc:	Samuel Ortiz <sameo@...ux.intel.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 3/3] gpio: add Intel SCH GPIO controller driver

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/