Home
last modified time | relevance | path

Searched +full:subset +full:- +full:of (Results 1 – 25 of 175) sorted by relevance

1234567

/Documentation/netlink/specs/
Ddevlink.yaml1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
5 protocol: genetlink-legacy
10 -
12 name: sb-pool-type
14 -
16 -
18 -
20 name: port-type
22 -
24 -
[all …]
/Documentation/arch/arm64/
Dasymmetric-32bit.rst2 Asymmetric 32-bit SoCs
7 This document describes the impact of asymmetric 32-bit SoCs on the
8 execution of 32-bit (``AArch32``) applications.
10 Date: 2021-05-17
15 Some Armv9 SoCs suffer from a big.LITTLE misfeature where only a subset
16 of the CPUs are capable of executing 32-bit user applications. On such
19 ``execve(2)`` of 32-bit ELF binaries, with the latter returning
20 ``-ENOEXEC``. If the mismatch is detected during late onlining of a
21 64-bit-only CPU, then the onlining operation fails and the new CPU is
24 Surprisingly, these SoCs have been produced with the intention of
[all …]
/Documentation/userspace-api/media/
Dglossary.rst1 .. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.1-no-invariants-or-later
9 The goal of this section is to standardize the terms used within the media
30 Unit of data transported by a bus. On parallel buses, the data unit
31 consists of one or more related samples while on serial buses the data
36 Part of the Linux Kernel that implements support for a hardware
41 transfer data in and out of a Kernel driver.
46 An API designed to control a subset of the :term:`Media Hardware`
55 optimized for the operational needs of digital signal processing.
58 **Field-programmable Gate Array**
63 See https://en.wikipedia.org/wiki/Field-programmable_gate_array.
[all …]
/Documentation/netlink/
Dgenetlink.yaml1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
3 ---
4 $id: http://kernel.org/schemas/netlink/genetlink-legacy.yaml#
5 $schema: https://json-schema.org/draft-07/schema
12 len-or-define:
14 pattern: ^[0-9A-Za-z_-]+( - 1)?$
16 len-or-limit:
17 # literal int or limit based on fixed-width type e.g. u8-min, u16-max, etc.
19 pattern: ^[su](8|16|32|64)-(min|max)$
24 description: Specification of a genetlink protocol
[all …]
Dgenetlink-c.yaml1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
3 ---
4 $id: http://kernel.org/schemas/netlink/genetlink-c.yaml#
5 $schema: https://json-schema.org/draft-07/schema
12 len-or-define:
14 pattern: ^[0-9A-Za-z_-]+( - 1)?$
16 len-or-limit:
17 # literal int or limit based on fixed-width type e.g. u8-min, u16-max, etc.
19 pattern: ^[su](8|16|32|64)-(min|max)$
24 description: Specification of a genetlink protocol
[all …]
Dgenetlink-legacy.yaml1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
3 ---
4 $id: http://kernel.org/schemas/netlink/genetlink-legacy.yaml#
5 $schema: https://json-schema.org/draft-07/schema
12 len-or-define:
14 pattern: ^[0-9A-Za-z_-]+( - 1)?$
16 len-or-limit:
17 # literal int or limit based on fixed-width type e.g. u8-min, u16-max, etc.
19 pattern: ^[su](8|16|32|64)-(min|max)$
24 description: Specification of a genetlink protocol
[all …]
Dnetlink-raw.yaml1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
3 ---
4 $id: http://kernel.org/schemas/netlink/netlink-raw.yaml#
5 $schema: https://json-schema.org/draft-07/schema
12 len-or-define:
14 pattern: ^[0-9A-Za-z_-]+( - 1)?$
19 description: Specification of a raw netlink protocol
21 required: [ name, doc, attribute-sets, operations ]
25 description: Name of the netlink family.
31 enum: [ netlink-raw ] # Trim
[all …]
/Documentation/devicetree/bindings/serial/
Darm_sbsa_uart.txt2 This UART uses a subset of the PL011 registers and consequently lives
7 - compatible: must be "arm,sbsa-uart"
8 - reg: exactly one register range
9 - interrupts: exactly one interrupt specifier
10 - current-speed: the (fixed) baud rate set by the firmware
/Documentation/filesystems/
Dext3.rst1 .. SPDX-License-Identifier: GPL-2.0
12 filesystem is a subset of ext4 filesystem so use ext4 driver for accessing
/Documentation/ABI/testing/
Dsysfs-class-gnss15 Note that also non-"NMEA" type receivers typically support a
16 subset of NMEA 0183 with vendor extensions (e.g. to allow
Dsysfs-bus-pci-devices-pvpanic2 /sys/bus/pci/drivers/pvpanic-pci/0000:00:0*.0/capability for PCI
6 Read-only attribute. Capabilities of pvpanic device which
16 /sys/bus/pci/drivers/pvpanic-pci/0000:00:0*.0/events for PCI
20 RW attribute. Set/get which features in-use. This attribute
21 is used to enable/disable feature(s) of pvpanic device.
22 Notice that this value should be a subset of capability.
Dsysfs-bus-coreboot5 The coreboot bus provides a variety of virtual devices used to
8 What: /sys/bus/coreboot/devices/cbmem-<id>
12 CBMEM is a downwards-growing memory region created by Coreboot,
16 A list of ids known to Coreboot can be found in the coreboot
20 What: /sys/bus/coreboot/devices/cbmem-<id>/address
27 What: /sys/bus/coreboot/devices/cbmem-<id>/size
31 This is the size of the CBMEM entry's data, in hexadecimal
34 What: /sys/bus/coreboot/devices/cbmem-<id>/mem
40 does not guarantee that the data will be page-aligned.
42 The mode of this file is 0600. While there shouldn't be
[all …]
/Documentation/i2c/
Dsummary.rst6 a protocol developed by Philips. It is a two-wire protocol with variable
8 an inexpensive bus for connecting many types of devices with infrequent or
14 The latest official I2C specification is the `"I²C-bus specification and user
15 manual" (UM10204) <https://www.nxp.com/docs/en/user-guide/UM10204.pdf>`_
16 published by NXP Semiconductors, version 7 as of this writing.
19 a subset of I2C protocols and signaling. Many I2C devices will work on an
25 Because the SMBus is mostly a subset of the generalized I2C bus, we can
36 .. kernel-figure:: i2c_bus.svg
46 class of I2C controllers. Each specific controller driver either depends on an
59 video-related chips.
[all …]
/Documentation/devicetree/bindings/perf/
Darm,coresight-pmu.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/perf/arm,coresight-pmu.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Robin Murphy <robin.murphy@arm.com>
14 const: arm,coresight-pmu
18 - description: Register page 0
19 - description: Register page 1, if the PMU implements the dual-page extension
24 - description: Overflow interrupt
27 description: If the PMU is associated with a particular CPU or subset of CPUs,
[all …]
Dspe-pmu.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/perf/spe-pmu.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Will Deacon <will@kernel.org>
14 performance sample data using an in-memory trace buffer.
18 const: arm,statistical-profiling-extension-v1
24 supported on a subset of the CPUs, please consult the arm,gic-v3 binding
30 - compatible
31 - interrupts
[all …]
Damlogic,g12-ddr-pmu.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/perf/amlogic,g12-ddr-pmu.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jiucheng Xu <jiucheng.xu@amlogic.com>
16 has different subset of event format attribute.
21 - amlogic,g12a-ddr-pmu
22 - amlogic,g12b-ddr-pmu
23 - amlogic,sm1-ddr-pmu
27 - description: DMC bandwidth register space.
[all …]
/Documentation/devicetree/bindings/
Dwriting-schema.rst1 .. SPDX-License-Identifier: GPL-2.0
3 Writing Devicetree Bindings in json-schema
6 Devicetree bindings are written using json-schema vocabulary. Schema files are
7 written in a JSON-compatible subset of YAML. YAML is used instead of JSON as it
11 Also see :ref:`example-schema`.
14 ---------------
16 Each schema doc is a structured json-schema which is defined by a set of
17 top-level properties. Generally, there is one binding defined per file. The
18 top-level json-schema properties used are:
21 A json-schema unique identifier string. The string must be a valid
[all …]
/Documentation/devicetree/bindings/hwmon/
Dltc2990.txt4 - compatible: Must be "lltc,ltc2990"
5 - reg: I2C slave address
6 - lltc,meas-mode:
7 An array of two integers for configuring the chip measurement mode.
14 1: V1-V2, TR2
15 2: V1-V2, V3, V4
17 4: TR1, V3-V4
19 6: V1-V2, V3-V4
23 allows a subset of the measurements to be enabled:
26 1: TR1, V1 or V1-V2 only per mode
[all …]
/Documentation/admin-guide/perf/
Darm_dsu_pmu.rst11 cores connected to the same DSU. Like most of the other uncore PMUs, DSU
14 The DSU provides a bitmap for a subset of implemented events via hardware
21 The user should refer to the TRM of the product to figure out the supported events
29 perf stat -a -e arm_dsu_0/cycles/
/Documentation/hwmon/
Dvexpress.rst12 * "Hardware Description" sections of the Technical Reference Manuals
15 - http://infocenter.arm.com/help/topic/com.arm.doc.subset.boards.express/index.html
17 * Section "4.4.14. System Configuration registers" of the V2M-P1 TRM:
19 - http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0447-/index.html
24 -----------
28 from a wide range of boards, each of them containing (apart of the main
29 chip/FPGA) a number of microcontrollers responsible for platform
31 board and its environment by a number of internal and external sensors,
33 temperature and power usage. Some of them also calculate consumed energy
39 As these devices are non-discoverable, they must be described in a Device
[all …]
/Documentation/devicetree/bindings/arm/
Darm,trace-buffer-extension.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
4 ---
5 $id: http://devicetree.org/schemas/arm/arm,trace-buffer-extension.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Anshuman Khandual <anshuman.khandual@arm.com>
26 - const: arm,trace-buffer-extension
31 TRBE is only supported on a subset of the CPUs, please consult
32 the arm,gic-v3 binding for details on describing a PPI partition.
36 - compatible
37 - interrupts
[all …]
/Documentation/dev-tools/
Dkselftest.rst5 The kernel contains a set of "self tests" under the tools/testing/selftests/
23 On some systems, hot-plug tests could hang forever waiting for cpu and
24 memory to be ready to be offlined. A special hot-plug target is created
25 to run the full range of hot-plug tests. In default mode, hot-plug tests run
26 in safe mode with a limited scope. In limited mode, cpu-hotplug test is
28 hotplug test is run on 2% of hotplug capable memory instead of 10%.
40 $ make -C tools/testing/selftests
44 $ make -C tools/testing/selftests run_tests
54 are supported. In both cases the working directory must be the root of the
55 kernel src. This is applicable to "Running a subset of selftests" section
[all …]
/Documentation/userspace-api/gpio/
Dgpio-v2-line-set-values-ioctl.rst1 .. SPDX-License-Identifier: GPL-2.0
12 GPIO_V2_LINE_SET_VALUES_IOCTL - Set the values of requested output lines.
25 The file descriptor of the GPIO character device, as returned in the
26 :c:type:`request.fd<gpio_v2_line_request>` by gpio-v2-get-line-ioctl.rst.
30 to indicate the subset of requested lines to set and ``bits`` set to
36 Set the values of requested output lines.
45 Only the values of output lines may be set.
46 Attempting to set the value of an input line is an error (**EPERM**).
53 On error -1 and the ``errno`` variable is set appropriately.
54 Common error codes are described in error-codes.rst.
Dgpio-v2-line-get-values-ioctl.rst1 .. SPDX-License-Identifier: GPL-2.0
12 GPIO_V2_LINE_GET_VALUES_IOCTL - Get the values of requested lines.
25 The file descriptor of the GPIO character device, as returned in the
26 :c:type:`request.fd<gpio_v2_line_request>` by gpio-v2-get-line-ioctl.rst.
30 to indicate the subset of requested lines to get.
35 Get the values of requested lines.
44 The values of both input and output lines may be read.
48 buffer (the actual level of the line), and depending on the hardware and
57 On error -1 and the ``errno`` variable is set appropriately.
58 Common error codes are described in error-codes.rst.
/Documentation/devicetree/bindings/mmc/
Dsdhci-omap.txt5 … maps to the appropriate thermal zone. This is used to get the temperature of the zone during tuni…
8 - compatible: Should be "ti,omap2430-sdhci" for omap2430 controllers
9 Should be "ti,omap3-sdhci" for omap3 controllers
10 Should be "ti,omap4-sdhci" for omap4 and ti81 controllers
11 Should be "ti,omap5-sdhci" for omap5 controllers
12 Should be "ti,dra7-sdhci" for DRA7 and DRA72 controllers
13 Should be "ti,k2g-sdhci" for K2G
14 Should be "ti,am335-sdhci" for am335x controllers
15 Should be "ti,am437-sdhci" for am437x controllers
16 - ti,hwmods: Must be "mmc<n>", <n> is controller instance starting 1
[all …]

1234567