Searched +full:0 +full:- +full:9 (Results 1 – 25 of 593) sorted by relevance
12345678910>>...24
| /Documentation/filesystems/ |
| D | 9p.txt | 1 v9fs: Plan 9 Resource Sharing for Linux
7 v9fs is a Unix implementation of the Plan 9 9p remote filesystem protocol.
16 the 9p client is available in the form of a USENIX paper:
21 http://xcpu.org/papers/xcpu-talk.pdf
25 http://xcpu.org/papers/cellfs-talk.pdf
26 * PROSE I/O: Using 9p to enable Application Partitions
28 * VirtFS: A Virtualization Aware File System pass-through
36 mount -t 9p 10.10.1.2 /mnt/9
38 For Plan 9 From User Space applications (http://swtch.com/plan9)
40 mount -t 9p `namespace`/acme /mnt/9 -o trans=unix,uname=$USER
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-devices-platform-sh_mobile_lcdc_fb | 1 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
9 from 0 (transparent) to 255 (opaque). The value is ignored if
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]+'.
[all …]
|
| D | sysfs-class-switchtec | 1 switchtec - Microsemi Switchtec PCI Switch Management Endpoint
3 For details on this subsystem look at Documentation/driver-api/switchtec.rst.
6 Date: 05-Jan-2017
11 subfolder (X being an integer >= 0).
14 What: /sys/class/switchtec/switchtec[0-9]+/component_id
15 Date: 05-Jan-2017
23 What: /sys/class/switchtec/switchtec[0-9]+/component_revision
24 Date: 05-Jan-2017
31 What: /sys/class/switchtec/switchtec[0-9]+/component_vendor
32 Date: 05-Jan-2017
[all …]
|
| /Documentation/devicetree/bindings/soundwire/ |
| D | soundwire-controller.yaml | 1 # 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":
25 const: 0
28 "^.*@[0-9a-f],[0-9a-f]$":
[all …]
|
| /Documentation/trace/postprocess/ |
| D | trace-vmscan-postprocess.pl | 3 # 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
25 use constant MM_VMSCAN_WRITEPAGE_ANON_SYNC => 9;
31 # Per-order events
43 # High-level events extrapolated from tracepoints
77 my $sigint_report = 0;
78 my $sigint_exit = 0;
79 my $sigint_pending = 0;
[all …]
|
| D | trace-pagealloc-postprocess.pl | 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/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
29 use constant STATE_PCPU_PAGES_REFILLED => 9;
31 # High-level events extrapolated from tracepoints
46 my $sigint_report = 0;
47 my $sigint_exit = 0;
48 my $sigint_pending = 0;
[all …]
|
| /Documentation/ABI/stable/ |
| D | sysfs-class-rfkill | 1 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,
14 subfolder (X being an integer >= 0).
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
[all …]
|
| D | sysfs-bus-firewire | 1 What: /sys/bus/firewire/devices/fw[0-9]+/
4 Contact: linux1394-devel@lists.sourceforge.net
7 Read-only. Mutable during the node device's lifetime.
12 Binary attribute; an array of host-endian u32.
15 The node's EUI-64 in the bus information block of
20 What: /sys/bus/firewire/devices/fw[0-9]+/units
23 Contact: linux1394-devel@lists.sourceforge.net
26 Read-only. Mutable during the node device's lifetime.
31 Contains space-separated tuples of specifier_id and
39 /dev/fw[0-9]+ character device files
[all …]
|
| /Documentation/media/uapi/v4l/ |
| D | pixfmt-y10b.rst | 4 .. Foundation, with no Invariant Sections, no Front-Cover Texts
5 .. and no Back-Cover Texts. A copy of the license is included at
6 .. Documentation/media/uapi/fdl-appendix.rst.
8 .. TODO: replace it to GFDL-1.1-or-later WITH no-invariant-sections
10 .. _V4L2-PIX-FMT-Y10BPACK:
16 Grey-scale image as a bit-packed array
22 This is a packed grey-scale image format with a depth of 10 bits per
23 pixel. Pixels are stored in a bit-packed array of 10bit bits per pixel,
27 **Bit-packed representation.**
32 .. flat-table::
[all …]
|
| D | subdev-formats.rst | 4 .. Foundation, with no Invariant Sections, no Front-Cover Texts
5 .. and no Back-Cover Texts. A copy of the license is included at
6 .. Documentation/media/uapi/fdl-appendix.rst.
8 .. TODO: replace it to GFDL-1.1-or-later WITH no-invariant-sections
10 .. _v4l2-mbus-format:
19 .. flat-table:: struct v4l2_mbus_framefmt
20 :header-rows: 0
21 :stub-columns: 0
24 * - __u32
25 - ``width``
[all …]
|
| D | pixfmt-y10p.rst | 4 .. Foundation, with no Invariant Sections, no Front-Cover Texts
5 .. and no Back-Cover Texts. A copy of the license is included at
6 .. Documentation/media/uapi/fdl-appendix.rst.
8 .. TODO: replace it to GFDL-1.1-or-later WITH no-invariant-sections
10 .. _V4L2-PIX-FMT-Y10P:
16 Grey-scale image as a MIPI RAW10 packed array
22 This is a packed grey-scale image format with a depth of 10 bits per
28 **Bit-packed representation.**
36 .. flat-table::
37 :header-rows: 0
[all …]
|
| D | pixfmt-sdr-pcu18be.rst | 4 .. Foundation, with no Invariant Sections, no Front-Cover Texts
5 .. and no Back-Cover Texts. A copy of the license is included at
6 .. Documentation/media/uapi/fdl-appendix.rst.
8 .. TODO: replace it to GFDL-1.1-or-later WITH no-invariant-sections
10 .. _V4L2-SDR-FMT-PCU18BE:
16 Planar complex unsigned 18-bit big endian IQ sample
22 number consist of two parts called In-phase and Quadrature (IQ). Both I
25 padded with 0. I value starts first and Q value starts at an offset
27 the 18 bits, bit 17:2 (16 bit) is data and bit 1:0 (2 bit) can be any
33 .. flat-table::
[all …]
|
| /Documentation/leds/ |
| D | leds-blinkm.rst | 5 The leds-blinkm driver supports the devices of the BlinkM family.
7 They are RGB-LED modules driven by a (AT)tiny microcontroller and
9 0x09 but this can be changed through a command. By this you could
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:
[all …]
|
| D | leds-lp55xx.rst | 8 -----------
14 Device attributes for user-space interface
33 LP5523/55231 has 9 output channels::
43 lp55xx_led #9
50 - Maximum number of channels
51 - Reset command, chip enable command
52 - Chip specific initialization
53 - Brightness control register access
54 - Setting LED output current
55 - Program memory address access for running patterns
[all …]
|
| /Documentation/devicetree/bindings/leds/ |
| D | leds-lp55xx.txt | 4 - compatible: one of
11 - reg: I2C slave address
12 - clock-mode: Input clock mode, (0: automode, 1: internal, 2: external)
15 - led-cur: Current setting at each led channel (mA x10, 0 if led is not connected)
16 - max-cur: Maximun current at each led channel.
19 - enable-gpio: GPIO attached to the chip's enable pin
20 - label: Used for naming LEDs
21 - pwr-sel: LP8501 specific property. Power selection for output channels.
22 0: D1~9 are connected to VDD
23 1: D1~6 with VDD, D7~9 with VOUT
[all …]
|
| /Documentation/devicetree/bindings/input/touchscreen/ |
| D | egalax-ts.txt | 4 - compatible: must be "eeti,egalax_ts"
5 - reg: i2c slave address
6 - interrupts: touch controller interrupt
7 - wakeup-gpios: the gpio pin to be used for waking up the controller
14 reg = <0x04>;
15 interrupt-parent = <&gpio1>;
16 interrupts = <9 2>;
17 wakeup-gpios = <&gpio1 9 0>;
|
| /Documentation/devicetree/bindings/pci/ |
| D | v3-v360epc-pci.txt | 6 - 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
18 each be exactly 256MB (0x10000000) in size.
[all …]
|
| /Documentation/core-api/ |
| D | packing.rst | 6 -----------------
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/devicetree/bindings/interrupt-controller/ |
| D | sifive,plic-1.0.0.txt | 1 SiFive Platform-Level Interrupt Controller (PLIC)
2 -------------------------------------------------
4 SiFive SOCs include an implementation of the Platform-Level Interrupt Controller
5 (PLIC) high-level specification in the RISC-V Privileged Architecture
10 in an 4 core system with 2-way SMT, you have 8 harts and probably at least two
13 Each interrupt can be enabled on per-context basis. Any context can claim
21 While the PLIC supports both edge-triggered and level-triggered interrupts,
23 specified in the PLIC device-tree binding.
25 While the RISC-V ISA doesn't specify a memory layout for the PLIC, the
26 "sifive,plic-1.0.0" device is a concrete implementation of the PLIC that
[all …]
|
| /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 <maxime.ripard@bootlin.com>
15 pattern: "^bus(@[0-9a-f]+)?$"
17 "#address-cells":
20 "#size-cells":
25 - const: allwinner,sun50i-a64-de2
[all …]
|
| /Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/ |
| D | pincfg.txt | 4 - 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:
11 0 = The pin is disabled
16 - open_drain : indicates the pin is normal or wired-OR:
18 0 = The pin is actively driven as an output
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
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | ethernet-phy.yaml | 1 # 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/networking/ |
| D | pktgen.txt | 4 ------------------------------------
6 Enable CONFIG_NET_PKTGEN to compile and build pktgen either in-kernel
15 root 129 0.3 0.0 0 0 ? SW 2003 523:20 [kpktgend_0]
16 root 130 0.3 0.0 0 0 ? SW 2003 509:50 [kpktgend_1]
29 overload type of benchmarking, as this could hurt the normal use-case.
32 # ethtool -G ethX tx 1024
41 ring-buffers for various performance reasons, and packets stalling
46 and the cleanup interval is affected by the ethtool --coalesce setting
47 of parameter "rx-usecs".
50 # ethtool -C ethX rx-usecs 30
[all …]
|
| /Documentation/devicetree/bindings/ipmi/ |
| D | npcm7xx-kcs-bmc.txt | 5 used to perform in-band IPMI communication with their host.
8 - compatible : should be one of
9 "nuvoton,npcm750-kcs-bmc"
10 - interrupts : interrupt generated by the controller
11 - kcs_chan : The KCS channel number in the controller
16 compatible = "nuvoton,npcm750-lpc-kcs", "simple-mfd", "syscon";
17 reg = <0xf0007000 0x40>;
18 reg-io-width = <1>;
20 #address-cells = <1>;
21 #size-cells = <1>;
[all …]
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | st,stm32-pinctrl.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/pinctrl/st,stm32-pinctrl.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Alexandre TORGUE <alexandre.torgue@st.com>
17 on-chip controllers onto these pads.
22 - st,stm32f429-pinctrl
23 - st,stm32f469-pinctrl
24 - st,stm32f746-pinctrl
25 - st,stm32f769-pinctrl
[all …]
|
12345678910>>...24