Searched +full:sub +full:- +full:groups (Results 1 – 25 of 56) sorted by relevance
123
| /Documentation/devicetree/bindings/pinctrl/ |
| D | berlin,pinctrl.txt | 1 * Pin-controller driver for the Marvell Berlin SoCs
4 controller register sets. Pin controller nodes should be a sub-node of
6 controlled are organized in groups, so no actual pin information is
9 A pin-controller node should contain subnodes representing the pin group
14 is called a 'function' in the pin-controller subsystem.
17 - compatible: should be one of:
18 "marvell,berlin2-soc-pinctrl",
19 "marvell,berlin2-system-pinctrl",
20 "marvell,berlin2cd-soc-pinctrl",
21 "marvell,berlin2cd-system-pinctrl",
[all …]
|
| D | abilis,tb10x-iomux.txt | 5 -------------------
7 - compatible: should be "abilis,tb10x-iomux";
8 - reg: should contain the physical address and size of the pin controller's
13 --------------------
15 Functions are defined (and referenced) by sub-nodes of the pin controller.
16 Every sub-node defines exactly one function (implying a set of pins).
19 controller sub-nodes.
22 - abilis,function: should be set to the name of the function's pin group.
24 The following pin groups are available:
25 - GPIO ports: gpioa, gpiob, gpioc, gpiod, gpioe, gpiof, gpiog,
[all …]
|
| D | brcm,ns2-pinmux.txt | 8 - compatible:
9 Must be "brcm,ns2-pinmux"
11 - reg:
15 Properties in sub nodes:
17 - function:
20 - groups:
21 The list of groups to select with a given function
23 - pins:
26 The generic properties bias-disable, bias-pull-down, bias-pull-up,
27 drive-strength, slew-rate, input-enable, input-disable are supported
[all …]
|
| D | pinmux-node.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/pinctrl/pinmux-node.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linus.walleij@linaro.org>
30 groups = "u0rxtx", "u0rtscts";
36 groups = "spi0pins";
50 For cases like this, the pin controller driver may use pinctrl-pin-array helper
55 #pinctrl-cells = <2>;
58 pinctrl-pin-array = <
[all …]
|
| D | canaan,k210-fpioa.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pinctrl/canaan,k210-fpioa.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Damien Le Moal <dlemoal@kernel.org>
16 a per-pin basis.
20 const: canaan,k210-fpioa
29 - description: Controller reference clock source
30 - description: APB interface clock source
32 clock-names:
[all …]
|
| D | cirrus,lochnagar.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - patches@opensource.cirrus.com
15 Logic devices on mini-cards, as well as allowing connection of various
26 [2] Pinctrl: ../pinctrl/pinctrl-bindings.txt
29 [3] include/dt-bindings/pinctrl/lochnagar.h
37 - cirrus,lochnagar-pinctrl
39 gpio-controller: true
41 '#gpio-cells':
[all …]
|
| /Documentation/admin-guide/perf/ |
| D | alibaba_pmu.rst | 2 Alibaba's T-Head SoC Uncore Performance Monitoring Unit (PMU)
5 The Yitian 710, custom-built by Alibaba Group's chip development business,
6 T-Head, implements uncore PMU for performance and functional debugging to
9 DDR Sub-System Driveway (DRW) PMU Driver
14 channel is split into two independent sub-channels. The DDR Sub-System Driveway
15 implements separate PMUs for each sub-channel to monitor various performance
20 sub-channels of the same channel in die 0. And the PMU device of die 1 is
23 Each sub-channel has 36 PMU counters in total, which is classified into
24 four groups:
26 - Group 0: PMU Cycle Counter. This group has one pair of counters
[all …]
|
| /Documentation/usb/ |
| D | gadget_configfs.rst | 50 http://www.spinics.net/lists/linux-usb/msg76388.html)
55 $ mount none $CONFIGFS_HOME -t configfs
60 -----------------------
104 ------------------------------
134 -------------------------
150 Each function provides its specific set of attributes, with either read-only
151 or read-write access. Where applicable they need to be written to as
153 Please refer to Documentation/ABI/testing/configfs-usb-gadget for more information.
156 ------------------------------------------------------
164 $ ln -s functions/<name>.<instance name> configs/<name>.<number>
[all …]
|
| /Documentation/ABI/testing/ |
| D | configfs-iio | 4 Contact: linux-iio@vger.kernel.org
7 directory. It contains sub-groups corresponding to IIO
|
| D | configfs-acpi | 4 Contact: linux-acpi@vger.kernel.org
7 contains sub-groups corresponding to ACPI configurable options.
18 - a binary attribute that the user can use to
27 The rest of the attributes are read-only and are valid only
31 - ASCII table signature
34 - length of table in bytes, including the header
37 - ACPI Specification minor version number
40 - ASCII OEM identification
43 - ASCII OEM table identification
46 - OEM revision number
[all …]
|
| /Documentation/netlink/specs/ |
| D | nlctrl.yaml | 1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
4 protocol: genetlink-legacy
5 uapi-header: linux/genetlink.h
8 genetlink meta-family that exposes information about all genetlink
12 -
13 name: op-flags
15 enum-name:
17 - admin-perm
18 - cmd-cap-do
19 - cmd-cap-dump
[all …]
|
| D | ovs_datapath.yaml | 1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
5 protocol: genetlink-legacy
6 uapi-header: linux/openvswitch.h
12 -
13 name: ovs-header
16 -
17 name: dp-ifindex
19 -
20 name: user-features
22 name-prefix: ovs-dp-f-
[all …]
|
| D | ovs_vport.yaml | 1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
5 protocol: genetlink-legacy
6 uapi-header: linux/openvswitch.h
12 -
13 name: ovs-header
16 -
17 name: dp-ifindex
19 -
20 name: vport-type
22 enum-name: ovs-vport-type
[all …]
|
| /Documentation/netlink/ |
| D | netlink-raw.yaml | 1 # 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)?$
21 required: [ name, doc, attribute-sets, operations ]
31 enum: [ netlink-raw ] # Trim
32 # Start netlink-raw
34 description: Protocol number to use for netlink-raw
[all …]
|
| D | genetlink.yaml | 1 # 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)$
26 required: [ name, doc, attribute-sets, operations ]
[all …]
|
| D | genetlink-c.yaml | 1 # 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)$
26 required: [ name, doc, attribute-sets, operations ]
[all …]
|
| D | genetlink-legacy.yaml | 1 # 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)$
26 required: [ name, doc, attribute-sets, operations ]
[all …]
|
| /Documentation/userspace-api/netlink/ |
| D | netlink-raw.rst | 1 .. SPDX-License-Identifier: BSD-3-Clause
8 families such as ``NETLINK_ROUTE`` which use the ``netlink-raw`` protocol
14 The netlink-raw schema extends the :doc:`genetlink-legacy <genetlink-legacy>`
17 information. The raw netlink families also make use of type-specific
18 sub-messages.
21 -------
29 .. code-block:: yaml
31 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
33 name: rt-addr
34 protocol: netlink-raw
[all …]
|
| D | specs.rst | 1 .. SPDX-License-Identifier: BSD-3-Clause
17 - the C uAPI header
18 …- documentation of the protocol as a ReST file - see :ref:`Documentation/networking/netlink_spec/i…
19 - policy tables for input attribute validation
20 - operation tables
25 See :doc:`intro-specs` for a practical starting guide.
28 ``((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)``
40 - ``genetlink`` - most streamlined, should be used by all new families
41 - ``genetlink-c`` - superset of ``genetlink`` with extra attributes allowing
45 - ``genetlink-legacy`` - Generic Netlink catch all schema supporting quirks of
[all …]
|
| /Documentation/devicetree/bindings/pci/ |
| D | snps,dw-pcie-common.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pci/snps,dw-pcie-common.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jingoo Han <jingoohan1@gmail.com>
11 - Gustavo Pimentel <gustavo.pimentel@synopsys.com>
23 Interface - DBI. In accordance with the reference manual the register
24 configuration space belongs to the Configuration-Dependent Module (CDM)
25 and is split up into several sub-parts Standard PCIe configuration
26 space, Port Logic Registers (PL), Shadow Config-space Registers,
[all …]
|
| /Documentation/arch/powerpc/ |
| D | associativity.rst | 9 are represented as being members of a sub-grouping domain. This performance
11 From the platform view, these groups are also referred to as domains.
17 Hypervisor indicates the type/form of associativity used via "ibm,architecture-vec-5 property".
18 Bit 0 of byte 5 in the "ibm,architecture-vec-5" property indicates usage of Form 0 or Form 1.
20 bit 2 of byte 5 in the "ibm,architecture-vec-5" property is used.
23 ------
27 ------
28 With Form 1 a combination of ibm,associativity-reference-points, and ibm,associativity
29 device tree properties are used to determine the NUMA distance between resource groups/domains.
34 The “ibm,associativity-reference-points” property contains a list of one or more numbers
[all …]
|
| /Documentation/userspace-api/media/dvb/ |
| D | frontend.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
9 The Digital TV frontend API was designed to support three groups of delivery
13 - Terrestrial systems: DVB-T, DVB-T2, ATSC, ATSC M/H, ISDB-T, DVB-H,
16 - Cable systems: DVB-C Annex A/C, ClearQAM (DVB-C Annex B)
18 - Satellite systems: DVB-S, DVB-S2, DVB Turbo, ISDB-S, DSS
20 The Digital TV frontend controls several sub-devices including:
22 - Tuner
24 - Digital TV demodulator
26 - Low noise amplifier (LNA)
28 - Satellite Equipment Control (SEC) [#f1]_.
[all …]
|
| /Documentation/devicetree/bindings/opp/ |
| D | opp-v2-base.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/opp/opp-v2-base.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Viresh Kumar <viresh.kumar@linaro.org>
13 Devices work at voltage-current-frequency combinations and some implementations
25 pattern: '^opp-table(-[a-z0-9]+)?$'
27 opp-shared:
36 '^opp(-?[0-9]+)*$':
39 One or more OPP nodes describing voltage-current-frequency combinations.
[all …]
|
| /Documentation/admin-guide/gpio/ |
| D | gpio-virtuser.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only
8 consumer devices can be instantiated from device-tree or over configfs.
10 A virtual consumer uses the driver-facing GPIO APIs and allows to cover it with
11 automated tests driven by user-space. The GPIOs are requested using
15 -----------------------
17 The gpio-consumer module registers a configfs subsystem called
18 ``'gpio-virtuser'``. For details of the configfs filesystem, please refer to
21 The user can create a hierarchy of configfs groups and items as well as modify
25 **Group:** ``/config/gpio-virtuser``
27 This is the top directory of the gpio-consumer configfs tree.
[all …]
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | cgroups.rst | 2 Control Groups
6 Documentation/admin-guide/cgroup-v1/cpusets.rst
12 Portions Copyright (c) 2004-2006 Silicon Graphics, Inc.
20 1. Control Groups
38 1. Control Groups
42 ----------------------
44 Control Groups provide a mechanism for aggregating/partitioning sets of
45 tasks, and all their future children, into hierarchical groups with
54 facilities provided by cgroups to treat groups of tasks in
56 schedules a resource or applies per-cgroup limits, but it may be
[all …]
|
123