Home
last modified time | relevance | path

Searched +full:1 +full:- +full:9 (Results 1 – 25 of 733) sorted by relevance

12345678910>>...30

/Documentation/devicetree/bindings/dma/
Drenesas,rcar-dmac.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/dma/renesas,rcar-dmac.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Renesas R-Car and RZ/G DMA Controller
10 - Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
13 - $ref: "dma-controller.yaml#"
18 - enum:
19 - renesas,dmac-r8a7742 # RZ/G1H
20 - renesas,dmac-r8a7743 # RZ/G1M
[all …]
/Documentation/ABI/testing/
Dsysfs-devices-platform-sh_mobile_lcdc_fb1 What: /sys/devices/platform/sh_mobile_lcdc_fb.[0-3]/graphics/fb[0-9]/ovl_alpha
5 This file is only available on fb[0-9] devices corresponding
12 What: /sys/devices/platform/sh_mobile_lcdc_fb.[0-3]/graphics/fb[0-9]/ovl_mode
16 This file is only available on fb[0-9] devices corresponding
22 - 0 - Alpha Blending
23 - 1 - ROP3
25 What: /sys/devices/platform/sh_mobile_lcdc_fb.[0-3]/graphics/fb[0-9]/ovl_position
29 This file is only available on fb[0-9] devices corresponding
33 position format is `[0-9]+,[0-9]+`.
35 What: /sys/devices/platform/sh_mobile_lcdc_fb.[0-3]/graphics/fb[0-9]/ovl_rop3
[all …]
/Documentation/devicetree/bindings/soundwire/
Dsoundwire-controller.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/soundwire/soundwire-controller.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
11 - Vinod Koul <vkoul@kernel.org>
21 "#address-cells":
24 "#size-cells":
28 "^.*@[0-9a-f],[0-9a-f]$":
33 pattern: "^sdw[0-9a-f]{1}[0-9a-f]{4}[0-9a-f]{4}[0-9a-f]{2}$"
[all …]
/Documentation/devicetree/bindings/sound/
Dnvidia,tegra210-admaif.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/sound/nvidia,tegra210-admaif.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
17 - Jon Hunter <jonathanh@nvidia.com>
18 - Sameer Pujar <spujar@nvidia.com>
22 pattern: "^admaif@[0-9a-f]*$"
26 - enum:
27 - nvidia,tegra210-admaif
28 - nvidia,tegra186-admaif
[all …]
Dsprd-pcm.txt4 - compatible: Should be "sprd,pcm-platform".
5 - dmas: Specify the list of DMA controller phandle and DMA request line ordered pairs.
6 - dma-names: Identifier string for each DMA request line in the dmas property.
7 These strings correspond 1:1 with the ordered pairs in dmas.
12 compatible = "sprd,pcm-platform";
13 dmas = <&agcp_dma 1 1>, <&agcp_dma 2 2>,
17 <&agcp_dma 9 9>, <&agcp_dma 10 10>;
18 dma-names = "normal_p_l", "normal_p_r",
/Documentation/trace/postprocess/
Dtrace-vmscan-postprocess.pl3 # page reclaim. It makes an attempt to extract some high-level information on
6 # Example usage: trace-vmscan-postprocess.pl < /sys/kernel/debug/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
17 use constant MM_VMSCAN_DIRECT_RECLAIM_BEGIN => 1;
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 …]
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
19 use constant MM_PAGE_ALLOC => 1;
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 …]
/Documentation/ABI/stable/
Dsysfs-class-rfkill1 rfkill - radio frequency (RF) connector kill switch support
3 For details to this subsystem look at Documentation/driver-api/rfkill.rst.
6 Documentation/ABI/removed/sysfs-class-rfkill.
9 Date: 09-Jul-2007
11 Contact: linux-wireless@vger.kernel.org,
17 What: /sys/class/rfkill/rfkill[0-9]+/name
18 Date: 09-Jul-2007
20 Contact: linux-wireless@vger.kernel.org
25 What: /sys/class/rfkill/rfkill[0-9]+/type
26 Date: 09-Jul-2007
[all …]
/Documentation/userspace-api/media/v4l/
Dpixfmt-y10p.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _V4L2-PIX-FMT-Y10P:
9 Grey-scale image as a MIPI RAW10 packed array
15 This is a packed grey-scale image format with a depth of 10 bits per
21 **Bit-packed representation.**
29 .. flat-table::
30 :header-rows: 0
31 :stub-columns: 0
34 * - Y'\ :sub:`00[9:2]`
35 - Y'\ :sub:`01[9:2]`
[all …]
Dpixfmt-sdr-pcu18be.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _V4L2-SDR-FMT-PCU18BE:
9 Planar complex unsigned 18-bit big endian IQ sample
15 number consist of two parts called In-phase and Quadrature (IQ). Both I
20 the 18 bits, bit 17:2 (16 bit) is data and bit 1:0 (2 bit) can be any
26 .. flat-table::
27 :header-rows: 1
28 :stub-columns: 0
30 * - Offset:
31 - Byte B0
[all …]
Dsubdev-formats.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _v4l2-mbus-format:
12 .. flat-table:: struct v4l2_mbus_framefmt
13 :header-rows: 0
14 :stub-columns: 0
15 :widths: 1 1 2
17 * - __u32
18 - ``width``
19 - Image width in pixels.
20 * - __u32
[all …]
Dpixfmt-y10b.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _V4L2-PIX-FMT-Y10BPACK:
9 Grey-scale image as a bit-packed array
15 This is a packed grey-scale image format with a depth of 10 bits per
16 pixel. Pixels are stored in a bit-packed array of 10bit bits per pixel,
20 **Bit-packed representation.**
25 .. flat-table::
26 :header-rows: 0
27 :stub-columns: 0
29 * - Y'\ :sub:`00[9:2]`
[all …]
/Documentation/devicetree/bindings/soc/ti/
Dti,pruss.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 TI Programmable Real-Time Unit and Industrial Communication Subsystem
11 - Suman Anna <s-anna@ti.com>
15 The Programmable Real-Time Unit and Industrial Communication Subsystem
16 (PRU-ICSS a.k.a. PRUSS) is present on various TI SoCs such as AM335x, AM437x,
17 Keystone 66AK2G, OMAP-L138/DA850 etc. A PRUSS consists of dual 32-bit RISC
18 cores (Programmable Real-Time Units, or PRUs), shared RAM, data and
23 peripheral interfaces, fast real-time responses, or specialized data handling.
[all …]
/Documentation/devicetree/bindings/mfd/
Dkontron,sl28cpld.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Michael Walle <michael@walle.cc>
24 maxItems: 1
26 "#address-cells":
27 const: 1
29 "#size-cells":
32 "#interrupt-cells":
36 maxItems: 1
[all …]
/Documentation/devicetree/bindings/net/
Dethernet-phy.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/net/ethernet-phy.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Andrew Lunn <andrew@lunn.ch>
11 - Florian Fainelli <f.fainelli@gmail.com>
12 - Heiner Kallweit <hkallweit1@gmail.com>
14 # The dt-schema tools will generate a select statement first by using
21 pattern: "^ethernet-phy(@[a-f0-9]+)?$"
24 - $nodename
[all …]
/Documentation/core-api/
Dpacking.rst6 -----------------
10 One can memory-map a pointer to a carefully crafted struct over the hardware
23 were performed byte-by-byte. Also the code can easily get cluttered, and the
24 high-level idea might get lost among the many bit shifts required.
25 Many drivers take the bit-shifting approach and then attempt to reduce the
30 ------------
34 - Packing a CPU-usable number into a memory buffer (with hardware
36 - Unpacking a memory buffer (which has hardware constraints/quirks)
37 into a CPU-usable number.
48 The byte offsets in the packed buffer are always implicitly 0, 1, ... 7.
[all …]
/Documentation/leds/
Dleds-blinkm.rst5 The leds-blinkm driver supports the devices of the BlinkM family.
7 They are RGB-LED modules driven by a (AT)tiny microcontroller and
10 dasy-chain up to 127 BlinkMs on an I2C bus.
16 The interface this driver provides is 2-fold:
23 blinkm-<i2c-bus-nr>-<i2c-device-nr>-<color>
25 $ ls -h /sys/class/leds/blinkm-6-*
26 /sys/class/leds/blinkm-6-9-blue:
29 /sys/class/leds/blinkm-6-9-green:
32 /sys/class/leds/blinkm-6-9-red:
35 (same is /sys/bus/i2c/devices/6-0009/leds)
[all …]
Dleds-lp55xx.rst8 -----------
14 Device attributes for user-space interface
33 LP5523/55231 has 9 output channels::
35 lp55xx_chip for LP5521 ... lp55xx_led #1
39 lp55xx_chip for LP5523 ... lp55xx_led #1
43 lp55xx_led #9
50 - Maximum number of channels
51 - Reset command, chip enable command
52 - Chip specific initialization
53 - Brightness control register access
[all …]
/Documentation/devicetree/bindings/pci/
Dv3-v360epc-pci.txt6 - compatible: should be one of:
7 "v3,v360epc-pci"
8 "arm,integrator-ap-pci", "v3,v360epc-pci"
9 - reg: should contain two register areas:
12 - interrupts: should contain a reference to the V3 error interrupt
14 - bus-range: see pci.txt
15 - ranges: this follows the standard PCI bindings in the IEEE Std
16 1275-1994 (see pci.txt) with the following restriction:
17 - The non-prefetchable and prefetchable memory windows must
19 - The prefetchable memory window must be immediately adjacent
[all …]
/Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/
Dpincfg.txt4 - pio-map : array of pin configurations. Each pin is defined by 6
7 - port : port number of the pin; 0-6 represent port A-G in UM.
8 - pin : pin number in the port.
9 - dir : direction of the pin, should encode as follows:
12 1 = The pin is an output
16 - open_drain : indicates the pin is normal or wired-OR:
19 1 = The pin is an open-drain driver. As an output, the pin is
20 driven active-low, otherwise it is three-stated.
22 - assignment : function number of the pin according to the Pin Assignment
25 - has_irq : indicates if the pin is used as source of external
[all …]
/Documentation/devicetree/bindings/bus/
Dallwinner,sun50i-a64-de2.yaml1 # 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":
18 const: 1
20 "#size-cells":
[all …]
/Documentation/input/devices/
Djoystick-parport.rst3 .. _joystick-parport:
9 :Copyright: |copy| 1998-2000 Vojtech Pavlik <vojtech@ucw.cz>
10 :Copyright: |copy| 1998 Andree Borrmann <a.borrmann@tu-bs.de>
18 Any information in this file is provided as-is, without any guarantee that
36 Many console and 8-bit computer gamepads and joysticks are supported. The
40 ------------
59 for your pads, use either keyboard or joystick port, and make a pass-through
65 needed, and I'd recommend pin 9 for that, the highest data bit. On the other
67 port, anything between and including pin 4 and pin 9 will work::
69 (pin 9) -----> Power
[all …]
/Documentation/devicetree/bindings/interrupt-controller/
Dsifive,plic-1.0.0.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
4 ---
5 $id: http://devicetree.org/schemas/interrupt-controller/sifive,plic-1.0.0.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: SiFive Platform-Level Interrupt Controller (PLIC)
11 SiFive SOCs include an implementation of the Platform-Level Interrupt Controller
12 (PLIC) high-level specification in the RISC-V Privileged Architecture
17 in an 4 core system with 2-way SMT, you have 8 harts and probably at least two
20 Each interrupt can be enabled on per-context basis. Any context can claim
28 While the PLIC supports both edge-triggered and level-triggered interrupts,
[all …]
/Documentation/devicetree/bindings/leds/
Dleds-lp55xx.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/leds/leds-lp55xx.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jacek Anaszewski <jacek.anaszewski@gmail.com>
11 - Pavel Machek <pavel@ucw.cz>
27 - national,lp5521
28 - national,lp5523
29 - ti,lp55231
30 - ti,lp5562
[all …]
/Documentation/networking/
Dpktgen.rst1 .. SPDX-License-Identifier: GPL-2.0
7 Enable CONFIG_NET_PKTGEN to compile and build pktgen either in-kernel
31 overload type of benchmarking, as this could hurt the normal use-case.
35 # ethtool -G ethX tx 1024
38 in the general case, 1) because the TX ring buffer might get larger
44 ring-buffers for various performance reasons, and packets stalling
49 and the cleanup interval is affected by the ethtool --coalesce setting
50 of parameter "rx-usecs".
52 For ixgbe use e.g. "30" resulting in approx 33K interrupts/sec (1/30*10^6)::
54 # ethtool -C ethX rx-usecs 30
[all …]

12345678910>>...30