Searched +full:1 +full:- +full:v0 (Results 1 – 21 of 21) sorted by relevance
| /Documentation/devicetree/bindings/arm/ |
| D | psci.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> 15 processors") can be used by Linux to initiate various CPU-centric power 25 r0 => 32-bit Function ID / return value 26 {r1 - r3} => Parameters 37 - description: 41 - description: 43 const: arm,psci-0.2 [all …]
|
| D | qcom.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Stephen Boyd <sboyd@codeaurora.org> 18 Each board must specify a top-level board compatible string with the following 21 compatible = "qcom,<SoC>[-<soc_version>][-<foundry_id>]-<board>[/<subtype>][-<board_version>]" 59 "qcom,msm8916-v1-cdp-pm8916-v2.1" 61 A CDP board with an msm8916 SoC, version 1 paired with a pm8916 PMIC of version 64 "qcom,apq8074-v2.0-2-dragonboard/1-v0.1" 66 A dragonboard board v0.1 of subtype 1 with an apq8074 SoC version 2, made in [all …]
|
| /Documentation/devicetree/bindings/spi/ |
| D | spi-sifive.txt | 2 ------------------------------------------ 5 - compatible : Should be "sifive,<chip>-spi" and "sifive,spi<version>". 7 "sifive,fu540-c000-spi" for the SiFive SPI v0 as integrated 9 SPI v0 IP block with no chip integration tweaks. 10 Please refer to sifive-blocks-ip-versioning.txt for details 11 - reg : Physical base address and size of SPI registers map 13 - interrupts : Must contain one entry 14 - interrupt-parent : Must be core interrupt controller 15 - clocks : Must reference the frequency given to the controller 16 - #address-cells : Must be '1', indicating which CS to use [all …]
|
| /Documentation/virt/kvm/arm/ |
| D | psci.txt | 3 and power-off to the guest. 16 pseudo-registers" that can be manipulated using the GET/SET_ONE_REG 24 - Only valid if the vcpu has the KVM_ARM_VCPU_PSCI_0_2 feature set 26 - Returns the current PSCI version on GET_ONE_REG (defaulting to the 27 highest PSCI version implemented by KVM and compatible with v0.2) 28 - Allows any PSCI version implemented by KVM and compatible with 29 v0.2 to be set with SET_ONE_REG 30 - Affects the whole VM (even if the register view is per-vcpu) 33 Holds the state of the firmware support to mitigate CVE-2017-5715, as 35 under SMCCC_ARCH_WORKAROUND_1 in [1]. [all …]
|
| /Documentation/networking/ |
| D | framerelay.txt | 7 Each DLCI is a point-to-point link between your machine and a remote one. 9 net-tools archives is 'dlcicfg'. This program will communicate with the 19 With this initial offering, only 1 FRAD driver is available. With many thanks 25 Configuration of the FRAD makes use of another net-tools program, 'fradcfg'. 35 the net-tools distribution. They can be found at ftp.invlogic.com, in 37 use 'cd linux'. v0.10 is for use on pre-2.0.3 and earlier, v0.15 is for 38 pre-2.0.4 and later.
|
| D | ip_dynaddr.txt | 1 IP dynamic address hack-port v0.03 5 It is implemented for TCP diald-box connections(1) and IP_MASQuerading(2). 8 1) Socket (and packet) source address is rewritten ON RETRANSMISSIONS 9 while in SYN_SENT state (diald-box processes). 10 2) Out-bounded MASQueraded source address changes ON OUTPUT (when 21 # echo 1 > /proc/sys/net/ipv4/ip_dynaddr 29 -- Juanjo <jjciarla@raiz.uncu.edu.ar>
|
| /Documentation/virt/kvm/ |
| D | hypercalls.txt | 4 KVM Hypercalls have a three-byte sequence of either the vmcall or the vmmcall 14 R2-R7 are used for parameters 1-6. In addition, R1 is used for hypercall 21 refer to Documentation/virt/kvm/s390-diag.txt. 24 It uses R3-R10 and hypercall number in R11. R4-R11 are used as output registers. 27 KVM hypercalls uses 4 byte opcode, that are patched with 'hypercall-instructions' 29 For more information refer to Documentation/virt/kvm/ppc-pv.txt 33 number in $2 (v0). Up to four arguments may be placed in $4-$7 (a0-a3) and 34 the return value is placed in $2 (v0). 39 1. Hypercall name. 44 1. KVM_HC_VAPIC_POLL_IRQ [all …]
|
| D | api.txt | 1 The Definitive KVM (Kernel-based Virtual Machine) API Documentation 4 1. General description 5 ---------------------- 10 - System ioctls: These query and set global attributes which affect the 14 - VM ioctls: These query and set attributes that affect an entire virtual 21 - vcpu ioctls: These query and set attributes that control the operation 29 - device ioctls: These query and set attributes that control the operation 36 ------------------- 73 ------------- 77 facility that allows backward-compatible extensions to the API to be [all …]
|
| /Documentation/arm64/ |
| D | sve.rst | 20 1. General 21 ----------- 24 tracked per-thread. 28 instructions and registers, and the Linux-specific system interfaces 54 cpu-feature-registers.txt for details. 63 an endianness-invariant layout, with bits [(8 * i + 7) : (8 * i)] encoded at 68 Beware that on big-endian systems this results in a different byte order than 69 for the FPSIMD V-registers, which are stored as single host-endian 128-bit 70 values, with bits [(127 - 8 * i) : (120 - 8 * i)] of the register encoded at 75 ----------------------------- [all …]
|
| /Documentation/ |
| D | lzo.txt | 26 - a distance when copying data from the dictionary (past output buffer) 27 - a length (number of bytes to copy from dictionary) 28 - the number of literals to copy, which is retained in variable "state" 43 around 255:1). The variable length encoding using #bits is always the same:: 45 length = byte & ((1 << #bits) - 1) 47 length = ((1 << #bits) - 1) 49 length += first-non-zero-byte 57 forming a little-endian 16-bit quantity (marked LE16 below). 59 After any instruction except the large literal copy, 0, 1, 2 or 3 literals 84 1: LZO-RLE [all …]
|
| /Documentation/input/joydev/ |
| D | joystick-api.rst | 1 .. _joystick-api: 7 :Author: Ragnar Hojland Espinosa <ragnar@macula.net> - 7 Aug 1998 18 driver now reports only any changes of its state. See joystick-api.txt, 23 For backward compatibility the old (v0.x) interface is still included. 65 ------------- 86 --------------- 95 1st Axis X 0 96 1st Axis Y 1 108 -------------- 110 For an axis, ``value`` is a signed integer between -32767 and +32767 [all …]
|
| /Documentation/admin-guide/auxdisplay/ |
| D | cfag12864b.rst | 7 :Date: 2006-10-27 13 1. DRIVER INFORMATION 18 1. Driver Information 19 --------------------- 25 --------------------- 40 :Data size: 1 byte each address 41 :Memory size: 2 * 8 * 64 * 1 = 1024 bytes = 1 Kbyte 45 --------- 55 Strobe ( 1)------------------------------(17) Enable 56 Data 0 ( 2)------------------------------( 4) Data 0 [all …]
|
| /Documentation/target/ |
| D | tcm_mod_builder.py | 2 # The TCM v4 multi-protocol fabric module generation script for drivers/target/$NEW_MOD 5 # Copyright (c) 2010 Linux-iSCSI.org 24 sys.exit(1) 29 return 1 50 buf = "#define " + fabric_mod_name.upper() + "_VERSION \"v0.1\"\n" 94 buf = "#define " + fabric_mod_name.upper() + "_VERSION \"v0.1\"\n" 137 buf = "#define " + fabric_mod_name.upper() + "_VERSION \"v0.1\"\n" 176 sys.exit(1) 222 buf += " return ERR_PTR(-EINVAL);\n" 224 buf += " return ERR_PTR(-EINVAL);\n\n" [all …]
|
| /Documentation/usb/ |
| D | acm.rst | 2 Linux ACM driver v0.16 23 Temple Place, Suite 330, Boston, MA 02111-1307 USA 25 Should you need to contact me, the author, you can do so either by e-mail - 32 1. Usage 34 The drivers/usb/class/cdc-acm.c drivers works with USB modems and USB ISDN terminal 40 - 3Com OfficeConnect 56k 41 - 3Com Voice FaxModem Pro 42 - 3Com Sportster 43 - MultiTech MultiModem 56k 44 - Zoom 2986L FaxModem [all …]
|
| /Documentation/input/ |
| D | input.rst | 7 :Copyright: |copy| 1999-2001 Vojtech Pavlik <vojtech@ucw.cz> - Sponsored by SuSE 18 loaded before any other of the input modules - it serves as a way of 22 -------------- 28 -------------- 31 via various interfaces - keystrokes to the kernel, mouse movements via 51 crw-r--r-- 1 root root 13, 63 Mar 28 22:45 mice 61 XFree to this device to use it - GPM should be called like:: 63 gpm -t ps2 -m /dev/input/mice 79 -------------- 82 in-kernel consumers, as needed. [all …]
|
| /Documentation/i2c/busses/ |
| D | i2c-parport.rst | 2 Kernel driver i2c-parport 7 This is a unified driver for several i2c-over-parallel-port adapters, 11 * i2c-philips-par 12 * i2c-elv 13 * i2c-velleman 14 * video/i2c-parport 20 * (type=1) home brew teletext adapter 25 * (type=6) Barco LPT->DVI (K5800236) adapter 27 * (type=8) VCT-jig 42 ------------------------- [all …]
|
| /Documentation/media/dvb-drivers/ |
| D | dvb-usb.rst | 1 .. SPDX-License-Identifier: GPL-2.0 3 Idea behind the dvb-usb-framework 11 #) **deprecated:** Newer DVB USB drivers should use the dvb-usb-v2 framework. 13 In March 2005 I got the new Twinhan USB2.0 DVB-T device. They provided specs 18 dibusb-driver would be a complete mess afterwards. So I decided to do it in a 19 different way: With the help of a dvb-usb-framework. 23 - Transport Stream URB handling in conjunction with dvb-demux-feed-control 25 - registering the device for the DVB-API 26 - registering an I2C-adapter if applicable 27 - remote-control/input-device handling [all …]
|
| /Documentation/input/devices/ |
| D | joystick-parport.rst | 3 .. _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 69 (pin 9) -----> Power 77 (pin 9) ----|>|-------+------> Power 79 (pin 8) ----|>|-------+ [all …]
|
| /Documentation/admin-guide/ |
| D | devices.txt | 1 0 Unnamed devices (e.g. non-device mounts) 5 1 char Memory devices 6 1 = /dev/mem Physical memory access 11 6 = /dev/core OBSOLETE - replaced by /proc/kcore 18 12 = /dev/oldmem OBSOLETE - replaced by /proc/vmcore 20 1 block RAM disk 22 1 = /dev/ram1 Second RAM disk 26 Older kernels had /dev/ramdisk (1, 1) here. 31 2 char Pseudo-TTY masters 33 1 = /dev/ptyp1 Second PTY master [all …]
|
| /Documentation/media/v4l-drivers/ |
| D | cx2341x.rst | 1 .. SPDX-License-Identifier: GPL-2.0 7 ----------------------- 12 .. note:: the memory long words are little-endian ('intel format'). 21 .. code-block:: none 23 ivtvctl -O min=0x02000000,max=0x020000ff 26 register space :-). 35 .. code-block:: none 37 0x00000000-0x00ffffff Encoder memory space 38 0x00000000-0x0003ffff Encode.rom 39 ???-??? MPEG buffer(s) [all …]
|
| /Documentation/RCU/ |
| D | RTFP.txt | 4 This document describes RCU-related publications, and is followed by 19 with short-lived threads, such as the K42 research operating system. 20 However, Linux has long-lived tasks, so more is needed. 23 serialization, which is an RCU-like mechanism that relies on the presence 27 that these overheads were not so expensive in the mid-80s. Nonetheless, 28 passive serialization appears to be the first deferred-destruction 30 has lapsed, so this approach may be used in non-GPL software, if desired. 34 In 1987, Rashid et al. described lazy TLB-flush [RichardRashid87a]. 36 this paper helped inspire the update-side batching used in the later 38 a description of Argus that noted that use of out-of-date values can [all …]
|