Home
last modified time | relevance | path

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

1234

/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
26 - Group 0: PMU Cycle Counter. This group has one pair of counters
30 - Group 1: PMU Bandwidth Counters. This group has 8 counters that are used
[all …]
/Documentation/hwmon/
Dibmpowernv.rst11 -----------
22 the DT maps to an attribute file in 'sysfs'. The node exports unique 'sensor-id'
26 -----------
31 ----------------
36 fanX_fault - 0: No fail condition
37 - 1: Failing fan
44 sub-group. In POWER9, this attribute corresponds to
48 - 1: Enable
49 - 0: Disable
52 inX_fault - 0: No fail condition.
[all …]
/Documentation/ABI/testing/
Dsysfs-kernel-iommu_groups5 Description: /sys/kernel/iommu_groups/ contains a number of sub-
6 directories, each representing an IOMMU group. The
7 name of the sub-directory matches the iommu_group_id()
8 for the group, which is an integer value. Within each
10 links to the sysfs devices contained in this group.
11 The group directory also optionally contains a "name"
13 common name for the group.
23 output direct-mapped, MSI, non mappable regions. Each
29 USB devices it is now exposed as "direct-relaxable" instead
38 domain in use by iommu for this group. See include/linux/iommu.h
[all …]
Dsysfs-bus-nvdimm7 The libnvdimm sub-system implements a common sysfs interface for
8 platform nvdimm resources. See Documentation/driver-api/nvdimm/.
14 Description: (RO) Attribute group to describe the magic bits
16 (See ABI/testing/sysfs-bus-event_source-devices-format).
18 Each attribute under this group defines a bit range of the
22 event = "config:0-4" - event ID
32 Description: (RO) Attribute group to describe performance monitoring events
33 for the nvdimm memory device. Each attribute in this group
36 (See ABI/testing/sysfs-bus-event_source-devices-events). A
38 can be found in Documentation/driver-api/nvdimm/$provider.
Dconfigfs-usb-gadget1 What: /config/usb-gadget
5 This group contains sub-groups corresponding to created
8 What: /config/usb-gadget/gadget
21 names are super-speed-plus, super-speed,
22 high-speed, full-speed, and low-speed.
34 What: /config/usb-gadget/gadget/configs
38 This group contains a USB gadget's configurations
40 What: /config/usb-gadget/gadget/configs/config
51 What: /config/usb-gadget/gadget/configs/config/strings
55 This group contains subdirectories for language-specific
[all …]
Dconfigfs-acpi4 Contact: linux-acpi@vger.kernel.org
7 contains sub-groups corresponding to ACPI configurable options.
14 This group contains the configuration for user defined ACPI
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
[all …]
/Documentation/userspace-api/netlink/
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 …]
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 …]
/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).
17 Every function is associated to one named pin group inside the pin controller
18 driver and these names are used to associate pin group predefinitions to pin
19 controller sub-nodes.
22 - abilis,function: should be set to the name of the function's pin group.
[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
9 A pin-controller node should contain subnodes representing the pin group
10 configurations, one per function. Each subnode has the group name and
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 …]
Dcnxt,cx92755-pinctrl.txt11 - compatible: Must be "cnxt,cx92755-pinctrl"
12 - reg: Base address of the General Purpose Pin Mapping register block and the
14 - gpio-controller: Marks the device node as a GPIO controller.
15 - #gpio-cells: Must be <2>. The first cell is the pin number and the
16 second cell is used to specify flags. See include/dt-bindings/gpio/gpio.h
22 compatible = "cnxt,cx92755-pinctrl";
24 gpio-controller;
25 #gpio-cells = <2>;
36 Each pin configuration node is a sub-node of the pin controller node and is a
37 container of an arbitrary number of subnodes, called pin group nodes in this
[all …]
Dmicrochip,pic32-pinctrl.txt3 Please refer to pinctrl-bindings.txt, ../gpio/gpio.txt, and
4 ../interrupt-controller/interrupts.txt for generic information regarding
7 PIC32 'pin configuration node' is a node of a group of pins which can be
12 - compatible: "microchip,pic32mada-pinctrl"
13 - reg: Address range of the pinctrl registers.
14 - clocks: Clock specifier (see clock bindings for details)
16 Required properties for pin configuration sub-nodes:
17 - pins: List of pins to which the configuration applies.
19 Optional properties for pin configuration sub-nodes:
20 ----------------------------------------------------
[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 <linus.walleij@linaro.org>
50 For cases like this, the pin controller driver may use pinctrl-pin-array helper
55 #pinctrl-cells = <2>;
58 pinctrl-pin-array = <
67 Above #pinctrl-cells specifies the number of value cells in addition to the
68 index of the registers. This is similar to the interrupts-extended binding with
[all …]
/Documentation/devicetree/bindings/opp/
Dopp-v2-base.yaml1 # 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/devicetree/bindings/phy/
Dphy-cadence-sierra.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/phy/phy-cadence-sierra.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
14 - Swapnil Jakhade <sjakhade@cadence.com>
15 - Yuti Amonkar <yamonkar@cadence.com>
20 - cdns,sierra-phy-t0
21 - ti,sierra-phy-t0
23 '#address-cells':
26 '#size-cells':
[all …]
Dphy-miphy365x.txt8 - compatible : Should be "st,miphy365x-phy"
9 - st,syscfg : Phandle / integer array property. Phandle of sysconfig group
11 an entry for each port sub-node, specifying the control
12 register offset inside the sysconfig group.
14 Required nodes : A sub-node is required for each channel the controller
16 'reg' and 'reg-names' properties are used inside these
21 - #phy-cells : Should be 1 (See second example)
23 - PHY_TYPE_SATA
24 - PHY_TYPE_PCI
25 - reg : Address and length of register sets for each device in
[all …]
/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 …]
/Documentation/driver-api/media/
Dv4l2-subdev.rst1 .. SPDX-License-Identifier: GPL-2.0
3 V4L2 sub-devices
4 ----------------
6 Many drivers need to communicate with sub-devices. These devices can do all
8 encoding or decoding. For webcams common sub-devices are sensors and camera
12 driver with a consistent interface to these sub-devices the
13 :c:type:`v4l2_subdev` struct (v4l2-subdev.h) was created.
15 Each sub-device driver must have a :c:type:`v4l2_subdev` struct. This struct
16 can be stand-alone for simple sub-devices or it might be embedded in a larger
18 low-level device struct (e.g. ``i2c_client``) that contains the device data as
[all …]
/Documentation/devicetree/bindings/mfd/
Dda9150.txt1 Dialog Semiconductor DA9150 Combined Charger/Fuel-Gauge MFD bindings
3 DA9150 consists of a group of sub-devices:
6 ------ -----------
7 da9150-gpadc : General Purpose ADC
8 da9150-charger : Battery Charger
9 da9150-fg : Battery Fuel-Gauge
14 - compatible : Should be "dlg,da9150"
15 - reg: Specifies the I2C slave address
16 - interrupts: IRQ line info for da9150 chip.
17 - interrupt-controller: da9150 has internal IRQs (own IRQ domain).
[all …]
Dda9055.txt3 DA9055 consists of a large and varied group of sub-devices (I2C Only):
6 ------ ------------ -----------
7 da9055-gpio : : GPIOs
8 da9055-regulator : : Regulators
9 da9055-onkey : : On key
10 da9055-rtc : : RTC
11 da9055-hwmon : : ADC
12 da9055-watchdog : : Watchdog
23 - compatible : Should be "dlg,da9055-pmic"
24 - reg: Specifies the I2C slave address (defaults to 0x5a but can be modified)
[all …]
/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 …]
/Documentation/sphinx/
Dmaintainers_include.py2 # SPDX-License-Identifier: GPL-2.0
3 # -*- coding: utf-8; mode: python -*-
7 maintainers-include
10 Implementation of the ``maintainers-include`` reST-directive.
15 The ``maintainers-include`` reST-directive performs extensive parsing
32 app.add_directive("maintainers-include", MaintainersInclude)
40 u"""MaintainersInclude (``maintainers-include``) directive"""
44 """Parse all the MAINTAINERS lines into ReST for human-readability"""
67 # Ensure a blank line following the last "|"-prefixed line.
73 if re.search('^[A-Z0-9]', line):
[all …]
/Documentation/devicetree/bindings/usb/
Ddwc3-st.txt3 This file documents the parameters for the dwc3-st driver.
8 - compatible : must be "st,stih407-dwc3"
9 - reg : glue logic base address and USB syscfg ctrl register offset
10 - reg-names : should be "reg-glue" and "syscfg-reg"
11 - st,syscon : should be phandle to system configuration node which
13 - resets : list of phandle and reset specifier pairs. There should be two entries, one
15 - reset-names : list of reset signal names. Names should be "powerdown" and "softreset"
16 See: Documentation/devicetree/bindings/reset/st,stih407-powerdown.yaml
19 - #address-cells, #size-cells : should be '1' if the device has sub-nodes
22 - pinctl-names : A pinctrl state named "default" must be defined
[all …]
/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 …]
/Documentation/admin-guide/gpio/
Dgpio-virtuser.rst1 .. 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
25 **Group:** ``/config/gpio-virtuser``
27 This is the top directory of the gpio-consumer configfs tree.
29 **Group:** ``/config/gpio-consumer/example-name``
[all …]

1234