android/android_kernel_xiaomi_sm8450
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[PATCH] Doc/hpet.txt: change to < 80 columns

Browse Source 
Put text into < 80 columns.  No other changes.

Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
This commit is contained in:
Randy Dunlap 2005-11-07 01:01:06 -08:00 committed by Linus Torvalds
parent 8f2709b542
commit 8a0d490069
1 changed files with 17 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
Documentation/hpet.txt
View File

@ -1,18 +1,21 @@
High Precision Event Timer Driver for Linux High Precision Event Timer Driver for Linux
The High Precision Event Timer (HPET) hardware is the future replacement for the 8254 and Real The High Precision Event Timer (HPET) hardware is the future replacement
Time Clock (RTC) periodic timer functionality. Each HPET can have up two 32 timers. It is possible for the 8254 and Real Time Clock (RTC) periodic timer functionality.
to configure the first two timers as legacy replacements for 8254 and RTC periodic. A specification Each HPET can have up two 32 timers. It is possible to configure the
done by INTEL and Microsoft can be found at http://www.intel.com/labs/platcomp/hpet/hpetspec.htm. first two timers as legacy replacements for 8254 and RTC periodic timers.
A specification done by Intel and Microsoft can be found at
<http://www.intel.com/hardwaredesign/hpetspec.htm>.
The driver supports detection of HPET driver allocation and initialization of the HPET before the The driver supports detection of HPET driver allocation and initialization
driver module_init routine is called. This enables platform code which uses timer 0 or 1 as the of the HPET before the driver module_init routine is called. This enables
main timer to intercept HPET initialization. An example of this initialization can be found in platform code which uses timer 0 or 1 as the main timer to intercept HPET
initialization. An example of this initialization can be found in
arch/i386/kernel/time_hpet.c. arch/i386/kernel/time_hpet.c.
The driver provides two APIs which are very similar to the API found in the rtc.c driver. The driver provides two APIs which are very similar to the API found in
There is a user space API and a kernel space API. An example user space program is provided the rtc.c driver. There is a user space API and a kernel space API.
below. An example user space program is provided below.
#include <stdio.h> #include <stdio.h>
#include <stdlib.h> #include <stdlib.h>
@ -290,9 +293,8 @@ The kernel API has three interfaces exported from the driver:
hpet_unregister(struct hpet_task *tp) hpet_unregister(struct hpet_task *tp)
hpet_control(struct hpet_task *tp, unsigned int cmd, unsigned long arg) hpet_control(struct hpet_task *tp, unsigned int cmd, unsigned long arg)
The kernel module using this interface fills in the ht_func and ht_data members of the The kernel module using this interface fills in the ht_func and ht_data
hpet_task structure before calling hpet_register. hpet_control simply vectors to the hpet_ioctl members of the hpet_task structure before calling hpet_register.
routine and has the same commands and respective arguments as the user API. hpet_unregister hpet_control simply vectors to the hpet_ioctl routine and has the same
commands and respective arguments as the user API. hpet_unregister
is used to terminate usage of the HPET timer reserved by hpet_register. is used to terminate usage of the HPET timer reserved by hpet_register.