ACPI: hotkey: remove driver, per feature-removal-schedule.txt

driver/acpi/hotkey.c implement:

1. /proc/acpi/hotkey/event_config 

(event based hotkey or event config interface):

a. add a  event based hotkey(event) : 

echo "0:bus::action:method:num:num" > event_config

b. delete a event based hotkey(event): 

echo "1:::::num:num" > event_config

c.  modify a event based hotkey(event):    

echo "2:bus::action:method:num:num" > event_config

2. /proc/acpi/hotkey/poll_config 

(polling based hotkey or event config interface):

a.add a polling based hotkey(event) : 	

echo "0:bus:method:action:method:num" > poll_config

this adding command will create a proc file 

/proc/acpi/hotkey/method, which is used to get 

result of polling.

b.delete a polling based hotkey(event): 	

echo "1:::::num" > event_config

c.modify a polling based hotkey(event):    

echo "2:bus:method:action:method:num" > poll_config

3./proc/acpi/hotkey/action 

(interface to call aml method associated with a 

specific hotkey(event))

echo "event_num:event_type:event_argument" > 

	/proc/acpi/hotkey/action.

The result of the execution of this aml method is 

attached to /proc/acpi/hotkey/poll_method, which is dynamically

created.  Please use command "cat /proc/acpi/hotkey/polling_method" 

to retrieve it.

Note: Use cmdline "acpi_generic_hotkey" to over-ride

platform-specific with generic driver.

---------------------------

<<<<<<< test:Documentation/feature-removal-schedule.txt

What:	ACPI hotkey driver (CONFIG_ACPI_HOTKEY)

When:	2.6.21

Why:	hotkey.c was an attempt to consolidate multiple drivers that use

	ACPI to implement hotkeys.  However, hotkeys are not documented

	in the ACPI specification, so the drivers used undocumented

	vendor-specific hooks and turned out to be more different than

	the same.

	Further, the keys and the features supplied by each platform

	are different, so there will always be a need for

	platform-specific drivers.

	So the new plan is to delete hotkey.c and instead, work on the

	platform specific drivers to try to make them look the same

	to the user when they supply the same features.

	hotkey.c has always depended on CONFIG_EXPERIMENTAL

Who:	Len Brown <len.brown@intel.com>

---------------------------

What:	/sys/firmware/acpi/namespace

When:	2.6.21

Why:	The ACPI namespace is effectively the symbol list for

	  Note that this is an ref. implementation only.  It may or may not work

	  for your integrated video device.

config ACPI_HOTKEY

	tristate "Generic Hotkey (EXPERIMENTAL)"

	depends on EXPERIMENTAL

	depends on X86

	default n

	help

	  Experimental consolidated hotkey driver.

	  If you are unsure, say N.

config ACPI_FAN

	tristate "Fan"

	default y

obj-$(CONFIG_ACPI_DOCK)		+= dock.o

obj-$(CONFIG_ACPI_BAY)		+= bay.o

obj-$(CONFIG_ACPI_VIDEO)	+= video.o

obj-$(CONFIG_ACPI_HOTKEY)	+= hotkey.o

obj-y				+= pci_root.o pci_link.o pci_irq.o pci_bind.o

obj-$(CONFIG_ACPI_POWER)	+= power.o

obj-$(CONFIG_ACPI_PROCESSOR)	+= processor.o

	if (acpi_disabled)

		return -ENODEV;

	if (!acpi_specific_hotkey_enabled) {

		printk(KERN_ERR "Using generic hotkey driver\n");

		return -ENODEV;

	}

	asus_proc_dir = proc_mkdir(PROC_ASUS, acpi_root_dir);

	if (!asus_proc_dir) {

		printk(KERN_ERR "Asus ACPI: Unable to create /proc entry\n");