Searched full:module (Results 1 – 25 of 1197) sorted by relevance
12345678910>>...48
| /Documentation/ABI/stable/ |
| D | sysfs-module | 1 The /sys/module tree consists of the following structure:
3 What: /sys/module/<MODULENAME>
5 The name of the module that is in the kernel. This
6 module name will always show up if the module is loaded as a
7 dynamic module. If it is built directly into the kernel, it
14 What: /sys/module/<MODULENAME>/parameters
17 individual parameters of the module that are able to be
18 changed at runtime. See the individual module
28 What: /sys/module/<MODULENAME>/refcnt
30 If the module is able to be unloaded from the kernel, this file
[all …]
|
| /Documentation/sound/ |
| D | alsa-configuration.rst | 29 Module parameters
32 The user can load modules with options. If the module supports more than
37 Module snd
40 The core ALSA module. It is used by all ALSA card drivers.
54 See `Module Autoloading Support`_ section for details.
63 Module snd-pcm-oss
66 The PCM OSS emulation module.
67 This module takes options which change the mapping of devices.
90 Module snd-rawmidi
93 This module takes options which change the mapping of devices.
[all …]
|
| /Documentation/scsi/ |
| D | megaraid.rst | 4 Megaraid Common Management Module
13 the controllers uniformly. Hence it is logical to have a single module that
23 iv. Applications have to interface with only module instead of
26 Currently this module (called Common Management Module) is used only to issue
27 ioctl commands. But this module is envisioned to handle all user space level
29 common module.
36 "Shared code in a third module, a "library module", is an acceptable
39 load the shared library module."
47 then perhaps you need a single small helper module (lsiioctl or some
59 The Common Management Module is implemented in megaraid_mm.[ch] files. This
[all …]
|
| D | ChangeLog.megaraid | 3 Current Version : 2.20.5.1 (scsi module), 2.20.2.6 (cmm module)
4 Older Version : 2.20.4.9 (scsi module), 2.20.2.6 (cmm module)
18 Current Version : 2.20.4.9 (scsi module), 2.20.2.6 (cmm module)
19 Older Version : 2.20.4.8 (scsi module), 2.20.2.6 (cmm module)
141 Current Version : 2.20.4.8 (scsi module), 2.20.2.6 (cmm module)
142 Older Version : 2.20.4.7 (scsi module), 2.20.2.6 (cmm module)
166 Current Version : 2.20.4.7 (scsi module), 2.20.2.6 (cmm module)
167 Older Version : 2.20.4.6 (scsi module), 2.20.2.6 (cmm module)
201 Current Version : 2.20.4.6 (scsi module), 2.20.2.6 (cmm module)
202 Older Version : 2.20.4.5 (scsi module), 2.20.2.5 (cmm module)
[all …]
|
| /Documentation/livepatch/ |
| D | module-elf-format.rst | 2 Livepatch module ELF format
18 exists in the module loader, so this former approach produced redundant
19 code. So, instead of duplicating code and re-implementing what the module
20 loader can already do, livepatch leverages existing code in the module
22 livepatch reuses the apply_relocate_add() function in the module loader to
23 write relocations. The patch module ELF format described in this document
29 Since apply_relocate_add() requires access to a module's section header
38 A typical livepatch module contains patched versions of functions that can
41 since the kernel module loader cannot resolve them and will therefore
42 reject the livepatch module. Furthermore, we cannot apply relocations that
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-module | 1 What: /sys/module/pch_phub/drivers/.../pch_mac
7 What: /sys/module/pch_phub/drivers/.../pch_firmware
14 What: /sys/module/ehci_hcd/drivers/.../uframe_periodic_max
38 What: /sys/module/*/{coresize,initsize}
42 Description: Module size in bytes.
44 What: /sys/module/*/initstate
49 the module.
51 What: /sys/module/*/taint
55 Description: Module taint flags:
57 P proprietary module
[all …]
|
| D | sysfs-class-net-grcan | 11 or set by the module parameter grcan.enable0 and can be read at
12 /sys/module/grcan/parameters/enable0.
23 or set by the module parameter grcan.enable1 and can be read at
24 /sys/module/grcan/parameters/enable1.
34 set by the module parameter grcan.select and can be read at
35 /sys/module/grcan/parameters/select.
|
| /Documentation/devicetree/bindings/bus/ |
| D | ti-sysc.yaml | 7 title: Texas Instruments interconnect target module
13 Texas Instruments SoCs can have a generic interconnect target module
15 using Arteris NoC, and L4 interconnect using Sonics s3220. This module
16 is mostly used for interaction between module and Power, Reset and Clock
20 Each interconnect target module can have one or more devices connected to
22 module clocks, idle modes and interconnect level resets.
24 The interconnect target module control registers are sprinkled into the
26 the interconnect target module. Typically the register names are REVISION,
31 pattern: "^target-module(@[0-9a-f]+)?$"
58 Interconnect target module control registers consisting of
[all …]
|
| D | arm,integrator-ap-lm.yaml | 7 title: Integrator/AP Logic Module extension bus
15 determine if a logic module is connected at index 0, 1, 2 or 3. The logic
16 module connector is described in this binding. The logic modules per se
17 then have their own specific per-module bindings and they will be described
18 as subnodes under this logic module extension bus.
36 description: Nodes on the Logic Module bus represent logic modules
37 and are named with bus. The first module is at 0xc0000000, the second
39 0xffffffff. All information about the memory used by the module is
61 /* The Logic Modules sees the Core Module 0 RAM @80000000 */
|
| /Documentation/driver-api/dmaengine/ |
| D | dmatest.rst | 7 This small document introduces how to test DMA drivers using dmatest module.
9 The dmatest module tests DMA memcpy, memset, XOR and RAID6 P+Q operations using
15 The dmatest module can be configured to test a specific channel. It can also
28 Part 1 - How to build the test module
36 be built as module or inside kernel. Let's consider those cases.
38 Part 2 - When dmatest is built as a module
48 % echo 2000 > /sys/module/dmatest/parameters/timeout
49 % echo 1 > /sys/module/dmatest/parameters/iterations
50 % echo dma0chan0 > /sys/module/dmatest/parameters/channel
51 % echo 1 > /sys/module/dmatest/parameters/run
[all …]
|
| /Documentation/admin-guide/LSM/ |
| D | index.rst | 2 Linux Security Module Usage
5 The Linux Security Module (LSM) framework provides a mechanism for
7 "module" is a bit of a misnomer since these extensions are not actually
21 followed by any number of "minor" modules and at most one "major" module.
27 will always include the capability module. The list reflects the
28 order in which checks are made. The capability module will always
30 the one "major" module (e.g. SELinux) if there is one configured.
34 A security module may maintain a module specific subdirectory there,
35 named after the module. ``/proc/.../attr/smack`` is provided by the Smack
36 security module and contains all its special files. The files directly
|
| /Documentation/kbuild/ |
| D | modules.rst | 5 This document describes how to build an out-of-tree kernel module.
15 === 3. Creating a Kbuild File for an External Module
25 === 5. Module Installation
28 === 6. Module Versioning
31 --- 6.3 Symbols From Another External Module
49 external module should supply a makefile that hides most of the
50 complexity, so one only has to type "make" to build the module. This is
69 NOTE: "modules_prepare" will not build Module.symvers even if
71 executed to make module versioning work.
76 The command to build an external module is::
[all …]
|
| /Documentation/networking/ |
| D | lapb-module.rst | 4 The Linux LAPB Module Interface
13 The LAPB module will be a separately compiled module for use by any parts of
15 defines the interfaces to, and the services provided by this module. The
16 term module in this context does not imply that the LAPB module is a
17 separately loadable module, although it may be. The term module is used in
20 The interface to the LAPB module consists of functions to the module,
21 callbacks from the module to indicate important state changes, and
22 structures for getting and setting information about the module.
34 module and is not for use.
41 of the LAPB module::
[all …]
|
| D | ipv6.rst | 8 Options for the ipv6 module are supplied as parameters at load time.
10 Module options may be given as command line arguments to the insmod
15 The available ipv6 module parameters are listed below. If a parameter
22 Specifies whether to load the IPv6 module, but disable all
23 its functionality. This might be used when another module
24 has a dependency on the IPv6 module being loaded, but no
|
| /Documentation/admin-guide/ |
| D | module-signing.rst | 1 Kernel module signing facility
7 .. - Configuring module signing.
21 The kernel module signing facility cryptographically signs modules during
22 installation and then checks the signature upon loading the module. This
24 or modules signed with an invalid key. Module signing increases security by
25 making it harder to load a malicious module into the kernel. The module
38 Configuring module signing
41 The module signing facility is enabled by going to the
42 :menuselection:`Enable Loadable Module Support` section of
45 CONFIG_MODULE_SIG "Module signature verification"
[all …]
|
| D | dynamic-debug-howto.rst | 25 - module name
27 - class name (as known/declared by each module)
35 # filename:lineno [module]function flags format
55 :#> ddcmd '-p; module main func run* +p'
114 'module' string |
152 module
153 The given string is compared against the module name
154 of each callsite. The module name is the string as
158 module sunrpc
159 module nfsd
[all …]
|
| /Documentation/security/ |
| D | lsm.rst | 35 migrating the Linux capabilities code into such a module.
44 security module.
56 logic is implemented as a security module.
57 This capabilities module is discussed further in
58 `LSM Capabilities Module`_.
70 Security blobs that are used by more than one security module are
94 Unlike the other security module data, the data used here is a
104 general security module stacking. It defines
105 security_add_hooks() to which each security module passes a
109 have been registered. The SELinux security module has implemented
[all …]
|
| /Documentation/devicetree/bindings/rtc/ |
| D | trivial-rtc.yaml | 23 # AB-RTCMC-32.768kHz-B5ZE-S3: Real Time Clock/Calendar Module with I2C Interface
25 # AB-RTCMC-32.768kHz-EOZ9: Real Time Clock/Calendar Module with I2C Interface
35 # I2C-BUS INTERFACE REAL TIME CLOCK MODULE
37 # I2C-BUS INTERFACE REAL TIME CLOCK MODULE
40 # I2C-BUS INTERFACE REAL TIME CLOCK MODULE with Battery Backed RAM
42 # I2C-BUS INTERFACE REAL TIME CLOCK MODULE
48 # Real Time Clock Module with I2C-Bus
52 # Real-time Clock Module
|
| /Documentation/core-api/ |
| D | symbol-namespaces.rst | 29 its configuration, reject loading the module or warn about a missing import.
54 and kernel/module/main.c make use the namespace at build time or module load
92 load the module. The module code is required to use the macro MODULE_IMPORT_NS
93 for the namespaces it uses symbols from. E.g. a module using the
99 This will create a ``modinfo`` tag in the module for each imported namespace.
100 This has the side effect, that the imported namespaces of a module can be
109 It is advisable to add the MODULE_IMPORT_NS() statement close to other module
116 At module loading time (e.g. ``insmod``), the kernel will check each symbol
117 referenced from the module for its availability and whether the namespace it
118 might be exported to has been imported by the module. The default behaviour of
[all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | renesas,rzg2l-cpg.yaml | 7 title: Renesas RZ/{G2L,V2L,V2M} Clock Pulse Generator / Module Standby Mode
13 On Renesas RZ/{G2L,V2L}-alike SoC's, the CPG (Clock Pulse Generator) and Module
19 - The Module Standby Mode block provides two functions:
20 1. Module Standby, providing a Clock Domain to control the clock supply
49 - For module clocks, the two clock specifier cells must be "CPG_MOD" and
50 a module number, as defined in <dt-bindings/clock/r9a0*-cpg.h>.
55 SoC devices that are part of the CPG/Module Standby Mode Clock Domain and
56 can be power-managed through Module Standby should refer to the CPG device
63 The single reset specifier cell must be the module number, as defined in
|
| /Documentation/devicetree/bindings/crypto/ |
| D | omap-des.txt | 1 OMAP SoC DES crypto Module
6 - ti,hwmods: Name of the hwmod associated with the DES module
7 - reg : Offset and length of the register set for the module
8 - interrupts : the interrupt-specifier for the DES module
9 - clocks : A phandle to the functional clock node of the DES module
|
| /Documentation/driver-api/firmware/ |
| D | fw_search_path.rst | 8 * fw_path_para - module parameter - default is empty so this is ignored
14 The module parameter ''path'' can be passed to the firmware_class module
23 * /sys/module/firmware_class/parameters/path
29 echo -n /path/to/script > /sys/module/firmware_class/parameters/path
|
| /Documentation/devicetree/bindings/arm/ti/ |
| D | k3.yaml | 51 - toradex,verdin-am62-nonwifi-dahlia # Verdin AM62 Module on Dahlia
52 - toradex,verdin-am62-nonwifi-dev # Verdin AM62 Module on Verdin Development Board
53 - toradex,verdin-am62-nonwifi-yavia # Verdin AM62 Module on Yavia
54 - const: toradex,verdin-am62-nonwifi # Verdin AM62 Module without Wi-Fi / BT
55 - const: toradex,verdin-am62 # Verdin AM62 Module
61 - toradex,verdin-am62-wifi-dahlia # Verdin AM62 Wi-Fi / BT Module on Dahlia
63 - toradex,verdin-am62-wifi-yavia # Verdin AM62 Wi-Fi / BT Module on Yavia
64 - const: toradex,verdin-am62-wifi # Verdin AM62 Wi-Fi / BT Module
65 - const: toradex,verdin-am62 # Verdin AM62 Module
|
| /Documentation/sound/cards/ |
| D | joystick.rst | 18 independent module (ns558). Meanwhile, the ALSA PCI drivers have the
25 loading the module.
31 For PCI cards, the joystick is enabled when the appropriate module
35 changed, however, to the static module options because of the system
41 Driver Module Option Available Values
67 additional modules. Load the corresponding module to add the gameport
71 Driver Additional Module
82 support, so you don't have to load ns558 module. Just load "joydev"
83 and the appropriate adapter module (e.g. "analog").
90 Instead, you need to load "ns558" module in addition to "joydev" and
[all …]
|
| /Documentation/devicetree/bindings/arm/omap/ |
| D | ctrl.txt | 1 OMAP Control Module bindings
3 Control Module contains miscellaneous features under it based on SoC type.
5 described in [1]. Typically some clock nodes are also under control module.
7 control module driver itself.
30 - reg: Contains Control Module register address range
34 - clocks: clocks for this module
35 - clockdomains: clockdomains for this module
|
12345678910>>...48