Home
last modified time | relevance | path

Searched +full:on +full:- +full:die (Results 1 – 25 of 35) sorted by relevance

12

/Documentation/ABI/testing/
Dsysfs-devices-mapping6 each dieX file (where X is die number) holds "Segment:Root Bus"
9 For example, on 4-die Xeon platform with up to 6 IIO stacks per
10 die and, therefore, 6 IIO PMON blocks per die, the mapping of
13 $ ls /sys/devices/uncore_iio_0/die*
14 -r--r--r-- /sys/devices/uncore_iio_0/die0
15 -r--r--r-- /sys/devices/uncore_iio_0/die1
16 -r--r--r-- /sys/devices/uncore_iio_0/die2
17 -r--r--r-- /sys/devices/uncore_iio_0/die3
19 $ tail /sys/devices/uncore_iio_0/die*
31 IIO PMU 0 on die 0 belongs to PCI RP on bus 0x00, domain 0x0000
[all …]
/Documentation/hwmon/
Dxgene-hwmon.rst1 Kernel driver xgene-hwmon
6 * APM X-Gene SoC
9 -----------
12 APM X-Gene SoC using the mailbox communication interface.
19 - SoC on-die temperature in milli-degree C
20 - Alarm when high/over temperature occurs
23 - CPU power in uW
24 - IO power in uW
26 sysfs-Interface
27 ---------------
[all …]
Dk10temp.rst8 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
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",
53 BIOS and Kernel Developer's Guide (BKDG) for AMD Family 14h Models 00h-0Fh Processors:
69 Revision Guide for AMD Family 14h Models 00h-0Fh Processors:
88 -----------
93 All these processors have a sensor, but on those for Socket F or AM2+,
[all …]
Dsparx5-temp.rst1 .. SPDX-License-Identifier: GPL-2.0-only
3 Microchip SparX-5 SoC
10 Prefix: 'sparx5-temp'
12 Addresses scanned: -
19 -----------
21 The Sparx5 SoC contains a temperature sensor based on the MR74060
24 The sensor has a range of -40°C to +125°C and an accuracy of +/-5°C.
27 -------------
32 temp1_input Die temperature (in millidegree Celsius.)
Dintel-m10-bmc-hwmon.rst1 .. SPDX-License-Identifier: GPL-2.0
3 Kernel driver intel-m10-bmc-hwmon
10 Prefix: 'n3000bmc-hwmon'
16 -----------
22 sensor data of different components on the board. The BMC firmware is
34 ----------------
38 - Intel MAX 10 BMC for Intel PAC N3000:
47 temp2_label "FPGA Die Temperature"
78 All the attributes are read-only.
Dltc2978.rst10 Addresses scanned: -
18 Addresses scanned: -
26 Addresses scanned: -
34 Addresses scanned: -
42 Addresses scanned: -
52 Addresses scanned: -
60 Addresses scanned: -
68 Addresses scanned: -
76 Addresses scanned: -
84 Addresses scanned: -
[all …]
Dadm1021.rst10 Addresses scanned: I2C 0x18 - 0x1a, 0x29 - 0x2b, 0x4c - 0x4e
18 Addresses scanned: I2C 0x18 - 0x1a, 0x29 - 0x2b, 0x4c - 0x4e
26 Addresses scanned: I2C 0x18 - 0x1a, 0x29 - 0x2b, 0x4c - 0x4e
34 Addresses scanned: I2C 0x18 - 0x1a, 0x29 - 0x2b, 0x4c - 0x4e
42 Addresses scanned: I2C 0x18 - 0x1a, 0x29 - 0x2b, 0x4c - 0x4e
50 Addresses scanned: I2C 0x18 - 0x1a, 0x29 - 0x2b, 0x4c - 0x4e
58 Addresses scanned: I2C 0x18 - 0x1a, 0x29 - 0x2b, 0x4c - 0x4e
66 Addresses scanned: I2C 0x18 - 0x1a, 0x29 - 0x2b, 0x4c - 0x4e
74 Addresses scanned: I2C 0x18 - 0x1a, 0x29 - 0x2b, 0x4c - 0x4e
82 Addresses scanned: I2C 0x18 - 0x1a, 0x29 - 0x2b, 0x4c - 0x4e
[all …]
/Documentation/admin-guide/pm/
Dintel-speed-select.rst1 .. SPDX-License-Identifier: GPL-2.0
14 - https://www.intel.com/content/www/us/en/architecture-and-technology/speed-select-technology-artic…
15 - https://builders.intel.com/docs/networkbuilders/intel-speed-select-technology-base-frequency-enha…
19 dynamically without pre-configuring via BIOS setup options. This dynamic
29 intel-speed-select configuration tool
32 Most Linux distribution packages may include the "intel-speed-select" tool. If not,
38 # cd tools/power/x86/intel-speed-select/
43 ------------
47 # intel-speed-select --help
49 The top-level help describes arguments and features. Notice that there is a
[all …]
/Documentation/driver-api/
Dhsi.rst5 ---------------
8 that is optimized for die-level interconnect between an Application Processor
18 commonly prefixed by AC for signals going from the application die to the
19 cellular die and CA for signals going the other way around.
23 +------------+ +---------------+
25 | Die | | Die |
26 | | - - - - - - CAWAKE - - - - - - >| |
27 | T|------------ CADATA ------------>|R |
28 | X|------------ CAFLAG ------------>|X |
29 | |<----------- ACREADY ------------| |
[all …]
/Documentation/locking/
Dww-mutex-design.rst2 Wound/Wait Deadlock-Proof Mutex Design
5 Please read mutex-design.txt first, as it applies to wait/wound mutexes too.
7 Motivation for WW-Mutexes
8 -------------------------
12 domains (for example VRAM vs system memory), and so on. And with
15 become ready. If you think about this in terms of waiting on a buffer
22 buffer(s) into VRAM before the GPU operates on the buffer(s), which
37 and the deadlock handling approach is called Wait-Die. The name is based on
41 and dies. Hence Wait-Die.
42 There is also another algorithm called Wound-Wait:
[all …]
Drobust-futex-ABI.rst9 futexes, for kernel assist of cleanup of held locks on task exit.
11 The interesting data as to what futexes a thread is holding is kept on a
25 threads in the kernel. Options on the sys_futex(2) system call support
26 waiting on a particular futex, and waking up the next waiter on a
32 to do so, then improperly listed locks will not be cleaned up on exit,
34 waiting on the same locks.
43 consisting of three words. Each word is 32 bits on 32 bit arch's, or 64
44 bits on 64 bit arch's, and local byte order. Each thread should have
47 If a thread is running in 32 bit compatibility mode on a 64 native arch
48 kernel, then it can actually have two such structures - one using 32 bit
[all …]
/Documentation/admin-guide/
Dcputopology.rst17 the CPU die ID of cpuX. Typically it is the hardware platform's
46 human-readable list of CPUs within the same core.
56 human-readable list of CPUs sharing the same physical_package_id.
61 internal kernel map of CPUs within the same die.
65 human-readable list of CPUs within the same die.
74 human-readable list of cpuX's hardware threads within the same
84 human-readable list of cpuX's hardware threads within the same
87 Architecture-neutral, drivers/base/topology.c, exports these attributes.
91 CONFIG_SCHED_BOOK and CONFIG_SCHED_DRAWER are currently only used on s390,
95 these macros in include/asm-XXX/topology.h::
[all …]
/Documentation/admin-guide/nfs/
Dnfs-client.rst14 and work is in progress on adding support for minor version 1 of the NFSv4
17 The purpose of this document is to provide information on some of the
68 …530 Section 6\: Filesystem Migration and Replication: https://tools.ietf.org/html/rfc3530#section-6
69 …lementation Guide for Referrals in NFSv4: https://tools.ietf.org/html/draft-ietf-nfsv4-referrals-00
85 - the cache name, "dns_resolve"
86 - the hostname to resolve
89 writes the result into the rpc_pipefs pseudo-file
111 .. code-block:: sh
121 die()
127 [ $# -lt 2 ] && die
[all …]
/Documentation/devicetree/bindings/mfd/
Dab8500.txt1 * AB8500 Multi-Functional Device (MFD)
4 - compatible : contains "stericsson,ab8500" or "stericsson,ab8505";
5 - interrupts : contains the IRQ line for the AB8500
6 - interrupt-controller : describes the AB8500 as an Interrupt Controller (has its own domain)
7 - #interrupt-cells : should be 2, for 2-cell format
8 - The first cell is the AB8500 local IRQ number
9 - The second cell is used to specify optional parameters
10 - bits[3:0] trigger type and level flags:
11 1 = low-to-high edge triggered
12 2 = high-to-low edge triggered
[all …]
Dmax77693.txt1 Maxim MAX77693 multi-function device
4 - PMIC,
5 - CHARGER,
6 - LED,
7 - MUIC,
8 - HAPTIC
14 - compatible : Must be "maxim,max77693".
15 - reg : Specifies the i2c slave address of PMIC block.
16 - interrupts : This i2c device has an IRQ line connected to the main SoC.
19 - regulators : The regulators of max77693 have to be instantiated under subnode
[all …]
/Documentation/devicetree/bindings/interrupt-controller/
Dmarvell,odmi-controller.txt4 Some Marvell SoCs have an On-Die Message Interrupt (ODMI) controller
5 which can be used by on-board peripheral for MSI interrupts.
9 - compatible : The value here should contain:
11 "marvell,ap806-odmi-controller", "marvell,odmi-controller".
13 - interrupt,controller : Identifies the node as an interrupt controller.
15 - msi-controller : Identifies the node as an MSI controller.
17 - marvell,odmi-frames : Number of ODMI frames available. Each frame
20 - reg : List of register definitions, one for each
23 - marvell,spi-base : List of GIC base SPI interrupts, one for each
24 ODMI frame. Those SPI interrupts are 0-based,
[all …]
/Documentation/devicetree/bindings/regulator/
Dmax8973-regulator.txt5 - compatible: must be one of following:
8 - reg: the i2c slave address of the regulator. It should be 0x1b.
15 -maxim,externally-enable: boolean, externally control the regulator output
17 -maxim,enable-gpio: GPIO for enable control. If the valid GPIO is provided
19 -maxim,dvs-gpio: GPIO which is connected to DVS pin of device.
20 -maxim,dvs-default-state: Default state of GPIO during initialisation.
22 -maxim,enable-remote-sense: boolean, enable reote sense.
23 -maxim,enable-falling-slew-rate: boolean, enable falling slew rate.
24 -maxim,enable-active-discharge: boolean: enable active discharge.
25 -maxim,enable-frequency-shift: boolean, enable 9% frequency shift.
[all …]
/Documentation/devicetree/bindings/mtd/
Dnand-controller.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/mtd/nand-controller.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Miquel Raynal <miquel.raynal@bootlin.com>
11 - Richard Weinberger <richard@nod.at>
24 The interpretation of these parameters is implementation-defined, so
31 pattern: "^nand-controller(@.*)?"
33 "#address-cells":
36 "#size-cells":
[all …]
/Documentation/admin-guide/kdump/
Dkdump.rst2 Documentation for Kdump - The kexec-based Crash Dumping Solution
11 Kdump uses kexec to quickly boot to a dump-capture kernel whenever a
14 the reboot and is accessible to the dump-capture kernel.
17 memory image to a dump file on the local disk, or across the network to
20 Kdump and kexec are currently supported on the x86, x86_64, ppc64, ia64,
24 the dump-capture kernel. This ensures that ongoing Direct Memory Access
25 (DMA) from the system kernel does not corrupt the dump-capture kernel.
26 The kexec -p command loads the dump-capture kernel into this reserved
29 On x86 machines, the first 640 KB of physical memory is needed to boot,
31 region just before rebooting into the dump-capture kernel.
[all …]
/Documentation/x86/
Dtopology.rst1 .. SPDX-License-Identifier: GPL-2.0
11 The architecture-agnostic topology definitions are in
12 Documentation/admin-guide/cputopology.rst. This file holds x86-specific
14 definitions. Thus, the way to read up on Linux topology on x86 is to start
17 Needless to say, code should use the generic functions - this file is *only*
35 - packages
36 - cores
37 - threads
44 Modern systems may also use the term 'Die' for package.
48 Package-related topology information in the kernel:
[all …]
/Documentation/process/
Dbotching-up-ioctls.rst5 From: https://blog.ffwll.ch/2013/11/botching-up-ioctls.html
11 memory on completely different GPUs is a futile effort. So nowadays every
13 Which is nice, since there's no more insanity in the form of fake-generic, but
19 only cover technicalities and not the big-picture issues like what the command
21 something every GPU driver has to do on its own.
25 -------------
28 will need to add a 32-bit compat layer:
33 * Align everything to the natural size and use explicit padding. 32-bit
34 platforms don't necessarily align 64-bit values to 64-bit boundaries, but
35 64-bit platforms do. So we always need padding to the natural size to get
[all …]
/Documentation/trace/postprocess/
Dtrace-pagealloc-postprocess.pl4 # to extract some high-level information on what is going on. The accuracy of the parser
7 # Example usage: trace-pagealloc-postprocess.pl < /sys/kernel/debug/tracing/trace_pipe
9 # --prepend-parent Report on the parent proc and PID
10 # --read-procstat If the trace lacks process info, get it from /proc
11 # --ignore-pid Aggregate processes of the same name together
31 # High-level events extrapolated from tracepoints
45 # Catch sigint and exit on request
52 if ($current_time - 2 > $sigint_received) {
53 print "SIGINT received, report pending. Hit ctrl-c again to exit\n";
74 'ignore-pid' => \$opt_ignorepid,
[all …]
/Documentation/devicetree/bindings/iio/adc/
Dqcom,pm8xxx-xoadc.txt8 - compatible: should be one of:
9 "qcom,pm8018-adc"
10 "qcom,pm8038-adc"
11 "qcom,pm8058-adc"
12 "qcom,pm8921-adc"
14 - reg: should contain the ADC base address in the PMIC, typically
17 - xoadc-ref-supply: should reference a regulator that can supply
18 a reference voltage on demand. The reference voltage may vary
22 iio-bindings.txt for more details, but notice that this particular
26 - #address-cells: should be set to <2>, the first cell is the
[all …]
/Documentation/security/keys/
Drequest-key.rst45 The main difference between the access points is that the in-kernel interface
50 The request_key_tag() call is like the in-kernel request_key(), except that it
57 mechanism rather than using /sbin/request-key.
70 forking and execution of /sbin/request-key.
95 4) request_key() then forks and executes /sbin/request-key with a new session
98 5) /sbin/request-key assumes the authority associated with key U.
100 6) /sbin/request-key execs an appropriate program to perform the actual
123 3) and another copy of /sbin/request-key spawned (as per step 4); but the
128 /sbin/request-key at the appropriate places because (a) execve will discard two
137 This is a short duration placeholder that causes any attempt at re-requesting
[all …]
/Documentation/admin-guide/media/
Dfaq.rst1 .. SPDX-License-Identifier: GPL-2.0
12 channel on this FAQ, and *services* for the logical channel.
23 1. The signal seems to die a few seconds after tuning.
28 is closed). The ``dvb-core`` module parameter ``dvb_shutdown_timeout``
37 tools and are grouped together with the ``v4l-utils`` git repository:
39 https://git.linuxtv.org/v4l-utils.git/
48 for example the ``dvbv5-scan`` tool. You can find more information
51 https://www.linuxtv.org/wiki/index.php/Dvbv5-scan
64 transponders available on your area. So, LinuxTV developers
70 https://git.linuxtv.org/dtv-scan-tables.git
[all …]

12