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]
Message-ID: <4B8CDA64.4070504@compulab.co.il>
Date:	Tue, 02 Mar 2010 11:29:08 +0200
From:	Denis Turischev <denis@...pulab.co.il>
To:	Len Brown <lenb@...nel.org>
CC:	Mike Rapoport <mike@...pulab.co.il>,
	David Brownell <david-b@...bell.net>,
	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

Mike Rapoport wrote:
> Len Brown wrote:
>>> I've looked at two x86 drivers in drivers/gpiolib (cs5535 and langwell) and
>>> there's no treatment of ACPI in either of them. Since SCH is defined by Intel
>>> as "embedded" product, having a GPIO driver for it seems logical even despite
>>> problems you mention.
>> FWIW
>> I believe that Langwell is used only in products without an ACPI BIOS.
>>
>> Poulsbo, OTOH, is used in zillions of netbooks running Windows XP.
>> I don't know what a cs5535 is.
> 
> The cs5535 is AMD Geode LX companion chip which is used with ACPI BIOS 
> as well.
> 
>> cheers,
>> Len Brown, Intel Open Source Technology Center
>>
> 
> 

I'm really not an ACPI expert too, but as I see in LDD3 "...the role of a device driver
is providing mechanism, not policy".

HW manufacturer must warn users if some GPIOs may conflict with ACPI, and it is user`s
responsibility to use the GPIOs in proper way.

Denis
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ