Searched +full:kernel +full:- +full:family (Results 1 – 25 of 202) sorted by relevance
123456789
| /Documentation/hwmon/ |
| D | k10temp.rst | 1 Kernel driver k10temp
6 * AMD Family 10h processors:
8 Socket F: Quad-Core/Six-Core/Embedded Opteron (but see below)
10 Socket AM2+: Quad-Core Opteron, Phenom (II) X3/X4, Athlon X2 (but see below)
12 Socket AM3: Quad-Core Opteron, Athlon/Phenom II X2/X3/X4, Sempron II
16 * AMD Family 11h processors:
20 * AMD Family 12h processors: "Llano" (E2/A4/A6/A8-Series)
22 * AMD Family 14h processors: "Brazos" (C/E/G/Z-Series)
24 * AMD Family 15h processors: "Bulldozer" (FX-Series), "Trinity", "Kaveri",
27 * AMD Family 16h processors: "Kabini", "Mullins"
[all …]
|
| D | peci-dimmtemp.rst | 1 .. SPDX-License-Identifier: GPL-2.0
3 Kernel driver peci-dimmtemp
9 Intel Xeon E5-14xx v3 family
10 Intel Xeon E5-24xx v3 family
11 Intel Xeon E5-16xx v3 family
12 Intel Xeon E5-26xx v3 family
13 Intel Xeon E5-46xx v3 family
14 Intel Xeon E7-48xx v3 family
15 Intel Xeon E7-88xx v3 family
17 Intel Xeon E5-16xx v4 family
[all …]
|
| D | fam15h_power.rst | 1 Kernel driver fam15h_power
6 * AMD Family 15h Processors
8 * AMD Family 16h Processors
16 - BIOS and Kernel Developer's Guide (BKDG) For AMD Family 15h Processors
17 - BIOS and Kernel Developer's Guide (BKDG) For AMD Family 16h Processors
18 - AMD64 Architecture Programmer's Manual Volume 2: System Programming
23 -----------
33 of AMD Family 15h and 16h processors via TDP algorithm.
35 For AMD Family 15h and 16h processors the following power values can
55 On multi-node processors the calculated value is for the entire
[all …]
|
| D | peci-cputemp.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only
3 Kernel driver peci-cputemp
9 Intel Xeon E5-14xx v3 family
10 Intel Xeon E5-24xx v3 family
11 Intel Xeon E5-16xx v3 family
12 Intel Xeon E5-26xx v3 family
13 Intel Xeon E5-46xx v3 family
14 Intel Xeon E7-48xx v3 family
15 Intel Xeon E7-88xx v3 family
17 Intel Xeon E5-16xx v4 family
[all …]
|
| D | powerz.rst | 1 .. SPDX-License-Identifier: GPL-2.0-or-later
3 Kernel driver POWERZ
8 * ChargerLAB POWER-Z KM003C
12 Addresses scanned: -
16 - Thomas Weißschuh <linux@weissschuh.net>
19 -----------
21 This driver implements support for the ChargerLAB POWER-Z USB-C power testing
22 family.
26 The channel labels exposed via hwmon match the labels used by the on-device
27 display and the official POWER-Z PC software.
|
| /Documentation/arch/arm/ |
| D | microchip.rst | 7 ------------
9 currently supported in Linux Mainline (you know, the one on kernel.org).
11 It is important to note that the Microchip (previously Atmel) ARM-based MPU
12 product line is historically named "AT91" or "at91" throughout the Linux kernel
15 git branches/tags and email subject always contain this "at91" sub-string.
19 ---------
25 - at91rm9200
29 …http://ww1.microchip.com/downloads/en/DeviceDoc/Atmel-1768-32-bit-ARM920T-Embedded-Microprocessor-…
32 - at91sam9260
36 …ttp://ww1.microchip.com/downloads/en/DeviceDoc/Atmel-6221-32-bit-ARM926EJ-S-Embedded-Microprocesso…
[all …]
|
| D | marvell.rst | 6 supported in mainline by the Linux kernel. As the Marvell families of
8 for a particular SoC is available in the Linux kernel. This document
12 Orion family
13 ------------
16 - 88F5082
17 - 88F5181 a.k.a Orion-1
18 - 88F5181L a.k.a Orion-VoIP
19 - 88F5182 a.k.a Orion-NAS
21 …- Datasheet: https://web.archive.org/web/20210124231420/http://csclub.uwaterloo.ca/~board/ts7800/M…
22 …- Programmer's User Guide: https://web.archive.org/web/20210124231536/http://csclub.uwaterloo.ca/~…
[all …]
|
| /Documentation/userspace-api/netlink/ |
| D | intro.rst | 1 .. SPDX-License-Identifier: BSD-3-Clause
8 It aims to replace fixed-format C structures as supplied
12 To achieve this Netlink uses a minimal fixed-format metadata header
27 .. code-block:: c
32 in both directions (to and from the kernel). The operations are still
39 .. code-block:: c
52 .. code-block:: c
69 The first two arguments of the socket() call require little explanation -
76 --------------------------
82 file, they include among others - general networking (NETLINK_ROUTE),
[all …]
|
| D | c-code-gen.rst | 1 .. SPDX-License-Identifier: BSD-3-Clause
9 allowed in older families by the ``genetlink-c`` protocol level,
14 of ``name`` in an attribute, and ``$family`` is the name of the
15 family (the global ``name`` property).
17 The upper case is used to denote literal values, e.g. ``$family-CMD``
18 means the concatenation of ``$family``, a dash character, and the literal
22 and with dashes (``-``) replaced by underscores (``_``).
25 appended (``do`` -> ``do_``).
30 ``c-family-name`` controls the name of the ``#define`` for the family
31 name, default is ``$family-FAMILY-NAME``.
[all …]
|
| D | intro-specs.rst | 1 .. SPDX-License-Identifier: BSD-3-Clause
13 Kernel comes with a simple CLI tool which should be useful when
16 to the kernel. Only Generic Netlink is supported.
21 - ``--spec`` - point to the spec file
22 - ``--do $name`` / ``--dump $name`` - issue request ``$name``
23 - ``--json $attrs`` - provide attributes for the request
24 - ``--subscribe $group`` - receive notifications from ``$group``
30 $ ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/ethtool.yaml \
31 --do rings-get \
32 --json '{"header":{"dev-index": 18}}'
[all …]
|
| D | specs.rst | 1 .. SPDX-License-Identifier: BSD-3-Clause
10 hand written Netlink code for each new family, command, attribute.
13 kernel headers directly.
15 Internally kernel uses the YAML specs to generate:
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)``
[all …]
|
| D | genetlink-legacy.rst | 1 .. SPDX-License-Identifier: BSD-3-Clause
9 the ``genetlink-legacy`` protocol level.
15 -------
22 Generic Netlink family version, default is 1.
24 ``version`` has historically been used to introduce family changes
29 --------------------
31 New Netlink families should use ``multi-attr`` to define arrays.
32 Older families (e.g. ``genetlink`` control family) attempted to
35 For reference the ``multi-attr`` array may look like this::
37 [ARRAY-ATTR]
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-habanalabs | 4 Contact: ogabbay@kernel.org
5 Description: Version of the Linux kernel running on the device's CPU.
6 Will be DEPRECATED in Linux kernel version 5.10, and be
12 Contact: ogabbay@kernel.org
14 Will be DEPRECATED in Linux kernel version 5.10, and be
20 Contact: ogabbay@kernel.org
25 only for the Gaudi ASIC family
30 Contact: ogabbay@kernel.org
32 This property is valid only for the Gaudi ASIC family
37 Contact: ogabbay@kernel.org
[all …]
|
| D | sysfs-devices-soc | 3 contact: Lee Jones <lee@kernel.org>
5 The /sys/devices/ directory contains a sub-directory for each
6 System-on-Chip (SoC) device on a running platform. Information
17 contact: Lee Jones <lee@kernel.org>
19 Read-only attribute common to all SoCs. Contains the SoC machine
22 What: /sys/devices/socX/family
24 contact: Lee Jones <lee@kernel.org>
26 Read-only attribute common to all SoCs. Contains SoC family name
57 Read-only attribute supported by most SoCs. Contains the SoC's
62 contact: Lee Jones <lee@kernel.org>
[all …]
|
| /Documentation/crypto/ |
| D | userspace-if.rst | 5 ------------
7 The concepts of the kernel crypto API visible to kernel space is fully
8 applicable to the user space interface as well. Therefore, the kernel
9 crypto API high level discussion for the in-kernel use cases applies
16 The following covers the user space interface exported by the kernel
19 applications that require cryptographic services from the kernel.
21 Some details of the in-kernel kernel crypto API aspects do not apply to
29 ------------------------------
31 The kernel crypto API is accessible from user space. Currently, the
34 - Message digest including keyed message digest (HMAC, CMAC)
[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
9 families registered in the kernel (including itself).
12 -
13 name: op-flags
15 enum-name:
17 - admin-perm
18 - cmd-cap-do
[all …]
|
| D | mptcp_pm.yaml | 1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
4 protocol: genetlink-legacy
7 c-family-name: mptcp-pm-name
8 c-version-name: mptcp-pm-ver
9 max-by-define: true
10 kernel-policy: per-op
11 cmd-cnt-name: --mptcp-pm-cmd-after-last
14 -
16 name: event-type
17 enum-name: mptcp-event-type
[all …]
|
| /Documentation/netlink/ |
| 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 …]
|
| 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.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 | 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 ]
25 description: Name of the netlink family.
31 enum: [ netlink-raw ] # Trim
32 # Start netlink-raw
[all …]
|
| /Documentation/arch/sh/ |
| D | new-machine.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 Paul Mundt <lethal@linux-sh.org>
18 of the board-specific code (with the exception of stboards) ended up
19 in arch/sh/kernel/ directly, with board-specific headers ending up in
20 include/asm-sh/. For the new kernel, things are broken out by board type,
24 Board-specific code::
27 |-- arch
28 | `-- sh
29 | `-- boards
30 | |-- adx
[all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | samsung,s2mps11.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Samsung S2M and S5M family clock generator block
10 - Krzysztof Kozlowski <krzk@kernel.org>
13 This is a part of device tree bindings for S2M and S5M family of Power
20 dt-bindings/clock/samsung,s2mps11.h header.
28 - samsung,s2mps11-clk
29 - samsung,s2mps13-clk # S2MPS13 and S2MPS15
30 - samsung,s2mps14-clk
[all …]
|
| /Documentation/timers/ |
| D | timers-howto.rst | 2 delays - Information on the various kernel delay / sleep mechanisms
10 familiar with the inner workings of the Linux Kernel.
14 ----------------
21 You must use the `*delay` family of functions. These
30 udelay is the generally preferred API; ndelay-level
31 precision may not actually exist on many non-PC devices.
38 NON-ATOMIC CONTEXT:
39 You should use the `*sleep[_range]` family of functions.
45 -- Backed by busy-wait loop:
49 -- Backed by hrtimers:
[all …]
|
| /Documentation/arch/arm/spear/ |
| D | overview.rst | 6 ------------
11 The ST Microelectronics SPEAr range of ARM9/CortexA9 System-on-Chip CPUs are
19 - SPEAr3XX (3XX SOC series, based on ARM9)
20 - SPEAr300 (SOC)
21 - SPEAr300 Evaluation Board
22 - SPEAr310 (SOC)
23 - SPEAr310 Evaluation Board
24 - SPEAr320 (SOC)
25 - SPEAr320 Evaluation Board
26 - SPEAr6XX (6XX SOC series, based on ARM9)
[all …]
|
123456789