Home
last modified time | relevance | path

Searched +full:non +full:- +full:specified (Results 1 – 25 of 388) sorted by relevance

12345678910>>...16

/Documentation/ABI/testing/
Dsysfs-bus-wmi5 This file allows the driver for a device to be specified which
7 When specified, only a driver with a name matching the value
10 The override is specified by writing a string to the
11 driver_override file (echo wmi-event-dummy > driver_override).
17 load the specified driver. If no driver with a matching name is
20 This also allows devices to opt-out of driver binding using a
22 specified in the override, there is no support for parsing delimiters.
31 Format: wmi:XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX.
47 the ACPI method names used by non-event WMI devices. It contains
62 present on a given WMI device. It contains a non-negative
Ddebugfs-cxl4 Contact: linux-cxl@vger.kernel.org
8 the device for the specified address. The DPA must be 64-byte
9 aligned and the length of the injected poison is 64-bytes. If
18 device returns 'Inject Poison Limit Reached' an -EBUSY error
26 Contact: linux-cxl@vger.kernel.org
30 the device for the specified address. Clearing poison removes
34 device cannot clear poison from the address, -ENXIO is returned.
41 Contact: linux-cxl@vger.kernel.org
51 0x2000 CXL.cache Protocol Uncorrectable non-fatal
54 0x10000 CXL.mem Protocol Uncorrectable non-fatal
[all …]
/Documentation/leds/
Dledtrig-transient.rst56 non-transient state. When driver gets suspended, irrespective of the transient
71 - duration allows setting timer value in msecs. The initial value is 0.
72 - activate allows activating and deactivating the timer specified by
75 - state allows user to specify a transient state to be held for the specified
79 - one shot timer activate mechanism.
84 activate state indicates a timer with a value of specified
90 - one shot timer value. When activate is set, duration value
96 - transient state to be held. It has two values 0 or 1. 0 maps
97 to LED_OFF and 1 maps to LED_FULL. The specified state is
99 state gets changed to the non-transient state which is the
[all …]
/Documentation/devicetree/bindings/arm/
Dsecure.txt15 can be supported by prefixing the property name with "secure-". So for
16 instance "secure-foo" would override "foo". For property names with
18 "vendor,secure-foo". If there is no "secure-" property then the Secure
19 world value is the same as specified for the Normal world by the
20 non-prefixed property. However, only the properties listed below may
21 validly have "secure-" versions; this list will be enlarged on a
22 case-by-case basis.
25 been annotated to indicate the presence of Secure-only devices can
26 still be processed unmodified by existing Non-secure software (and in
32 secure- bindings only need to be used where both the Secure and Normal
[all …]
/Documentation/devicetree/bindings/mmc/
Dmmc-controller.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/mmc/mmc-controller.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Ulf Hansson <ulf.hansson@linaro.org>
25 "#address-cells":
30 "#size-cells":
37 broken-cd:
42 cd-gpios:
47 non-removable:
[all …]
/Documentation/firmware-guide/acpi/apei/
Deinj.rst1 .. SPDX-License-Identifier: GPL-2.0
15 which shows that the BIOS is exposing an EINJ table - it is the
43 - available_error_type
51 0x00000002 Processor Uncorrectable non-fatal
54 0x00000010 Memory Uncorrectable non-fatal
57 0x00000080 PCI Express Uncorrectable non-fatal
60 0x00000400 Platform Uncorrectable non-fatal
67 - error_type
72 - error_inject
75 sure you have specified all necessary error parameters, i.e. this
[all …]
/Documentation/devicetree/bindings/hwmon/
Dntc-thermistor.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
2 ---
3 $id: http://devicetree.org/schemas/hwmon/ntc-thermistor.yaml#
4 $schema: http://devicetree.org/meta-schemas/core.yaml#
9 - Linus Walleij <linus.walleij@linaro.org>
13 vary in resistance in an often non-linear way in relation to temperature.
16 temperature is non-linear, software drivers most often need to use a look
20 pull-up resistor or/and a pull-down resistor and a fixed voltage like this:
22 + e.g. 5V = pull-up voltage (puv)
24 +-+
[all …]
/Documentation/devicetree/bindings/sound/
Dsound-card-common.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/sound/sound-card-common.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Mark Brown <broonie@kernel.org>
13 audio-routing:
14 $ref: /schemas/types.yaml#/definitions/non-unique-string-array
20 ignore-suspend-widgets:
21 $ref: /schemas/types.yaml#/definitions/non-unique-string-array
29 description: User specified audio sound card name
[all …]
Dtdm-slot.txt6 dai-tdm-slot-num : Number of slots in use.
7 dai-tdm-slot-width : Width in bits for each slot.
8 dai-tdm-slot-tx-mask : Transmit direction slot mask, optional
9 dai-tdm-slot-rx-mask : Receive direction slot mask, optional
12 dai-tdm-slot-num = <2>;
13 dai-tdm-slot-width = <8>;
14 dai-tdm-slot-tx-mask = <0 1>;
15 dai-tdm-slot-rx-mask = <1 0>;
17 And for each specified driver, there could be one .of_xlate_tdm_slot_mask()
27 number presents bit-0 (LSB), second presents bit-1, etc. Any non zero
[all …]
Daudio-graph.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/sound/audio-graph.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
13 - $ref: /schemas/sound/dai-params.yaml#
17 $ref: /schemas/types.yaml#/definitions/phandle-array
28 $ref: /schemas/types.yaml#/definitions/non-unique-string-array
31 User specified audio sound widgets.
35 $ref: /schemas/types.yaml#/definitions/non-unique-string-array
[all …]
Datmel,sama5d2-classd.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/sound/atmel,sama5d2-classd.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Nicolas Ferre <nicolas.ferre@microchip.com>
12 - Alexandre Belloni <alexandre.belloni@bootlin.com>
13 - Claudiu Beznea <claudiu.beznea@microchip.com>
22 - items:
23 - const: atmel,sama5d2-classd
24 - items:
[all …]
/Documentation/driver-api/
Dswitchtec.rst23 through the Memory-mapped Remote Procedure Call (MRPC) interface.
24 Commands are submitted to the interface with a 4-byte command
26 respond with a 4-byte return code and up to 1KB of command-specific
48 the 4-byte Command Return Value plus up to 1024 bytes of output
49 data. (The length will be specified by the size parameter of the read
50 call -- reading less than 4 bytes will produce an error.)
57 * SWITCHTEC_IOCTL_FLASH_INFO - Retrieve firmware length and number
60 * SWITCHTEC_IOCTL_FLASH_PART_INFO - Retrieve address and lengeth for
61 any specified partition in flash.
63 * SWITCHTEC_IOCTL_EVENT_SUMMARY - Read a structure of bitmaps
[all …]
/Documentation/admin-guide/mm/
Dpagemap.rst12 physical frame each virtual page is mapped to. It contains one 64-bit
16 * Bits 0-54 page frame number (PFN) if present
17 * Bits 0-4 swap type if swapped
18 * Bits 5-54 swap offset if swapped
19 * Bit 55 pte is soft-dirty (see
20 Documentation/admin-guide/mm/soft-dirty.rst)
22 * Bit 57 pte is uffd-wp write-protected (since 5.13) (see
23 Documentation/admin-guide/mm/userfaultfd.rst)
25 * Bits 59-60 zero
26 * Bit 61 page is file-page or shared-anon (since 3.5)
[all …]
Dhugetlbpage.rst13 256M and ppc64 supports 4K and 16M. A TLB is a cache of virtual-to-physical
93 Once a number of huge pages have been pre-allocated to the kernel huge page
106 be specified in bytes with optional scale suffix [kKmMgG]. The default huge
113 parameter to preallocate a number of huge pages of the specified
114 size. Hence, hugepagesz and hugepages are typically specified in
119 hugepagesz can only be specified once on the command line for a
128 specified, it can not be overwritten by a hugepagesz,hugepages
151 only be specified once on the command line. default_hugepagesz can
154 sized huge pages to preallocate can also be implicitly specified as
169 indicates the current number of pre-allocated huge pages of the default size.
[all …]
/Documentation/devicetree/bindings/pmem/
Dpmem-region.txt1 Device-tree bindings for persistent memory regions
2 -----------------------------------------------------
16 -----------------------------
19 - compatible = "pmem-region"
21 - reg = <base, size>;
28 each address range will be treated as though it was specified
33 - Any relevant NUMA associativity properties for the target platform.
35 - volatile; This property indicates that this region is actually
36 backed by non-persistent memory. This lets the OS know that it
41 is backed by non-volatile memory.
[all …]
/Documentation/userspace-api/media/dvb/
Dfrontend_f_open.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 fe-open - Open a frontend device
18 .. code-block:: c
53 The device can be opened in read-only mode, which only allows monitoring
57 In a system with multiple front-ends, it is usually the case that
59 long as a front-end device is opened in read/write mode, other open()
61 non-blocking or blocking mode was specified. A front-end device opened
62 in blocking mode can later be put into non-blocking mode (and vice
66 the specified mode. This implies that the corresponding hardware is
67 powered up, and that other front-ends may have been powered down to make
[all …]
/Documentation/usb/
Dmass-storage.rst9 appearing to the host as a disk or a CD-ROM drive. It supports
12 to read-only, and gadget can indicate that it is removable and/or
13 CD-ROM (the latter implies read-only access).
15 Its requirements are modest; only a bulk-in and a bulk-out endpoint
17 Support is included for full-speed, high-speed and SuperSpeed
20 Note that the driver is slightly non-portable in that it assumes
21 a single memory/DMA buffer will be usable for bulk-in and bulk-out
38 - file=filename[,filename...]
42 FSG_MAX_LUNS (8) LUNs set. If more files are specified, they will
53 simulating CD-ROM, block size of the device if the backing file is
[all …]
/Documentation/dev-tools/
Dgpio-sloppy-logic-analyzer.rst1 .. SPDX-License-Identifier: GPL-2.0
12 This document briefly describes how to run the GPIO based in-kernel sloppy
22 Another feature is to snoop on on-chip peripherals if the I/O cells of these
26 control subsystem such pin controllers are called "non-strict": a certain pin
31 non-deterministic code paths and non-maskable interrupts. It is called 'sloppy'
47 i2c-analyzer {
48 compatible = "gpio-sloppy-logic-analyzer";
49 probe-gpios = <&gpio6 21 GPIO_OPEN_DRAIN>, <&gpio6 4 GPIO_OPEN_DRAIN>;
50 probe-names = "SCL", "SDA";
53 Note that you must provide a name for every GPIO specified. Currently a
[all …]
/Documentation/userspace-api/media/mediactl/
Dmedia-ioc-setup-link.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 MEDIA_IOC_SETUP_LINK - Modify the properties of a link
50 non-dynamic link will return an ``EBUSY`` error code.
52 If the specified link can't be found the driver returns with an ``EINVAL``
58 On success 0 is returned, on error -1 and the ``errno`` variable is set
60 :ref:`Generic Error Codes <gen-errors>` chapter.
64 non-existing link, or the link is immutable and an attempt to modify
/Documentation/scsi/
Dst.rst1 .. SPDX-License-Identifier: GPL-2.0
18 to any specific tape drive. The tape parameters can be specified with
23 flexible method and applicable to single-user workstations. However,
32 drive performs auto-detection of the tape format well (like some
33 QIC-drives). The result is that any tape can be read, writing can be
37 does not perform auto-detection well enough and there is a single
40 or not :-).
57 between formats in multi-tape operations (the explicitly overridden
72 limits). Both the auto-rewind (minor equals device number) and
73 non-rewind devices (minor is 128 + device number) are implemented.
[all …]
/Documentation/driver-api/usb/
Derror-codes.rst1 .. _usb-error-codes:
6 :Revised: 2004-Oct-21
20 Non-USB-specific:
26 ``-ENOMEM`` no memory for allocation of internal structures
29 USB-specific:
32 ``-EBUSY`` The URB is already active.
34 ``-ENODEV`` specified USB-device or bus doesn't exist
36 ``-ENOENT`` specified interface or endpoint does not exist or
39 ``-ENXIO`` host controller driver does not support queuing of
42 ``-EINVAL`` a) Invalid transfer type specified (or not supported)
[all …]
/Documentation/devicetree/bindings/nvmem/
Dnvmem-consumer.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/nvmem/nvmem-consumer.yaml#
5 $schema: http://devicetree.org/meta-schemas/base.yaml#
7 title: NVMEM (Non Volatile Memory) Consumer
10 - Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
16 $ref: /schemas/types.yaml#/definitions/phandle-array
20 nvmem-cells:
21 $ref: /schemas/types.yaml#/definitions/phandle-array
25 nvmem-names:
[all …]
/Documentation/devicetree/bindings/power/supply/
Dmaxim,ds2760.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Sebastian Reichel <sre@kernel.org>
13 The ds2760 is a w1 slave device and must hence have its sub-node in
17 - $ref: power-supply.yaml#
23 maxim,pmod-enabled:
29 maxim,cache-time-ms:
35 rated-capacity-microamp-hours:
38 If not specified, the value stored in the non-volatile chip memory is used.
[all …]
/Documentation/driver-api/rapidio/
Drio_cm.rst19 This driver (RIO_CM) provides to user-space applications shared access to
23 messaging mailboxes in case of multi-packet message (up to 4KB) and
24 up to 64 mailboxes if single-packet messages (up to 256 B) are used. In addition
30 capability to large number of user-space processes by introducing socket-like
39 Following ioctl commands are available to user-space applications:
41 - RIO_CM_MPORT_GET_LIST:
46 - RIO_CM_EP_GET_LIST_SIZE:
48 in a RapidIO network associated with the specified mport device.
49 - RIO_CM_EP_GET_LIST:
52 with the specified mport device.
[all …]
/Documentation/fb/
Dmodedb.rst9 - one routine to probe for video modes, which can be used by all frame buffer
11 - one generic video mode database with a fair amount of standard videomodes
13 - the possibility to supply your own mode database for graphics hardware that
14 needs non-standard modes, like amifb and Mac frame buffer drivers (which
18 consider that to be a video mode option. If no frame buffer device is specified
23 <xres>x<yres>[M][R][-<bpp>][@<refresh>][i][m][eDd]
24 <name>[-<bpp>][@<refresh>]
31 - NSTC: 480i output, with the CCIR System-M TV mode and NTSC color encoding
32 - NTSC-J: 480i output, with the CCIR System-M TV mode, the NTSC color
34 - PAL: 576i output, with the CCIR System-B TV mode and PAL color encoding
[all …]

12345678910>>...16