diff options
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/acpi-hotkey.txt | 38 | ||||
-rw-r--r-- | Documentation/feature-removal-schedule.txt | 23 | ||||
-rw-r--r-- | Documentation/sony-laptop.txt | 106 |
3 files changed, 106 insertions, 61 deletions
diff --git a/Documentation/acpi-hotkey.txt b/Documentation/acpi-hotkey.txt deleted file mode 100644 index 38040fa37649..000000000000 --- a/Documentation/acpi-hotkey.txt +++ /dev/null | |||
@@ -1,38 +0,0 @@ | |||
1 | driver/acpi/hotkey.c implement: | ||
2 | 1. /proc/acpi/hotkey/event_config | ||
3 | (event based hotkey or event config interface): | ||
4 | a. add a event based hotkey(event) : | ||
5 | echo "0:bus::action:method:num:num" > event_config | ||
6 | |||
7 | b. delete a event based hotkey(event): | ||
8 | echo "1:::::num:num" > event_config | ||
9 | |||
10 | c. modify a event based hotkey(event): | ||
11 | echo "2:bus::action:method:num:num" > event_config | ||
12 | |||
13 | 2. /proc/acpi/hotkey/poll_config | ||
14 | (polling based hotkey or event config interface): | ||
15 | a.add a polling based hotkey(event) : | ||
16 | echo "0:bus:method:action:method:num" > poll_config | ||
17 | this adding command will create a proc file | ||
18 | /proc/acpi/hotkey/method, which is used to get | ||
19 | result of polling. | ||
20 | |||
21 | b.delete a polling based hotkey(event): | ||
22 | echo "1:::::num" > event_config | ||
23 | |||
24 | c.modify a polling based hotkey(event): | ||
25 | echo "2:bus:method:action:method:num" > poll_config | ||
26 | |||
27 | 3./proc/acpi/hotkey/action | ||
28 | (interface to call aml method associated with a | ||
29 | specific hotkey(event)) | ||
30 | echo "event_num:event_type:event_argument" > | ||
31 | /proc/acpi/hotkey/action. | ||
32 | The result of the execution of this aml method is | ||
33 | attached to /proc/acpi/hotkey/poll_method, which is dynamically | ||
34 | created. Please use command "cat /proc/acpi/hotkey/polling_method" | ||
35 | to retrieve it. | ||
36 | |||
37 | Note: Use cmdline "acpi_generic_hotkey" to over-ride | ||
38 | platform-specific with generic driver. | ||
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt index c585aa8d62b4..28f897fd3674 100644 --- a/Documentation/feature-removal-schedule.txt +++ b/Documentation/feature-removal-schedule.txt | |||
@@ -253,29 +253,6 @@ Who: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com> | |||
253 | 253 | ||
254 | --------------------------- | 254 | --------------------------- |
255 | 255 | ||
256 | <<<<<<< test:Documentation/feature-removal-schedule.txt | ||
257 | What: ACPI hotkey driver (CONFIG_ACPI_HOTKEY) | ||
258 | When: 2.6.21 | ||
259 | Why: hotkey.c was an attempt to consolidate multiple drivers that use | ||
260 | ACPI to implement hotkeys. However, hotkeys are not documented | ||
261 | in the ACPI specification, so the drivers used undocumented | ||
262 | vendor-specific hooks and turned out to be more different than | ||
263 | the same. | ||
264 | |||
265 | Further, the keys and the features supplied by each platform | ||
266 | are different, so there will always be a need for | ||
267 | platform-specific drivers. | ||
268 | |||
269 | So the new plan is to delete hotkey.c and instead, work on the | ||
270 | platform specific drivers to try to make them look the same | ||
271 | to the user when they supply the same features. | ||
272 | |||
273 | hotkey.c has always depended on CONFIG_EXPERIMENTAL | ||
274 | |||
275 | Who: Len Brown <len.brown@intel.com> | ||
276 | |||
277 | --------------------------- | ||
278 | |||
279 | What: /sys/firmware/acpi/namespace | 256 | What: /sys/firmware/acpi/namespace |
280 | When: 2.6.21 | 257 | When: 2.6.21 |
281 | Why: The ACPI namespace is effectively the symbol list for | 258 | Why: The ACPI namespace is effectively the symbol list for |
diff --git a/Documentation/sony-laptop.txt b/Documentation/sony-laptop.txt new file mode 100644 index 000000000000..dfd26df056f4 --- /dev/null +++ b/Documentation/sony-laptop.txt | |||
@@ -0,0 +1,106 @@ | |||
1 | Sony Notebook Control Driver (SNC) Readme | ||
2 | ----------------------------------------- | ||
3 | Copyright (C) 2004- 2005 Stelian Pop <stelian@popies.net> | ||
4 | Copyright (C) 2007 Mattia Dongili <malattia@linux.it> | ||
5 | |||
6 | This mini-driver drives the SNC device present in the ACPI BIOS of | ||
7 | the Sony Vaio laptops. | ||
8 | |||
9 | It gives access to some extra laptop functionalities. In its current | ||
10 | form, this driver let the user set or query the screen brightness | ||
11 | through the backlight subsystem and remove/apply power to some devices. | ||
12 | |||
13 | Backlight control: | ||
14 | ------------------ | ||
15 | If your laptop model supports it, you will find sysfs files in the | ||
16 | /sys/class/backlight/sony/ | ||
17 | directory. You will be able to query and set the current screen | ||
18 | brightness: | ||
19 | brightness get/set screen brightness (an iteger | ||
20 | between 0 and 7) | ||
21 | actual_brightness reading from this file will query the HW | ||
22 | to get real brightness value | ||
23 | max_brightness the maximum brightness value | ||
24 | |||
25 | |||
26 | Platform specific: | ||
27 | ------------------ | ||
28 | Loading the sony-laptop module will create a | ||
29 | /sys/devices/platform/sony-laptop/ | ||
30 | directory populated with some files. | ||
31 | |||
32 | You then read/write integer values from/to those files by using | ||
33 | standard UNIX tools. | ||
34 | |||
35 | The files are: | ||
36 | brightness_default screen brightness which will be set | ||
37 | when the laptop will be rebooted | ||
38 | cdpower power on/off the internal CD drive | ||
39 | audiopower power on/off the internal sound card | ||
40 | lanpower power on/off the internal ethernet card | ||
41 | (only in debug mode) | ||
42 | |||
43 | Note that some files may be missing if they are not supported | ||
44 | by your particular laptop model. | ||
45 | |||
46 | Example usage: | ||
47 | # echo "1" > /sys/devices/platform/sony-laptop/brightness_default | ||
48 | sets the lowest screen brightness for the next and later reboots, | ||
49 | # echo "8" > /sys/devices/platform/sony-laptop/brightness_default | ||
50 | sets the highest screen brightness for the next and later reboots, | ||
51 | # cat /sys/devices/platform/sony-laptop/brightness_default | ||
52 | retrieves the value. | ||
53 | |||
54 | # echo "0" > /sys/devices/platform/sony-laptop/audiopower | ||
55 | powers off the sound card, | ||
56 | # echo "1" > /sys/devices/platform/sony-laptop/audiopower | ||
57 | powers on the sound card. | ||
58 | |||
59 | Development: | ||
60 | ------------ | ||
61 | |||
62 | If you want to help with the development of this driver (and | ||
63 | you are not afraid of any side effects doing strange things with | ||
64 | your ACPI BIOS could have on your laptop), load the driver and | ||
65 | pass the option 'debug=1'. | ||
66 | |||
67 | REPEAT: DON'T DO THIS IF YOU DON'T LIKE RISKY BUSINESS. | ||
68 | |||
69 | In your kernel logs you will find the list of all ACPI methods | ||
70 | the SNC device has on your laptop. You can see the GCDP/GCDP methods | ||
71 | used to pwer on/off the CD drive, but there are others. | ||
72 | |||
73 | I HAVE NO IDEA WHAT THOSE METHODS DO. | ||
74 | |||
75 | The sony-laptop driver creates, for some of those methods (the most | ||
76 | current ones found on several Vaio models), an entry under | ||
77 | /sys/devices/platform/sony-laptop, just like the 'cdpower' one. | ||
78 | You can create other entries corresponding to your own laptop methods by | ||
79 | further editing the source (see the 'sony_acpi_values' table, and add a new | ||
80 | entry to this table with your get/set method names using the | ||
81 | HANDLE_NAMES macro). | ||
82 | |||
83 | Your mission, should you accept it, is to try finding out what | ||
84 | those entries are for, by reading/writing random values from/to those | ||
85 | files and find out what is the impact on your laptop. | ||
86 | |||
87 | Should you find anything interesting, please report it back to me, | ||
88 | I will not disavow all knowledge of your actions :) | ||
89 | |||
90 | Bugs/Limitations: | ||
91 | ----------------- | ||
92 | |||
93 | * This driver is not based on official documentation from Sony | ||
94 | (because there is none), so there is no guarantee this driver | ||
95 | will work at all, or do the right thing. Although this hasn't | ||
96 | happened to me, this driver could do very bad things to your | ||
97 | laptop, including permanent damage. | ||
98 | |||
99 | * The sony-laptop and sonypi drivers do not interact at all. In the | ||
100 | future, sonypi could use sony-laptop to do (part of) its business. | ||
101 | |||
102 | * spicctrl, which is the userspace tool used to communicate with the | ||
103 | sonypi driver (through /dev/sonypi) does not try to use the | ||
104 | sony-laptop driver. In the future, spicctrl could try sonypi first, | ||
105 | and if it isn't present, try sony-laptop instead. | ||
106 | |||