Searched +full:a +full:- +full:za +full:- +full:z0 +full:- +full:9 +full:- (Results 1 – 8 of 8) sorted by relevance
| /Documentation/devicetree/bindings/bus/ |
| D | allwinner,sun50i-a64-de2.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/bus/allwinner,sun50i-a64-de2.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Chen-Yu Tsai <wens@csie.org>
11 - Maxime Ripard <mripard@kernel.org>
15 pattern: "^bus(@[0-9a-f]+)?$"
17 "#address-cells":
20 "#size-cells":
25 - const: allwinner,sun50i-a64-de2
[all …]
|
| /Documentation/arch/arm64/ |
| D | sme.rst | 14 model. To aid understanding, a minimal description of relevant programmer's
15 model features for SME is included in Appendix A.
19 -----------
21 * PSTATE.SM, PSTATE.ZA, the streaming mode vector length, the ZA and (when
26 instructions and registers, and the Linux-specific system interfaces
31 the SME2 instructions and ZT0, and the Linux-specific system interfaces
42 * There are a number of optional SME features, presence of these is reported
58 cpu-feature-registers.txt for details.
62 way of detecting support for these regsets is to connect to a target process
63 first and then attempt a
[all …]
|
| /Documentation/devicetree/bindings/thermal/ |
| D | thermal-zones.yaml | 1 # SPDX-License-Identifier: (GPL-2.0)
4 ---
5 $id: http://devicetree.org/schemas/thermal/thermal-zones.yaml#
6 $schema: http://devicetree.org/meta-schemas/base.yaml#
11 - Daniel Lezcano <daniel.lezcano@linaro.org>
18 The following node types are used to completely describe a thermal management
20 - thermal-sensor: device that measures temperature, has SoC-specific bindings
21 - cooling-device: device used to dissipate heat either passively or actively
22 - thermal-zones: a container of the following node types used to describe all
25 This binding describes the thermal-zones.
[all …]
|
| /Documentation/trace/postprocess/ |
| D | trace-pagealloc-postprocess.pl | 2 # This is a POC (proof of concept or piece of crap, take your pick) for reading the
4 # 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/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
29 use constant STATE_PCPU_PAGES_REFILLED => 9;
31 # High-level events extrapolated from tracepoints
52 if ($current_time - 2 > $sigint_received) {
53 print "SIGINT received, report pending. Hit ctrl-c again to exit\n";
[all …]
|
| D | trace-vmscan-postprocess.pl | 2 # This is a POC for reading the text representation of trace output related to
3 # page reclaim. It makes an attempt to extract some high-level information on
6 # Example usage: trace-vmscan-postprocess.pl < /sys/kernel/tracing/trace_pipe
8 # --read-procstat If the trace lacks process info, get it from /proc
9 # --ignore-pid Aggregate processes of the same name together
25 use constant MM_VMSCAN_WRITEPAGE_ANON_SYNC => 9;
31 # Per-order events
43 # High-level events extrapolated from tracepoints
83 if ($current_time - 2 > $sigint_received) {
84 print "SIGINT received, report pending. Hit ctrl-c again to exit\n";
[all …]
|
| /Documentation/devicetree/bindings/display/ |
| D | simple-framebuffer.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/display/simple-framebuffer.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Hans de Goede <hdegoede@redhat.com>
13 A simple frame-buffer describes a frame-buffer setup by firmware or
19 sub-nodes of the chosen node (*). Simplefb nodes must be named
22 If the devicetree contains nodes for the display hardware used by a
23 simplefb, then the simplefb node must contain a property called
24 display, which contains a phandle pointing to the primary display
[all …]
|
| /Documentation/devicetree/bindings/ |
| D | vendor-prefixes.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/vendor-prefixes.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Rob Herring <robh@kernel.org>
19 "^(at25|bm|devbus|dmacap|dsa|exynos|fsi[ab]|gpio-fan|gpio-key|gpio|gpmc|hdmi|i2c-gpio),.*": true
21 "^(pinctrl-single|#pinctrl-single|PowerPC),.*": true
22 "^(pl022|pxa-mmc|rcar_sound|rotary-encoder|s5m8767|sdhci),.*": true
23 "^(simple-audio-card|st-plgpio|st-spics|ts),.*": true
50 "^active-semi,.*":
[all …]
|
| /Documentation/bpf/libbpf/ |
| D | program_types.rst | 1 .. SPDX-License-Identifier: (LGPL-2.1 OR BSD-2-Clause)
11 - ``type`` is an exact match, e.g. ``SEC("socket")``
12 - ``type+`` means it can be either exact ``SEC("type")`` or well-formed ``SEC("type/extras")``
13 with a '``/``' separator between ``type`` and ``extras``.
15 When ``extras`` are specified, they provide details of how to auto-attach the BPF program. The
21 +-------------------------------------------+----------------------------------------+-------------…
25 +-------------------------------------------+----------------------------------------+-------------…
27 … +----------------------------------------+------------------------…
29 … +----------------------------------------+------------------------…
31 +-------------------------------------------+----------------------------------------+-------------…
[all …]
|