diff options
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/00-INDEX | 4 | ||||
-rw-r--r-- | Documentation/DMA-API-HOWTO.txt | 10 | ||||
-rw-r--r-- | Documentation/DMA-API.txt | 6 | ||||
-rw-r--r-- | Documentation/DocBook/Makefile | 4 | ||||
-rw-r--r-- | Documentation/DocBook/kernel-api.tmpl | 1 | ||||
-rw-r--r-- | Documentation/feature-removal-schedule.txt | 17 | ||||
-rw-r--r-- | Documentation/filesystems/squashfs.txt | 2 | ||||
-rw-r--r-- | Documentation/gpio.txt | 35 | ||||
-rw-r--r-- | Documentation/kernel-parameters.txt | 3 | ||||
-rw-r--r-- | Documentation/mmc/00-INDEX | 4 | ||||
-rw-r--r-- | Documentation/mmc/mmc-dev-attrs.txt | 56 | ||||
-rw-r--r-- | Documentation/networking/wavelan.txt | 74 | ||||
-rw-r--r-- | Documentation/padata.txt | 24 | ||||
-rw-r--r-- | Documentation/powerpc/dts-bindings/fsl/esdhc.txt | 2 | ||||
-rw-r--r-- | Documentation/sound/alsa/HD-Audio-Models.txt | 13 |
15 files changed, 146 insertions, 109 deletions
diff --git a/Documentation/00-INDEX b/Documentation/00-INDEX index 5405f7aecefc..8dfc6708a257 100644 --- a/Documentation/00-INDEX +++ b/Documentation/00-INDEX | |||
@@ -130,8 +130,6 @@ edac.txt | |||
130 | - information on EDAC - Error Detection And Correction | 130 | - information on EDAC - Error Detection And Correction |
131 | eisa.txt | 131 | eisa.txt |
132 | - info on EISA bus support. | 132 | - info on EISA bus support. |
133 | exception.txt | ||
134 | - how Linux v2.2 handles exceptions without verify_area etc. | ||
135 | fault-injection/ | 133 | fault-injection/ |
136 | - dir with docs about the fault injection capabilities infrastructure. | 134 | - dir with docs about the fault injection capabilities infrastructure. |
137 | fb/ | 135 | fb/ |
@@ -234,6 +232,8 @@ memory.txt | |||
234 | - info on typical Linux memory problems. | 232 | - info on typical Linux memory problems. |
235 | mips/ | 233 | mips/ |
236 | - directory with info about Linux on MIPS architecture. | 234 | - directory with info about Linux on MIPS architecture. |
235 | mmc/ | ||
236 | - directory with info about the MMC subsystem | ||
237 | mono.txt | 237 | mono.txt |
238 | - how to execute Mono-based .NET binaries with the help of BINFMT_MISC. | 238 | - how to execute Mono-based .NET binaries with the help of BINFMT_MISC. |
239 | mutex-design.txt | 239 | mutex-design.txt |
diff --git a/Documentation/DMA-API-HOWTO.txt b/Documentation/DMA-API-HOWTO.txt index 98ce51796f71..3c4e07123e59 100644 --- a/Documentation/DMA-API-HOWTO.txt +++ b/Documentation/DMA-API-HOWTO.txt | |||
@@ -753,6 +753,16 @@ to "Closing". | |||
753 | alignment constraints (e.g. the alignment constraints about 64-bit | 753 | alignment constraints (e.g. the alignment constraints about 64-bit |
754 | objects). | 754 | objects). |
755 | 755 | ||
756 | 3) Supporting multiple types of IOMMUs | ||
757 | |||
758 | If your architecture needs to support multiple types of IOMMUs, you | ||
759 | can use include/linux/asm-generic/dma-mapping-common.h. It's a | ||
760 | library to support the DMA API with multiple types of IOMMUs. Lots | ||
761 | of architectures (x86, powerpc, sh, alpha, ia64, microblaze and | ||
762 | sparc) use it. Choose one to see how it can be used. If you need to | ||
763 | support multiple types of IOMMUs in a single system, the example of | ||
764 | x86 or powerpc helps. | ||
765 | |||
756 | Closing | 766 | Closing |
757 | 767 | ||
758 | This document, and the API itself, would not be in its current | 768 | This document, and the API itself, would not be in its current |
diff --git a/Documentation/DMA-API.txt b/Documentation/DMA-API.txt index 05e2ae236865..fe2326906610 100644 --- a/Documentation/DMA-API.txt +++ b/Documentation/DMA-API.txt | |||
@@ -456,12 +456,6 @@ be identical to those passed in (and returned by | |||
456 | dma_alloc_noncoherent()). | 456 | dma_alloc_noncoherent()). |
457 | 457 | ||
458 | int | 458 | int |
459 | dma_is_consistent(struct device *dev, dma_addr_t dma_handle) | ||
460 | |||
461 | Returns true if the device dev is performing consistent DMA on the memory | ||
462 | area pointed to by the dma_handle. | ||
463 | |||
464 | int | ||
465 | dma_get_cache_alignment(void) | 459 | dma_get_cache_alignment(void) |
466 | 460 | ||
467 | Returns the processor cache alignment. This is the absolute minimum | 461 | Returns the processor cache alignment. This is the absolute minimum |
diff --git a/Documentation/DocBook/Makefile b/Documentation/DocBook/Makefile index 4b603c5c3cc1..34929f24c284 100644 --- a/Documentation/DocBook/Makefile +++ b/Documentation/DocBook/Makefile | |||
@@ -35,7 +35,7 @@ PS_METHOD = $(prefer-db2x) | |||
35 | PHONY += xmldocs sgmldocs psdocs pdfdocs htmldocs mandocs installmandocs cleandocs xmldoclinks | 35 | PHONY += xmldocs sgmldocs psdocs pdfdocs htmldocs mandocs installmandocs cleandocs xmldoclinks |
36 | 36 | ||
37 | BOOKS := $(addprefix $(obj)/,$(DOCBOOKS)) | 37 | BOOKS := $(addprefix $(obj)/,$(DOCBOOKS)) |
38 | xmldocs: $(BOOKS) xmldoclinks | 38 | xmldocs: $(BOOKS) |
39 | sgmldocs: xmldocs | 39 | sgmldocs: xmldocs |
40 | 40 | ||
41 | PS := $(patsubst %.xml, %.ps, $(BOOKS)) | 41 | PS := $(patsubst %.xml, %.ps, $(BOOKS)) |
@@ -95,7 +95,7 @@ define rule_docproc | |||
95 | ) > $(dir $@).$(notdir $@).cmd | 95 | ) > $(dir $@).$(notdir $@).cmd |
96 | endef | 96 | endef |
97 | 97 | ||
98 | %.xml: %.tmpl FORCE | 98 | %.xml: %.tmpl xmldoclinks FORCE |
99 | $(call if_changed_rule,docproc) | 99 | $(call if_changed_rule,docproc) |
100 | 100 | ||
101 | ### | 101 | ### |
diff --git a/Documentation/DocBook/kernel-api.tmpl b/Documentation/DocBook/kernel-api.tmpl index 44b3def961a2..a20c6f6fffc3 100644 --- a/Documentation/DocBook/kernel-api.tmpl +++ b/Documentation/DocBook/kernel-api.tmpl | |||
@@ -132,7 +132,6 @@ X!Ilib/string.c | |||
132 | <title>FIFO Buffer</title> | 132 | <title>FIFO Buffer</title> |
133 | <sect1><title>kfifo interface</title> | 133 | <sect1><title>kfifo interface</title> |
134 | !Iinclude/linux/kfifo.h | 134 | !Iinclude/linux/kfifo.h |
135 | !Ekernel/kfifo.c | ||
136 | </sect1> | 135 | </sect1> |
137 | </chapter> | 136 | </chapter> |
138 | 137 | ||
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt index b16cbe4152ea..842aa9de84a6 100644 --- a/Documentation/feature-removal-schedule.txt +++ b/Documentation/feature-removal-schedule.txt | |||
@@ -547,3 +547,20 @@ Why: superseded by acpi_sleep=nonvs | |||
547 | Who: Rafael J. Wysocki <rjw@sisk.pl> | 547 | Who: Rafael J. Wysocki <rjw@sisk.pl> |
548 | 548 | ||
549 | ---------------------------- | 549 | ---------------------------- |
550 | |||
551 | What: PCI DMA unmap state API | ||
552 | When: August 2012 | ||
553 | Why: PCI DMA unmap state API (include/linux/pci-dma.h) was replaced | ||
554 | with DMA unmap state API (DMA unmap state API can be used for | ||
555 | any bus). | ||
556 | Who: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> | ||
557 | |||
558 | ---------------------------- | ||
559 | |||
560 | What: DMA_xxBIT_MASK macros | ||
561 | When: Jun 2011 | ||
562 | Why: DMA_xxBIT_MASK macros were replaced with DMA_BIT_MASK() macros. | ||
563 | Who: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> | ||
564 | |||
565 | ---------------------------- | ||
566 | |||
diff --git a/Documentation/filesystems/squashfs.txt b/Documentation/filesystems/squashfs.txt index 203f7202cc9e..66699afd66ca 100644 --- a/Documentation/filesystems/squashfs.txt +++ b/Documentation/filesystems/squashfs.txt | |||
@@ -2,7 +2,7 @@ SQUASHFS 4.0 FILESYSTEM | |||
2 | ======================= | 2 | ======================= |
3 | 3 | ||
4 | Squashfs is a compressed read-only filesystem for Linux. | 4 | Squashfs is a compressed read-only filesystem for Linux. |
5 | It uses zlib compression to compress files, inodes and directories. | 5 | It uses zlib/lzo compression to compress files, inodes and directories. |
6 | Inodes in the system are very small and all blocks are packed to minimise | 6 | Inodes in the system are very small and all blocks are packed to minimise |
7 | data overhead. Block sizes greater than 4K are supported up to a maximum | 7 | data overhead. Block sizes greater than 4K are supported up to a maximum |
8 | of 1Mbytes (default block size 128K). | 8 | of 1Mbytes (default block size 128K). |
diff --git a/Documentation/gpio.txt b/Documentation/gpio.txt index c2c6e9b39bbe..d96a6dba5748 100644 --- a/Documentation/gpio.txt +++ b/Documentation/gpio.txt | |||
@@ -158,10 +158,11 @@ and configure pullups/pulldowns appropriately.) | |||
158 | Spinlock-Safe GPIO access | 158 | Spinlock-Safe GPIO access |
159 | ------------------------- | 159 | ------------------------- |
160 | Most GPIO controllers can be accessed with memory read/write instructions. | 160 | Most GPIO controllers can be accessed with memory read/write instructions. |
161 | That doesn't need to sleep, and can safely be done from inside IRQ handlers. | 161 | Those don't need to sleep, and can safely be done from inside hard |
162 | (That includes hardirq contexts on RT kernels.) | 162 | (nonthreaded) IRQ handlers and similar contexts. |
163 | 163 | ||
164 | Use these calls to access such GPIOs: | 164 | Use the following calls to access such GPIOs, |
165 | for which gpio_cansleep() will always return false (see below): | ||
165 | 166 | ||
166 | /* GPIO INPUT: return zero or nonzero */ | 167 | /* GPIO INPUT: return zero or nonzero */ |
167 | int gpio_get_value(unsigned gpio); | 168 | int gpio_get_value(unsigned gpio); |
@@ -210,9 +211,31 @@ To access such GPIOs, a different set of accessors is defined: | |||
210 | /* GPIO OUTPUT, might sleep */ | 211 | /* GPIO OUTPUT, might sleep */ |
211 | void gpio_set_value_cansleep(unsigned gpio, int value); | 212 | void gpio_set_value_cansleep(unsigned gpio, int value); |
212 | 213 | ||
213 | Other than the fact that these calls might sleep, and will not be ignored | 214 | |
214 | for GPIOs that can't be accessed from IRQ handlers, these calls act the | 215 | Accessing such GPIOs requires a context which may sleep, for example |
215 | same as the spinlock-safe calls. | 216 | a threaded IRQ handler, and those accessors must be used instead of |
217 | spinlock-safe accessors without the cansleep() name suffix. | ||
218 | |||
219 | Other than the fact that these accessors might sleep, and will work | ||
220 | on GPIOs that can't be accessed from hardIRQ handlers, these calls act | ||
221 | the same as the spinlock-safe calls. | ||
222 | |||
223 | ** IN ADDITION ** calls to setup and configure such GPIOs must be made | ||
224 | from contexts which may sleep, since they may need to access the GPIO | ||
225 | controller chip too: (These setup calls are usually made from board | ||
226 | setup or driver probe/teardown code, so this is an easy constraint.) | ||
227 | |||
228 | gpio_direction_input() | ||
229 | gpio_direction_output() | ||
230 | gpio_request() | ||
231 | |||
232 | ## gpio_request_one() | ||
233 | ## gpio_request_array() | ||
234 | ## gpio_free_array() | ||
235 | |||
236 | gpio_free() | ||
237 | gpio_set_debounce() | ||
238 | |||
216 | 239 | ||
217 | 240 | ||
218 | Claiming and Releasing GPIOs | 241 | Claiming and Releasing GPIOs |
diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt index d529b1363e95..873b68090098 100644 --- a/Documentation/kernel-parameters.txt +++ b/Documentation/kernel-parameters.txt | |||
@@ -915,9 +915,6 @@ and is between 256 and 4096 characters. It is defined in the file | |||
915 | controller | 915 | controller |
916 | i8042.nopnp [HW] Don't use ACPIPnP / PnPBIOS to discover KBD/AUX | 916 | i8042.nopnp [HW] Don't use ACPIPnP / PnPBIOS to discover KBD/AUX |
917 | controllers | 917 | controllers |
918 | i8042.panicblink= | ||
919 | [HW] Frequency with which keyboard LEDs should blink | ||
920 | when kernel panics (default is 0.5 sec) | ||
921 | i8042.reset [HW] Reset the controller during init and cleanup | 918 | i8042.reset [HW] Reset the controller during init and cleanup |
922 | i8042.unlock [HW] Unlock (ignore) the keylock | 919 | i8042.unlock [HW] Unlock (ignore) the keylock |
923 | 920 | ||
diff --git a/Documentation/mmc/00-INDEX b/Documentation/mmc/00-INDEX new file mode 100644 index 000000000000..fca586f5b853 --- /dev/null +++ b/Documentation/mmc/00-INDEX | |||
@@ -0,0 +1,4 @@ | |||
1 | 00-INDEX | ||
2 | - this file | ||
3 | mmc-dev-attrs.txt | ||
4 | - info on SD and MMC device attributes | ||
diff --git a/Documentation/mmc/mmc-dev-attrs.txt b/Documentation/mmc/mmc-dev-attrs.txt new file mode 100644 index 000000000000..ff2bd685bced --- /dev/null +++ b/Documentation/mmc/mmc-dev-attrs.txt | |||
@@ -0,0 +1,56 @@ | |||
1 | SD and MMC Device Attributes | ||
2 | ============================ | ||
3 | |||
4 | All attributes are read-only. | ||
5 | |||
6 | cid Card Identifaction Register | ||
7 | csd Card Specific Data Register | ||
8 | scr SD Card Configuration Register (SD only) | ||
9 | date Manufacturing Date (from CID Register) | ||
10 | fwrev Firmware/Product Revision (from CID Register) (SD and MMCv1 only) | ||
11 | hwrev Hardware/Product Revision (from CID Register) (SD and MMCv1 only) | ||
12 | manfid Manufacturer ID (from CID Register) | ||
13 | name Product Name (from CID Register) | ||
14 | oemid OEM/Application ID (from CID Register) | ||
15 | serial Product Serial Number (from CID Register) | ||
16 | erase_size Erase group size | ||
17 | preferred_erase_size Preferred erase size | ||
18 | |||
19 | Note on Erase Size and Preferred Erase Size: | ||
20 | |||
21 | "erase_size" is the minimum size, in bytes, of an erase | ||
22 | operation. For MMC, "erase_size" is the erase group size | ||
23 | reported by the card. Note that "erase_size" does not apply | ||
24 | to trim or secure trim operations where the minimum size is | ||
25 | always one 512 byte sector. For SD, "erase_size" is 512 | ||
26 | if the card is block-addressed, 0 otherwise. | ||
27 | |||
28 | SD/MMC cards can erase an arbitrarily large area up to and | ||
29 | including the whole card. When erasing a large area it may | ||
30 | be desirable to do it in smaller chunks for three reasons: | ||
31 | 1. A single erase command will make all other I/O on | ||
32 | the card wait. This is not a problem if the whole card | ||
33 | is being erased, but erasing one partition will make | ||
34 | I/O for another partition on the same card wait for the | ||
35 | duration of the erase - which could be a several | ||
36 | minutes. | ||
37 | 2. To be able to inform the user of erase progress. | ||
38 | 3. The erase timeout becomes too large to be very | ||
39 | useful. Because the erase timeout contains a margin | ||
40 | which is multiplied by the size of the erase area, | ||
41 | the value can end up being several minutes for large | ||
42 | areas. | ||
43 | |||
44 | "erase_size" is not the most efficient unit to erase | ||
45 | (especially for SD where it is just one sector), | ||
46 | hence "preferred_erase_size" provides a good chunk | ||
47 | size for erasing large areas. | ||
48 | |||
49 | For MMC, "preferred_erase_size" is the high-capacity | ||
50 | erase size if a card specifies one, otherwise it is | ||
51 | based on the capacity of the card. | ||
52 | |||
53 | For SD, "preferred_erase_size" is the allocation unit | ||
54 | size specified by the card. | ||
55 | |||
56 | "preferred_erase_size" is in bytes. | ||
diff --git a/Documentation/networking/wavelan.txt b/Documentation/networking/wavelan.txt deleted file mode 100644 index 90e0ac4e15da..000000000000 --- a/Documentation/networking/wavelan.txt +++ /dev/null | |||
@@ -1,74 +0,0 @@ | |||
1 | The Wavelan drivers saga | ||
2 | ------------------------ | ||
3 | |||
4 | By Jean Tourrilhes <jt@hpl.hp.com> | ||
5 | |||
6 | The Wavelan is a Radio network adapter designed by | ||
7 | Lucent. Under this generic name is hidden quite a variety of hardware, | ||
8 | and many Linux driver to support it. | ||
9 | The get the full story on Wireless LANs, please consult : | ||
10 | http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/ | ||
11 | |||
12 | "wavelan" driver (old ISA Wavelan) | ||
13 | ---------------- | ||
14 | o Config : Network device -> Wireless LAN -> AT&T WaveLAN | ||
15 | o Location : .../drivers/net/wireless/wavelan* | ||
16 | o in-line doc : .../drivers/net/wireless/wavelan.p.h | ||
17 | o on-line doc : | ||
18 | http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Wavelan.html | ||
19 | |||
20 | This is the driver for the ISA version of the first generation | ||
21 | of the Wavelan, now discontinued. The device is 2 Mb/s, composed of a | ||
22 | Intel 82586 controller and a Lucent Modem, and is NOT 802.11 compliant. | ||
23 | The driver has been tested with the following hardware : | ||
24 | o Wavelan ISA 915 MHz (full length ISA card) | ||
25 | o Wavelan ISA 915 MHz 2.0 (half length ISA card) | ||
26 | o Wavelan ISA 2.4 GHz (full length ISA card, fixed frequency) | ||
27 | o Wavelan ISA 2.4 GHz 2.0 (half length ISA card, frequency selectable) | ||
28 | o Above cards with the optional DES encryption feature | ||
29 | |||
30 | "wavelan_cs" driver (old Pcmcia Wavelan) | ||
31 | ------------------- | ||
32 | o Config : Network device -> PCMCIA network -> | ||
33 | Pcmcia Wireless LAN -> AT&T/Lucent WaveLAN | ||
34 | o Location : .../drivers/net/pcmcia/wavelan* | ||
35 | o in-line doc : .../drivers/net/pcmcia/wavelan_cs.h | ||
36 | o on-line doc : | ||
37 | http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Wavelan.html | ||
38 | |||
39 | This is the driver for the PCMCIA version of the first | ||
40 | generation of the Wavelan, now discontinued. The device is 2 Mb/s, | ||
41 | composed of a Intel 82593 controller (totally different from the 82586) | ||
42 | and a Lucent Modem, and NOT 802.11 compatible. | ||
43 | The driver has been tested with the following hardware : | ||
44 | o Wavelan Pcmcia 915 MHz 2.0 (Pcmcia card + separate | ||
45 | modem/antenna block) | ||
46 | o Wavelan Pcmcia 2.4 GHz 2.0 (Pcmcia card + separate | ||
47 | modem/antenna block) | ||
48 | |||
49 | "wvlan_cs" driver (Wavelan IEEE, GPL) | ||
50 | ----------------- | ||
51 | o Config : Not yet in kernel | ||
52 | o Location : Pcmcia package 3.1.10+ | ||
53 | o on-line doc : | ||
54 | http://web.archive.org/web/*/http://www.fasta.fh-dortmund.de/users/andy/wvlan/ | ||
55 | |||
56 | This is the driver for the current generation of Wavelan IEEE, | ||
57 | which is 802.11 compatible. Depending on version, it is 2 Mb/s or 11 | ||
58 | Mb/s, with or without encryption, all implemented in Lucent specific | ||
59 | DSP (the Hermes). | ||
60 | This is a GPL full source PCMCIA driver (ISA is just a Pcmcia | ||
61 | card with ISA-Pcmcia bridge). | ||
62 | |||
63 | "wavelan2_cs" driver (Wavelan IEEE, binary) | ||
64 | -------------------- | ||
65 | o Config : Not yet in kernel | ||
66 | o Location : ftp://sourceforge.org/pcmcia/contrib/ | ||
67 | |||
68 | This driver support exactly the same hardware as the previous | ||
69 | driver, the main difference is that it is based on a binary library | ||
70 | and supported by Lucent. | ||
71 | |||
72 | I hope it clears the confusion ;-) | ||
73 | |||
74 | Jean | ||
diff --git a/Documentation/padata.txt b/Documentation/padata.txt index 473ebf22cd69..7ddfe216a0aa 100644 --- a/Documentation/padata.txt +++ b/Documentation/padata.txt | |||
@@ -19,7 +19,7 @@ overall control of how tasks are to be run: | |||
19 | 19 | ||
20 | The pcpumask describes which processors will be used to execute work | 20 | The pcpumask describes which processors will be used to execute work |
21 | submitted to this instance in parallel. The cbcpumask defines which | 21 | submitted to this instance in parallel. The cbcpumask defines which |
22 | processors are allowed to use as the serialization callback processor. | 22 | processors are allowed to be used as the serialization callback processor. |
23 | The workqueue wq is where the work will actually be done; it should be | 23 | The workqueue wq is where the work will actually be done; it should be |
24 | a multithreaded queue, naturally. | 24 | a multithreaded queue, naturally. |
25 | 25 | ||
@@ -30,10 +30,10 @@ cpumasks this helper function can be used: | |||
30 | 30 | ||
31 | Note: Padata maintains two kinds of cpumasks internally. The user supplied | 31 | Note: Padata maintains two kinds of cpumasks internally. The user supplied |
32 | cpumasks, submitted by padata_alloc/padata_alloc_possible and the 'usable' | 32 | cpumasks, submitted by padata_alloc/padata_alloc_possible and the 'usable' |
33 | cpumasks. The usable cpumasks are always the subset of active cpus in the | 33 | cpumasks. The usable cpumasks are always a subset of active CPUs in the |
34 | user supplied cpumasks, these are the cpumasks padata actually use. So | 34 | user supplied cpumasks; these are the cpumasks padata actually uses. So |
35 | it is legal to supply a cpumask to padata that contains offline cpus. | 35 | it is legal to supply a cpumask to padata that contains offline CPUs. |
36 | Once a offline cpu in the user supplied cpumask comes online, padata | 36 | Once an offline CPU in the user supplied cpumask comes online, padata |
37 | is going to use it. | 37 | is going to use it. |
38 | 38 | ||
39 | There are functions for enabling and disabling the instance: | 39 | There are functions for enabling and disabling the instance: |
@@ -44,7 +44,7 @@ There are functions for enabling and disabling the instance: | |||
44 | These functions are setting or clearing the "PADATA_INIT" flag; | 44 | These functions are setting or clearing the "PADATA_INIT" flag; |
45 | if that flag is not set, other functions will refuse to work. | 45 | if that flag is not set, other functions will refuse to work. |
46 | padata_start returns zero on success (flag set) or -EINVAL if the | 46 | padata_start returns zero on success (flag set) or -EINVAL if the |
47 | padata cpumask contains no active cpu (flag not set). | 47 | padata cpumask contains no active CPU (flag not set). |
48 | padata_stop clears the flag and blocks until the padata instance | 48 | padata_stop clears the flag and blocks until the padata instance |
49 | is unused. | 49 | is unused. |
50 | 50 | ||
@@ -63,11 +63,11 @@ done with great frequency. | |||
63 | 63 | ||
64 | It's possible to change both cpumasks of a padata instance with | 64 | It's possible to change both cpumasks of a padata instance with |
65 | padata_set_cpumasks by specifying the cpumasks for parallel execution (pcpumask) | 65 | padata_set_cpumasks by specifying the cpumasks for parallel execution (pcpumask) |
66 | and for the serial callback function (cbcpumask). padata_set_cpumask is to | 66 | and for the serial callback function (cbcpumask). padata_set_cpumask is used to |
67 | change just one of the cpumasks. Here cpumask_type is one of PADATA_CPU_SERIAL, | 67 | change just one of the cpumasks. Here cpumask_type is one of PADATA_CPU_SERIAL, |
68 | PADATA_CPU_PARALLEL and cpumask specifies the new cpumask to use. | 68 | PADATA_CPU_PARALLEL and cpumask specifies the new cpumask to use. |
69 | To simply add or remove one cpu from a certain cpumask the functions | 69 | To simply add or remove one CPU from a certain cpumask the functions |
70 | padata_add_cpu/padata_remove_cpu are used. cpu specifies the cpu to add or | 70 | padata_add_cpu/padata_remove_cpu are used. cpu specifies the CPU to add or |
71 | remove and mask is one of PADATA_CPU_SERIAL, PADATA_CPU_PARALLEL. | 71 | remove and mask is one of PADATA_CPU_SERIAL, PADATA_CPU_PARALLEL. |
72 | 72 | ||
73 | If a user is interested in padata cpumask changes, he can register to | 73 | If a user is interested in padata cpumask changes, he can register to |
@@ -82,7 +82,7 @@ To unregister from that notifier: | |||
82 | struct notifier_block *nblock); | 82 | struct notifier_block *nblock); |
83 | 83 | ||
84 | The padata cpumask change notifier notifies about changes of the usable | 84 | The padata cpumask change notifier notifies about changes of the usable |
85 | cpumasks, i.e. the subset of active cpus in the user supplied cpumask. | 85 | cpumasks, i.e. the subset of active CPUs in the user supplied cpumask. |
86 | 86 | ||
87 | Padata calls the notifier chain with: | 87 | Padata calls the notifier chain with: |
88 | 88 | ||
@@ -92,7 +92,7 @@ Padata calls the notifier chain with: | |||
92 | 92 | ||
93 | Here cpumask_change_notifier is registered notifier, notification_mask | 93 | Here cpumask_change_notifier is registered notifier, notification_mask |
94 | is one of PADATA_CPU_SERIAL, PADATA_CPU_PARALLEL and cpumask is a pointer | 94 | is one of PADATA_CPU_SERIAL, PADATA_CPU_PARALLEL and cpumask is a pointer |
95 | to a struct padata_cpumask that contains the new cpumask informations. | 95 | to a struct padata_cpumask that contains the new cpumask information. |
96 | 96 | ||
97 | Actually submitting work to the padata instance requires the creation of a | 97 | Actually submitting work to the padata instance requires the creation of a |
98 | padata_priv structure: | 98 | padata_priv structure: |
@@ -104,7 +104,7 @@ padata_priv structure: | |||
104 | }; | 104 | }; |
105 | 105 | ||
106 | This structure will almost certainly be embedded within some larger | 106 | This structure will almost certainly be embedded within some larger |
107 | structure specific to the work to be done. Most its fields are private to | 107 | structure specific to the work to be done. Most of its fields are private to |
108 | padata, but the structure should be zeroed at initialisation time, and the | 108 | padata, but the structure should be zeroed at initialisation time, and the |
109 | parallel() and serial() functions should be provided. Those functions will | 109 | parallel() and serial() functions should be provided. Those functions will |
110 | be called in the process of getting the work done as we will see | 110 | be called in the process of getting the work done as we will see |
diff --git a/Documentation/powerpc/dts-bindings/fsl/esdhc.txt b/Documentation/powerpc/dts-bindings/fsl/esdhc.txt index 8a0040738969..64bcb8be973c 100644 --- a/Documentation/powerpc/dts-bindings/fsl/esdhc.txt +++ b/Documentation/powerpc/dts-bindings/fsl/esdhc.txt | |||
@@ -14,6 +14,8 @@ Required properties: | |||
14 | reports inverted write-protect state; | 14 | reports inverted write-protect state; |
15 | - sdhci,1-bit-only : (optional) specifies that a controller can | 15 | - sdhci,1-bit-only : (optional) specifies that a controller can |
16 | only handle 1-bit data transfers. | 16 | only handle 1-bit data transfers. |
17 | - sdhci,auto-cmd12: (optional) specifies that a controller can | ||
18 | only handle auto CMD12. | ||
17 | 19 | ||
18 | Example: | 20 | Example: |
19 | 21 | ||
diff --git a/Documentation/sound/alsa/HD-Audio-Models.txt b/Documentation/sound/alsa/HD-Audio-Models.txt index 03771d7c5dd7..ce46fa1e643e 100644 --- a/Documentation/sound/alsa/HD-Audio-Models.txt +++ b/Documentation/sound/alsa/HD-Audio-Models.txt | |||
@@ -83,8 +83,8 @@ ALC269 | |||
83 | ====== | 83 | ====== |
84 | basic Basic preset | 84 | basic Basic preset |
85 | quanta Quanta FL1 | 85 | quanta Quanta FL1 |
86 | eeepc-p703 ASUS Eeepc P703 P900A | 86 | laptop-amic Laptops with analog-mic input |
87 | eeepc-p901 ASUS Eeepc P901 S101 | 87 | laptop-dmic Laptops with digital-mic input |
88 | fujitsu FSC Amilo | 88 | fujitsu FSC Amilo |
89 | lifebook Fujitsu Lifebook S6420 | 89 | lifebook Fujitsu Lifebook S6420 |
90 | auto auto-config reading BIOS (default) | 90 | auto auto-config reading BIOS (default) |
@@ -109,6 +109,8 @@ ALC662/663/272 | |||
109 | asus-mode4 ASUS | 109 | asus-mode4 ASUS |
110 | asus-mode5 ASUS | 110 | asus-mode5 ASUS |
111 | asus-mode6 ASUS | 111 | asus-mode6 ASUS |
112 | asus-mode7 ASUS | ||
113 | asus-mode8 ASUS | ||
112 | dell Dell with ALC272 | 114 | dell Dell with ALC272 |
113 | dell-zm1 Dell ZM1 with ALC272 | 115 | dell-zm1 Dell ZM1 with ALC272 |
114 | samsung-nc10 Samsung NC10 mini notebook | 116 | samsung-nc10 Samsung NC10 mini notebook |
@@ -295,8 +297,10 @@ Conexant 5066 | |||
295 | ============= | 297 | ============= |
296 | laptop Basic Laptop config (default) | 298 | laptop Basic Laptop config (default) |
297 | dell-laptop Dell laptops | 299 | dell-laptop Dell laptops |
300 | dell-vostro Dell Vostro | ||
298 | olpc-xo-1_5 OLPC XO 1.5 | 301 | olpc-xo-1_5 OLPC XO 1.5 |
299 | ideapad Lenovo IdeaPad U150 | 302 | ideapad Lenovo IdeaPad U150 |
303 | thinkpad Lenovo Thinkpad | ||
300 | 304 | ||
301 | STAC9200 | 305 | STAC9200 |
302 | ======== | 306 | ======== |
@@ -404,6 +408,7 @@ STAC92HD83* | |||
404 | mic-ref Reference board with power management for ports | 408 | mic-ref Reference board with power management for ports |
405 | dell-s14 Dell laptop | 409 | dell-s14 Dell laptop |
406 | hp HP laptops with (inverted) mute-LED | 410 | hp HP laptops with (inverted) mute-LED |
411 | hp-dv7-4000 HP dv-7 4000 | ||
407 | auto BIOS setup (default) | 412 | auto BIOS setup (default) |
408 | 413 | ||
409 | STAC9872 | 414 | STAC9872 |
@@ -416,3 +421,7 @@ Cirrus Logic CS4206/4207 | |||
416 | mbp55 MacBook Pro 5,5 | 421 | mbp55 MacBook Pro 5,5 |
417 | imac27 IMac 27 Inch | 422 | imac27 IMac 27 Inch |
418 | auto BIOS setup (default) | 423 | auto BIOS setup (default) |
424 | |||
425 | VIA VT17xx/VT18xx/VT20xx | ||
426 | ======================== | ||
427 | auto BIOS setup (default) | ||