| /Documentation/arch/riscv/ |
| D | hwprobe.rst | 27 Usermode can supply NULL for ``cpus`` and 0 for ``cpusetsize`` as a shortcut for
35 means to be the exact same as the value. For boolean-like keys, matching
37 exactly the same as the pair's value. Additionally, when ``cpus`` is an empty
49 as defined by the RISC-V privileged architecture specification.
51 * :c:macro:`RISCV_HWPROBE_KEY_MARCHID`: Contains the value of ``marchid``, as
54 * :c:macro:`RISCV_HWPROBE_KEY_MIMPLID`: Contains the value of ``mimplid``, as
62 rv64ima, as defined by version 2.2 of the user ISA and version 1.10 of the
68 kernel-controlled mechanism such as the vDSO).
74 * :c:macro:`RISCV_HWPROBE_IMA_FD`: The F and D extensions are supported, as
78 * :c:macro:`RISCV_HWPROBE_IMA_C`: The C extension is supported, as defined
[all …]
|
| /Documentation/devicetree/bindings/riscv/ |
| D | extensions.yaml | 56 The base ISA implemented by this hart, as described by the 20191213
71 The base integer instruction set, as ratified in the 20191213
80 The standard M extension for integer multiplication and division, as
86 The standard A extension for atomic instructions, as ratified in the
91 The standard F extension for single-precision floating point, as
97 The standard D extension for double-precision floating-point, as
103 The standard Q extension for quad-precision floating-point, as
109 The standard C extension for compressed instructions, as ratified in
114 The standard V extension for vector operations, as ratified
120 The standard H extension for hypervisors as ratified in the 20191213
[all …]
|
| /Documentation/pcmcia/ |
| D | driver-changes.rst | 7 * pcmcia_loop_config() and autoconfiguration (as of 2.6.36)
20 * pcmcia_request_configuration -> pcmcia_enable_device (as of 2.6.36)
22 as it mirrors pcmcia_disable_device(). Configuration settings are now
26 * pcmcia_request_window changes (as of 2.6.36)
33 * pcmcia_request_io changes (as of 2.6.36)
40 * No dev_info_t, no cs_types.h (as of 2.6.36)
42 in PCMCIA device drivers. Also, do not include pcmcia/cs_types.h, as
45 * No dev_node_t (as of 2.6.35)
48 * New IRQ request rules (as of 2.6.35)
57 * no cs_error / CS_CHECK / CONFIG_PCMCIA_DEBUG (as of 2.6.33)
[all …]
|
| /Documentation/input/ |
| D | gamepad.rst | 16 As "gamepad" we define devices which roughly look like this::
45 differently labeled on most devices so we define them as NORTH,
51 Furthermore, many gamepads have a fancy branded button that is used as
70 an alias for BTN_SOUTH/BTN_A. It can be used to identify a gamepad as such.
74 Legacy drivers often don't comply to these rules. As we cannot change them
85 and one analog stick. It reports them as if it were a gamepad with only one
111 If only 2 action-buttons are present, they are reported as BTN_SOUTH and
117 If only 3 action-buttons are present, they are reported as (from left
119 If the buttons are aligned perfectly vertically, they are reported as
125 different formations. If diamond-shaped, they are reported as BTN_NORTH,
[all …]
|
| /Documentation/admin-guide/ |
| D | ufs.rst | 20 default value, supported as read-only
24 supported as read-write
28 supported as read-write
35 supported as read-write
39 supported as read-write
43 supported as read-only
47 supported as read-only
51 supported as read-only
55 supported as read-only
|
| /Documentation/devicetree/bindings/sound/ |
| D | ti,tlv320adcx140.yaml | 68 array is defined as <PDMIN1 PDMIN2 PDMIN3 PDMIN4>.
90 The array is defined as <GPI1 GPI2 GPI3 GPI4>.
93 1 - GPIX is configured as a general-purpose input (GPI)
94 2 - GPIX is configured as a master clock input (MCLK)
95 3 - GPIX is configured as an ASI input for daisy-chain (SDIN)
96 4 - GPIX is configured as a PDM data input for channel 1 and channel
98 5 - GPIX is configured as a PDM data input for channel 3 and channel
100 6 - GPIX is configured as a PDM data input for channel 5 and channel
102 7 - GPIX is configured as a PDM data input for channel 7 and channel
117 type. The array is defined as <GPIO1_CFG GPIO1_DRV>
[all …]
|
| D | realtek,rt5659.yaml | 64 - 1 # using IN2N pin as dmic1 data pin
65 - 2 # using GPIO5 pin as dmic1 data pin
66 - 3 # using GPIO9 pin as dmic1 data pin
67 - 4 # using GPIO11 pin as dmic1 data pin
68 description: Specify which pin to be used as DMIC1 data pin.
75 - 1 # using IN2P pin as dmic2 data pin
76 - 2 # using GPIO6 pin as dmic2 data pin
77 - 3 # using GPIO10 pin as dmic2 data pin
78 - 4 # using GPIO12 pin as dmic2 data pin
79 description: Specify which pin to be used as DMIC2 data pin.
[all …]
|
| /Documentation/devicetree/bindings/input/ |
| D | nvidia,tegra20-kbc.txt | 3 can be configured as row or column. The maximum column pin can be 8
10 - nvidia,kbc-row-pins: The KBC pins which are configured as row. This is an
11 array of pin numbers which is used as rows.
12 - nvidia,kbc-col-pins: The KBC pins which are configured as column. This is an
13 array of pin numbers which is used as column.
14 - linux,keymap: The keymap for keys as described in the binding document
26 - linux,fn-keymap: a second keymap, same specification as the
32 - wakeup-source: configure keyboard as a wakeup source for suspend/resume
46 nvidia,kbc-row-pins = <0 1 2>; /* pin 0, 1, 2 as rows */
47 nvidia,kbc-col-pins = <11 12 13>; /* pin 11, 12, 13 as columns */
|
| /Documentation/images/ |
| D | COPYING-logo | 4 and is freely usable as long as you acknowledge Larry as the original
16 as long as you acknowledge Larry, Garrett and IFo as above.
|
| /Documentation/networking/device_drivers/can/ |
| D | can327.rst | 21 Let's use ELM327s as CAN adapters.
29 into full fledged (as far as possible) CAN interfaces.
32 the driver has to switch between its modes as quickly as possible in
35 As such, can327 is a best effort driver. However, this is more than
36 enough to implement simple request-response protocols (such as OBD II),
37 and to monitor broadcast messages on a bus (such as in a vehicle).
39 Most ELM327s come as nondescript serial devices, attached via USB or
40 Bluetooth. The driver cannot recognize them by itself, and as such it
65 be attached on a command prompt as follows::
92 After this, you can set out as usual with candump, cansniffer, etc.
[all …]
|
| /Documentation/misc-devices/ |
| D | pci-endpoint-test.rst | 7 This driver should be used as a host side driver if the root complex is
32 should be passed as argument.
37 to be tested should be passed as argument.
40 to be tested should be passed as argument.
43 should be passed as argument (0: Legacy, 1:MSI, 2:MSI-X).
48 as argument.
51 as argument.
54 as argument.
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | snps,dw-apb-ictl.txt | 3 Synopsys DesignWare provides interrupt controller IP for APB known as
4 dw_apb_ictl. The IP is used as secondary interrupt controller in some SoCs with
5 APB bus, e.g. Marvell Armada 1500. It can also be used as primary interrupt
12 - interrupt-controller: identifies the node as an interrupt controller
15 Additional required property when it's used as secondary interrupt controller:
27 /* dw_apb_ictl is used as secondary interrupt controller */
37 /* dw_apb_ictl is used as primary interrupt controller */
|
| /Documentation/netlabel/ |
| D | introduction.rst | 24 engine will handle those tasks as well. Other kernel subsystems should
37 formatting of these NetLabel messages as well as the Generic NETLINK family
38 names can be found in the 'net/netlabel/' directory as comments in the
39 header files as well as in 'include/net/netlabel.h'.
51 'include/net/netlabel.h' header file as well as the 'lsm_interface.txt' file
|
| /Documentation/arch/arm64/ |
| D | cpu-hotplug.rst | 12 ``possible`` and ``present`` refer to the state of the CPU as seen by linux.
18 Physical systems need to mark a CPU that is ``possible`` but not ``present`` as
47 as such devices are emulated.
50 CPU Hotplug as all resources are described as ``present``, but CPUs may be
51 marked as disabled by firmware. Only the CPU's online/offline behaviour is
58 Virtual hotplug is implemented as a firmware policy affecting which CPUs can be
65 bit set, to indicate they can be enabled later. The boot CPU must be marked as
69 CPUs described as ``online capable`` but not ``enabled`` can be set to enabled
71 must always report the CPU as ``present``. Changes to the firmware policy can
74 CPUs described as ``enabled`` in the static table, should not have their _STA
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-dmi-entries | 12 cannot ensure that the data as exported to userland is
15 DMI is structured as a large table of entries, where
17 length of the entry, as well as a firmware-provided
33 doesn't matter), they will be represented in sysfs as
45 assigned entry handles as the kernel itself makes no
46 guarantees that handles as exported are unique, and
51 exported as attributes:
57 length The length of the entry, as presented in the
71 as found in the directory name. It indicates
74 given type. This value is the same as found
[all …]
|
| D | sysfs-firmware-qemu_fw_cfg | 7 (fw_cfg) device, originally intended as a way for the host to
11 useful as an out-of-band, asynchronous mechanism for providing
23 with the file directory), as there is no way to determine the
38 displayed as entries named after their unique selector key
47 as attributes:
50 name The 56-byte nul-terminated ASCII string used as the
52 size The length of the blob, as given in the fw_cfg
54 key The value of the blob's selector key as given in the
55 fw_cfg directory. This value is the same as used in
86 "basename", as illustrated below (assume current directory is
[all …]
|
| /Documentation/timers/ |
| D | timekeeping.rst | 17 on this timeline, providing facilities such as high-resolution timers.
32 It will ideally NEVER stop ticking as long as the system is running. It
35 The clock source shall have as high resolution as possible, and the frequency
36 shall be as stable and correct as possible as compared to a real-world wall
55 into a nanosecond value as an unsigned long long (unsigned 64 bit) number.
57 mathematical sense is not desirable: instead the number is taken as close as
64 to aid in providing these mult and shift values, such as
68 factors using the frequency of the clock source as the only input.
95 fire interrupts, so as to trigger events on the system timeline. On an SMP
115 implementation is not provided, the system jiffy counter will be used as
[all …]
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-max77620.txt | 3 Device has 8 GPIO pins which can be configured as GPIO as well as the
18 The pin configurations are defined as child of the pinctrl states node. Each
28 Following are optional properties defined as pinmux DT binding document
69 selected as FPS0, FPS1 or FPS2.
76 selected as FPS0, FPS1 or FPS2.
78 - maxim,suspend-fps-source: This is same as property
83 - maxim,suspend-fps-power-up-slot: This is same as property
89 FPS source is selected as FPS0, FPS1 or
91 - maxim,suspend-fps-power-down-slot: This is same as property
97 FPS source is selected as FPS0, FPS1 or
|
| /Documentation/process/ |
| D | contribution-maturity-model.rst | 11 As a part of the 2021 Linux Kernel Maintainers’ Summit, there was a
13 recruiting kernel maintainers as well as maintainer succession. Some of
16 maintainers as part of their job, so they can grow into becoming
19 take on upstream contributions such as reviewing other people’s patches,
48 kernel, either as part of their job responsibilities or on their own
54 * Software Engineers are expected to contribute to the Linux Kernel as
57 conferences as a part of their job.
65 authored by engineers from other companies) as part of their job
92 time focused on Upstream Work, which is defined as reviewing patches,
94 such as writing or maintaining tests, upstream tech debt reduction,
[all …]
|
| /Documentation/userspace-api/gpio/ |
| D | sysfs.rst | 9 encouraged to migrate as soon as possible, as this API will be removed
78 reads as either "in" or "out". This value may
79 normally be written. Writing as "out" defaults to
80 initializing the value as low. To ensure glitch free
82 configure the GPIO as an output with that initial value.
90 reads as either 0 (inactive) or 1 (active). If the GPIO
91 is configured as an output, this value may be written;
92 any nonzero value is treated as active.
94 If the pin can be configured as interrupt-generating interrupt
106 reads as either "none", "rising", "falling", or
[all …]
|
| /Documentation/userspace-api/ |
| D | dma-buf-alloc-exchange.rst | 8 As originally designed, the Linux graphics subsystem had extremely limited
52 have an alpha value as an additional channel.
65 channels R, G, and B. Alpha channel is sometimes counted as a color
66 channel as well.
81 and byte-offset values. Typically used as the byte offset between two
85 usually is done as-if the layout was linear.
97 wherever possible, as they are the standard descriptions used for interchange.
113 always as described in the format definition, which is usually little-endian.
115 As a more complex example, ``DRM_FORMAT_NV12`` describes a format in which luma
143 in order to ensure a compatible and optimal pipeline, as discussed below.
[all …]
|
| /Documentation/dev-tools/kunit/ |
| D | style.rst | 7 To make finding, writing, and using KUnit tests as simple as possible, it is
34 cannot be compiled as a module, in many cases the subsystem should correspond to
57 Avoid names as shown in examples below:
63 This name should use underscores, and not have "kunit-test" as a
64 suffix. ``qos`` is also ambiguous as a subsystem name, because several parts
90 put into separate suites, with the type of test as the last element in the suite
94 The full test suite name (including the subsystem name) should be specified as
105 The ``kasan`` subsystem has only one suite, so the suite name is the same as
116 just be called as ``kasan``. Do not redundantly add
118 unit tests are added, then that suite could be named as ``kasan_unittest`` or
[all …]
|
| /Documentation/kbuild/ |
| D | gendwarfksyms.rst | 11 as Rust, where the source code has insufficient information about
103 for source code annotation. Note that as these features are only used to
118 This string sequence is repeated as many times as needed to express all
119 the rules. The fields are as follows:
142 the format is extensible enough to allow further rules to be added as
150 symbol that references the type even if the ABI remains unchanged. As
152 `declonly` rule can be used to specify a type as declaration-only, even
155 The rule fields are expected to be as follows:
159 (as shown in **--dump-dies** output).
162 Using the `__KABI_RULE` macro, this rule can be defined as::
[all …]
|
| /Documentation/networking/ |
| D | xfrm_sync.rst | 15 the processing of the SA as accurate as possible if it has access to it.
20 with as minimal loss at failover time.
21 This way a backup stays as closely up-to-date as an active member.
49 A XFRM_MSG_NEWAE will have at least two TLVs (as is
76 message (kernel<->user) as well the cause (config, query or event).
106 This is a timer value in milliseconds which is used as the nagle
117 in order to not change existing applications such as racoon
156 XFRM_MSG_NEWAE is also issued to any listeners as described in iii).
158 ii) kernel->user direction as a response to XFRM_MSG_GETAE
165 iii) kernel->user to report as event if someone sets any values or
[all …]
|
| /Documentation/filesystems/bcachefs/ |
| D | errorcodes.rst | 6 In bcachefs, as a hard rule we do not throw or directly use standard error
7 codes (-EINVAL, -EBUSY, etc.). Instead, we define private error codes as needed
16 errors), as well as specifying which standard error code should be returned at
27 Try to give error codes names that are as reasonably descriptive of the error
28 as possible. Frequently, the error will be logged at a place far removed from
|