Searched full:machine (Results 1 – 25 of 328) sorted by relevance
12345678910>>...14
| /Documentation/sound/soc/ |
| D | machine.rst | 2 ASoC Machine Driver
5 The ASoC machine (or board) driver is the code that glues together all the
10 The machine driver can contain codec and platform specific code. It registers
15 /* SoC machine */
42 probe/remove are optional. Do any machine specific probe here.
47 The machine driver has pre and post versions of suspend and resume to take care
48 of any machine audio tasks that have to be done before or after the codec, DAIs
52 Machine DAI Configuration
54 The machine DAI configuration glues all the codec and CPU DAIs together. It can
55 also be used to set up the DAI system clock and for any machine related DAI
[all …]
|
| D | dapm.rst | 19 DAPM spans the whole machine. It covers power control within the entire
20 audio subsystem, this includes internal codec power blocks and machine
31 Platform/Machine domain
34 Is platform/machine and user action specific, is configured by the
35 machine driver and responds to asynchronous events e.g when HP
51 routing map of the whole machine. This map is specific to each machine and
195 Machine domain Widgets
198 Machine widgets are different from codec widgets in that they don't have a
199 codec register bit associated with them. A machine widget is assigned to each
200 machine audio component (non codec or DSP) that can be independently
[all …]
|
| D | overview.rst | 18 machine specific code to re-route audio, enable amps, etc., after such an
50 * Machine specific controls: Allow machines to add controls to the sound card
60 on any architecture and machine.
66 * Machine class driver: The machine driver class acts as the glue that
68 "sound card device". It handles any machine specific controls and
69 machine level audio events (e.g. turning on an amp at start of playback).
|
| D | jack.rst | 34 machine driver and updated by jack detection methods.
36 Jacks are created by the machine driver calling snd_soc_jack_new().
43 which are updated automatically. They are created by the machine driver
55 be set up by the machine driver, taking configuration for the jack to
66 Machine drivers
69 These are all hooked together by the machine driver depending on the
70 system hardware. The machine driver will set up the snd_soc_jack and
|
| /Documentation/x86/x86_64/ |
| D | machinecheck.rst | 4 Configurable sysfs parameters for the x86-64 machine check code
7 Machine checks report internal hardware error conditions detected
8 by the CPU. Uncorrected errors typically cause a machine check
9 (often with panic), corrected ones cause a machine check log entry.
11 Machine checks are organized in banks (normally associated with
17 When you see the "Machine check errors logged" message in the system
18 log then mcelog should run to collect and decode machine check entries
40 How often to poll for corrected machine check errors, in seconds
46 maximum polling interval. 0 means no polling for corrected machine
51 Tolerance level. When a machine check exception occurs for a non
[all …]
|
| D | boot-options.rst | 10 Machine check
15 Disable machine check
17 Disable CMCI(Corrected Machine Check Interrupt) that
42 Enable logging of machine checks left over from booting.
46 to make sure you log even machine check events that result
49 Disable boot machine check logging.
59 Sets the time in us to wait for other CPUs on machine checks. 0
69 Force-enable recoverable machine check code paths
|
| /Documentation/arm/ |
| D | arm.rst | 71 `arch-*` machine/platform specific header files
73 `mach` descriptions of generic ARM to specific machine interfaces
79 Machine/Platform support
82 The ARM tree contains support for a lot of different machine types. To
84 machine-specific parts by directory. For this, the machine category is
86 $(MACHINE) to refer to the category)
88 To this end, we now have arch/arm/mach-$(MACHINE) directories which are
89 designed to house the non-driver files for a particular machine (eg, PCI,
91 machines, there should be a corresponding arch/arm/mach-$(MACHINE)/include/mach
99 each module on an ARM2/ARM250/ARM3 machine when is loaded will take
[all …]
|
| D | booting.rst | 21 3. Detect the machine type.
37 this in a machine dependent manner. (It may use internal algorithms
39 the RAM in the machine, or any other method the boot loader designer
63 3. Detect the machine type
71 The boot loader should detect the machine type its running on by some
78 For DT-only platforms, the machine type will be determined by device
79 tree. set the machine type to all ones (~0). This is not strictly
193 - r1 = machine type number discovered in (3) above.
|
| D | interrupts.rst | 19 Unfortunately, this means that machine types that touch the irq_desc[]
20 array (basically all machine types) will break, and this means every
21 machine type that we currently have.
121 1. Machine implementations must not write to the irqdesc array.
124 to be useful only to machine specific code. The last is recommended to
125 only be used by machine specific code, but may be used in drivers if
|
| D | porting.rst | 11 __virt_to_phys() does for your machine. This macro converts the passed
129 Machine specific fixups, run before memory subsystems have been
133 Machine specific function to map IO areas (including the debug
137 Machine specific function to initialise interrupts.
|
| /Documentation/ABI/testing/ |
| D | sysfs-platform-dell-smbios | 7 available on the machine.
19 Tokens will vary from machine to machine, and
20 only tokens available on that machine will be
|
| D | debugfs-ideapad | 7 cfg shows the return value of _CFG method in VPC2004 device. It tells machine
8 capability and what graphic component within the machine.
|
| /Documentation/dev-tools/ |
| D | gcov.rst | 123 box for setups where kernels are built and run on the same machine. In
124 cases where the kernel runs on a separate machine, special preparations
127 a) gcov is run on the TEST machine
129 The gcov tool version on the test machine must be compatible with the
131 copied from build to test machine:
142 exact same file system location on the test machine as on the build
143 machine. If any of the path components is symbolic link, the actual
146 b) gcov is run on the BUILD machine
149 to build machine:
155 These files can be copied to any location on the build machine. gcov
[all …]
|
| /Documentation/power/regulator/ |
| D | machine.rst | 2 Regulator Machine Driver Interface
5 The regulator machine driver interface is intended for board/machine specific
8 Consider the following machine::
15 order to control their power supplies. This mapping can be achieved in machine
24 e.g. for the machine above::
|
| /Documentation/arm/spear/ |
| D | overview.rst | 38 A generic configuration is provided for each machine, and can be used as the
48 The common files for multiple machine families (SPEAr3xx, SPEAr6xx and
52 Each machine series have a directory with name arch/arm/mach-spear followed by
57 mach-spear13xx/spear13xx.c. mach-spear* also contain soc/machine specific
|
| /Documentation/devicetree/bindings/sound/ |
| D | mt2701-cs42448.txt | 4 - compatible: "mediatek,mt2701-cs42448-machine"
17 compatible = "mediatek,mt2701-cs42448-machine";
19 /* CS42448 Machine name */
|
| D | mt2701-wm8960.txt | 4 - compatible: "mediatek,mt2701-wm8960-machine"
14 compatible = "mediatek,mt2701-wm8960-machine";
|
| /Documentation/crypto/ |
| D | descore-readme.txt | 74 compiler machine desCore libdes ALT_ECB slower by
102 to use only 128k. his tables and code are machine independent.
108 the tables used seem to be machine-independent;
111 when the machine's architecture allows it.
125 machine-independent.
128 UC Berkeley code (depends on machine-endedness):
172 which depended on endedness and other machine quirks,
176 obfuscate the code and in the end were slower than a simpler machine
200 whichever one is closest to the capabilities of your machine.
205 ROR and ROL macros to use machine rotate instructions if you have them.
[all …]
|
| /Documentation/driver-api/ |
| D | regulator.rst | 70 by the machine interface.
83 Note that since multiple consumers may be using a regulator and machine
122 Machine interface
134 time as part of the machine constraints.
139 As well as defining the connections the machine interface also provides
163 .. kernel-doc:: include/linux/regulator/machine.h
|
| /Documentation/devicetree/bindings/reserved-memory/ |
| D | xen,shared-memory.txt | 4 virtual machine. Typically, a region is configured at VM creation time
19 64 bit integer offset within the owner virtual machine's shared
|
| /Documentation/devicetree/bindings/arm/msm/ |
| D | qcom,idle-state.txt | 16 trigger to execute the SPM state machine. The SPM state machine waits for the
19 the SPM state machine out of its wait, the next step is to ensure that the
22 driver and is not defined in the DT. The SPM state machine should be
|
| /Documentation/networking/ |
| D | PLIP.txt | 80 There is a performance drop on the machine hosting the driver.
100 in which case a long timeout would stall the machine when, for whatever
127 data bit outputs of the first port (machine T) connected to the
128 status bit inputs of the second port (machine R). There are five
161 ``printer'' (as opposed to ``parallel'') ports or when the machine
203 To start a transfer the transmitting machine outputs a nibble 0x08.
205 machine. The receiving machine disables interrupts and raises its own ACK
|
| /Documentation/filesystems/caching/ |
| D | object.txt | 11 (*) Object management state machine.
93 OBJECT MANAGEMENT STATE MACHINE
97 machine. The state for an object is kept in the fscache_object struct, in
101 Each state has an action associated with it that is invoked when the machine
148 state machine at once, this simplifies the locking, particularly with respect
158 The object state machine has a set of states that it can be in. There are
228 The state machine comes here to update the object in the cache from the
281 There are a number of events that can be raised to an object state machine:
285 The netfs requested that an object be updated. The state machine will ask
318 state machine, it doesn't matter if there's a collision with both ends trying
[all …]
|
| /Documentation/sparc/oradax/ |
| D | dax-hv-api.txt | 1 Excerpt from UltraSPARC Virtual Machine Specification
22 functionality offered may vary by virtual machine implementation.
39 …machine, however, internal resource limitations within the virtual machine can cause CCB submissio…
235 …interpreted by the virtual machine. Not all of the types specified are used by every CCB format. T…
238 …e submitting virtual processor. Virtual addresses which cannot be translated by the virtual machine
391 …value. The page size must be one of the sizes supported by the underlying virtual machine. Using a…
419 machine:
485 the virtual machine to use when accessing this data stream
576 … the virtual machine to use when accessing this data stream
622 machine:
[all …]
|
| /Documentation/w1/masters/ |
| D | w1-gpio.rst | 12 wire and the GPIO pin can be specified using GPIO machine descriptor tables.
22 #include <linux/gpio/machine.h>
|
12345678910>>...14