Home
last modified time | relevance | path

Searched +full:sub +full:- +full:groups (Results 1 – 25 of 211) sorted by relevance

123456789

/linux-6.14.4/include/media/
Dv4l2-device.h1 /* SPDX-License-Identifier: GPL-2.0-or-later */
12 #include <media/media-device.h>
13 #include <media/v4l2-subdev.h>
14 #include <media/v4l2-dev.h>
19 * struct v4l2_device - main struct to for V4L2 device drivers
27 * @notify: notify operation called by some sub-devices.
35 * either stand-alone or embedded in a larger struct.
37 * It allows easy access to sub-devices (see v4l2-subdev.h) and provides
38 * basic V4L2 device-level support.
42 * #) @dev->driver_data points to this struct.
[all …]
/linux-6.14.4/arch/arm64/boot/dts/renesas/
Dwhite-hawk-ethernet.dtsi1 // SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 * Device Tree Source for the White Hawk RAVB/Ethernet(1000Base-T1)
4 * sub-board
17 pinctrl-0 = <&avb1_pins>;
18 pinctrl-names = "default";
19 phy-handle = <&avb1_phy>;
23 #address-cells = <1>;
24 #size-cells = <0>;
26 reset-gpios = <&gpio6 1 GPIO_ACTIVE_LOW>;
27 reset-post-delay-us = <4000>;
[all …]
Dr8a779a0-falcon-ethernet.dtsi1 // SPDX-License-Identifier: GPL-2.0
3 * Device Tree Source for the Falcon Ethernet sub-board
19 pinctrl-0 = <&avb1_pins>;
20 pinctrl-names = "default";
21 phy-handle = <&avb1_phy>;
25 #address-cells = <1>;
26 #size-cells = <0>;
28 reset-gpios = <&gpio5 15 GPIO_ACTIVE_LOW>;
29 reset-post-delay-us = <4000>;
31 avb1_phy: ethernet-phy@7 {
[all …]
Dcat875.dtsi1 // SPDX-License-Identifier: GPL-2.0
3 * Device Tree Source for the Silicon Linux sub board for CAT874 (CAT875)
9 model = "Silicon Linux sub board for CAT874 (CAT875)";
17 pinctrl-0 = <&avb_pins>;
18 pinctrl-names = "default";
19 renesas,no-ether-link;
20 phy-handle = <&phy0>;
21 phy-mode = "rgmii-id";
24 phy0: ethernet-phy@0 {
25 compatible = "ethernet-phy-id001c.c915",
[all …]
Dr8a779f0-spider-ethernet.dtsi1 // SPDX-License-Identifier: GPL-2.0
3 * Device Tree Source for the Spider Ethernet sub-board
15 label = "ethernet-sub-board";
23 groups = "tsn0_mdio_b", "tsn0_link_b";
25 power-source = <1800>;
29 groups = "tsn1_mdio_b", "tsn1_link_b";
31 power-source = <1800>;
35 groups = "tsn2_mdio_b", "tsn2_link_b";
37 power-source = <1800>;
42 pinctrl-0 = <&tsn0_pins>, <&tsn1_pins>, <&tsn2_pins>;
[all …]
Dhihope-rzg2-ex.dtsi1 // SPDX-License-Identifier: GPL-2.0
3 * Device Tree Source for the RZ/G2[HMN] HiHope sub board common parts
19 pinctrl-0 = <&avb_pins>;
20 pinctrl-names = "default";
21 phy-handle = <&phy0>;
22 tx-internal-delay-ps = <2000>;
23 rx-internal-delay-ps = <1800>;
26 phy0: ethernet-phy@0 {
27 compatible = "ethernet-phy-id001c.c915",
28 "ethernet-phy-ieee802.3-c22";
[all …]
Dr8a779h0-gray-hawk-single.dts1 // SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 * Device Tree Source for the R-Car V4M Gray Hawk Single board
11 * Because R-Car V4M has only 1 SSI, it cannot handle both Playback/Capture
28 /dts-v1/;
30 #include <dt-bindings/gpio/gpio.h>
31 #include <dt-bindings/input/input.h>
32 #include <dt-bindings/leds/common.h>
33 #include <dt-bindings/media/video-interfaces.h>
39 compatible = "renesas,gray-hawk-single", "renesas,r8a779h0";
51 can_transceiver0: can-phy0 {
[all …]
/linux-6.14.4/Documentation/usb/
Dgadget_configfs.rst50 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 …]
/linux-6.14.4/fs/xfs/
Dxfs_drain.h1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * Copyright (C) 2022-2023 Oracle. All Rights Reserved.
41 * higher level locking primitive guarding allocation groups.
43 * When there's a collision, cross-referencing between data structures (e.g.
53 * a work item and all the sub-items that the parent item creates before moving
55 * sub-items. Writer threads are permitted to queue multiple work items
57 * sub-items (such as RUIs) must bump the intent counter and maintain it until
58 * the sub-items can themselves bump the intent counter.
65 * The same principles apply to realtime groups because the rt metadata inode
/linux-6.14.4/Documentation/admin-guide/perf/
Dalibaba_pmu.rst2 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 …]
/linux-6.14.4/Documentation/devicetree/bindings/pinctrl/
Dabilis,tb10x-iomux.txt5 -------------------
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 …]
Dberlin,pinctrl.txt1 * 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 …]
Dbrcm,ns2-pinmux.txt8 - 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 …]
Dpinmux-node.yaml1 # 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 <[email protected]>
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 …]
/linux-6.14.4/tools/net/ynl/pyynl/
Dynl_gen_rst.py2 # SPDX-License-Identifier: GPL-2.0
3 # -*- coding: utf-8; mode: python -*-
34 def headroom(level: int) -> str:
39 def bold(text: str) -> str:
44 def inline(text: str) -> str:
49 def sanitize(text: str) -> str:
55 def rst_fields(key: str, value: str, level: int = 0) -> str:
60 def rst_definition(key: str, value: Any, level: int = 0) -> str:
65 def rst_paragraph(paragraph: str, level: int = 0) -> str:
70 def rst_bullet(item: str, level: int = 0) -> str:
[all …]
/linux-6.14.4/tools/perf/pmu-events/
Dmetric.py1 # SPDX-License-Identifier: (LGPL-2.1 OR BSD-2-Clause)
13 def ToPerfJson(self) -> str:
17 def ToPython(self) -> str:
25 def Equals(self, other) -> bool:
29 def Substitute(self, name: str, expression: 'Expression') -> 'Expression':
32 def __str__(self) -> str:
35 def __or__(self, other: Union[int, float, 'Expression']) -> 'Operator':
38 def __ror__(self, other: Union[int, float, 'Expression']) -> 'Operator':
41 def __xor__(self, other: Union[int, float, 'Expression']) -> 'Operator':
44 def __and__(self, other: Union[int, float, 'Expression']) -> 'Operator':
[all …]
/linux-6.14.4/Documentation/netlink/
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)?$
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 …]
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)$
26 required: [ name, doc, attribute-sets, operations ]
[all …]
/linux-6.14.4/Documentation/userspace-api/netlink/
Dspecs.rst1 .. 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 …]
Dnetlink-raw.rst1 .. 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 …]
/linux-6.14.4/Documentation/devicetree/bindings/pci/
Dsnps,dw-pcie-common.yaml1 # 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 <[email protected]>
11 - Gustavo Pimentel <[email protected]>
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 …]
/linux-6.14.4/Documentation/netlink/specs/
Dnlctrl.yaml1 # 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 …]
/linux-6.14.4/tools/net/ynl/pyynl/lib/
Dnlspec.py1 # SPDX-License-Identifier: GPL-2.0 OR BSD-3-Clause
37 self.ident_name = self.name.replace('-', '_')
119 value_start = self.yaml.get('value-start', 0)
160 sub_type string, name of sub type
164 sub_message string, name of sub message type
166 sub-message type
168 is_auto_scalar bool, attr is a variable-size scalar
176 self.is_multi = yaml.get('multi-attr', False)
178 self.sub_type = yaml.get('sub-type')
179 self.byte_order = yaml.get('byte-order')
[all …]
/linux-6.14.4/include/target/iscsi/
Discsi_target_stat.h1 /* SPDX-License-Identifier: GPL-2.0 */
10 * For struct iscsi_tiqn->tiqn_wwn default groups
19 * For struct iscsi_session->se_sess default groups
39 /* iSCSI login failure types (sub oids) */
/linux-6.14.4/Documentation/arch/powerpc/
Dassociativity.rst9 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 …]

123456789