| /Documentation/userspace-api/media/v4l/ |
| D | pixfmt-z16.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _V4L2-PIX-FMT-Z16:
10 16-bit depth data with distance values at each pixel
16 This is a 16-bit format, representing depth data. Each pixel is a
19 is stored in a 16-bit word in the little endian byte order.
27 .. flat-table::
28 :header-rows: 0
29 :stub-columns: 0
31 * - start + 0:
32 - Z\ :sub:`00low`
[all …]
|
| /Documentation/arch/arm/nwfpe/ |
| D | netwinder-fpe.rst | 14 {P|M|Z} = {round to +infinity,round to -infinity,round to zero},
20 ------------------------------------------------------------
22 LDF/STF - load and store floating
30 LFM/SFM - load and store multiple floating
47 ----------------------------------------------------------------
51 FLT{cond}<S,D,E>{P,M,Z} Fn, Rd Convert integer to floating point
52 FIX{cond}{P,M,Z} Rd, Fn Convert floating point to integer
76 ---------------------------------------------------
80 ADF{cond}<S|D|E>{P,M,Z} Fd, Fn, <Fm,#value> - add
81 SUF{cond}<S|D|E>{P,M,Z} Fd, Fn, <Fm,#value> - subtract
[all …]
|
| D | todo.rst | 6 POW{cond}<S|D|E>{P,M,Z} Fd, Fn, <Fm,#value> - power
7 RPW{cond}<S|D|E>{P,M,Z} Fd, Fn, <Fm,#value> - reverse power
8 POL{cond}<S|D|E>{P,M,Z} Fd, Fn, <Fm,#value> - polar angle (arctan2)
10 LOG{cond}<S|D|E>{P,M,Z} Fd, <Fm,#value> - logarithm to base 10
11 LGN{cond}<S|D|E>{P,M,Z} Fd, <Fm,#value> - logarithm to base e
12 EXP{cond}<S|D|E>{P,M,Z} Fd, <Fm,#value> - exponent
13 SIN{cond}<S|D|E>{P,M,Z} Fd, <Fm,#value> - sine
14 COS{cond}<S|D|E>{P,M,Z} Fd, <Fm,#value> - cosine
15 TAN{cond}<S|D|E>{P,M,Z} Fd, <Fm,#value> - tangent
16 ASN{cond}<S|D|E>{P,M,Z} Fd, <Fm,#value> - arcsine
[all …]
|
| D | notes.rst | 4 There seems to be a problem with exp(double) and our emulator. I haven't
10 registers f4-f7 to be preserved over a function call. The compiler quite
11 often uses an stfe instruction to save f4 on the stack upon entry to a
14 I was looking at some code, that calculated a double result, stored it in f4
15 then made a function call. Upon return from the function call the number in
18 This is a side effect of the stfe instruction. The double in f4 had to be
21 result from the function call and f4 were used in a multiplication. If the
22 emulator sees a multiply of a double and extended, it promotes the double to
27 double x, y, z;
28 z = log(x)/log(y);
[all …]
|
| /Documentation/devicetree/bindings/iio/accel/ |
| D | lis302.txt | 3 This device is matched via its bus drivers, and has a number of properties
8 - compatible: should be set to "st,lis3lv02d-spi"
9 - reg: the chipselect index
10 - spi-max-frequency: maximal bus speed, should be set to 1000000 unless
12 - interrupts: the interrupt generated by the device
15 - compatible: should be set to "st,lis3lv02d"
16 - reg: i2c slave address
17 - Vdd-supply: The input supply for Vdd
18 - Vdd_IO-supply: The input supply for Vdd_IO
23 - st,click-single-{x,y,z}: if present, tells the device to issue an
[all …]
|
| /Documentation/devicetree/bindings/iio/ |
| D | mount-matrix.txt | 2 * is the definition of +/- values practical or counterintuitive?
5 * should we have HOWTO engineer a correct matrix for a new device (without comparing to a different…
12 The mounting matrix is a device tree property used to orient any device
13 that produce three-dimensional data in relation to the world where it is
17 reference into the device frame of reference using a translation matrix as
20 The typical usecase is that where a component has an internal representation
21 of the (x,y,z) triplets, such as different registers to read these coordinates,
22 and thus implying that the component should be mounted in a certain orientation
25 For example a device with some kind of screen, where the user is supposed to
28 reference to (x,y,z) orientation, with (x,y) corresponding to these axes on the
[all …]
|
| /Documentation/driver-api/ |
| D | zorro.rst | 5 :Author: Written by Geert Uytterhoeven <geert@linux-m68k.org>
10 ------------
13 AutoConfig(tm), it's 100% Plug-and-Play.
17 - The Zorro II address space is 24-bit and lies within the first 16 MB of the
20 - Zorro III is a 32-bit extension of Zorro II, which is backwards compatible
25 -------------------------
27 Zorro devices are found by calling ``zorro_find_device()``, which returns a
28 pointer to the ``next`` Zorro device with the specified Zorro ID. A probe loop
31 struct zorro_dev *z = NULL;
33 while ((z = zorro_find_device(ZORRO_PROD_xxx, z))) {
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-ata | 3 Provide a place in sysfs for storing the ATA topology of the
8 -------------------------------
10 For each port, a directory ataX is created where X is the ata_port_id of the
20 nr_pmp_links: (RO) If a SATA Port Multiplier (PM) is
35 persistent links in /dev/disk/by-path.
38 -------------------------------
40 Behind each port, there is a ata_link. If there is a SATA PM in the topology, 15
43 If a link is behind a port, the directory name is linkX, where X is ata_port_id
44 of the port. If a link is behind a PM, its name is linkX.Y where X is
65 ---------------------------------
[all …]
|
| D | sysfs-devices-platform-trackpoint | 4 Contact: linux-input@vger.kernel.org
11 Contact: linux-input@vger.kernel.org
19 Contact: linux-input@vger.kernel.org
21 (RW) Backup range for z-axis press.
26 Contact: linux-input@vger.kernel.org
29 z-axis pressed.
34 Contact: linux-input@vger.kernel.org
41 Contact: linux-input@vger.kernel.org
48 Contact: linux-input@vger.kernel.org
50 (RW) Minimum value for z-axis force required to trigger a press
[all …]
|
| D | sysfs-platform-wilco-ec | 5 Boot on AC is a policy which makes the device boot from S5
7 want to run their device headless or with a dock.
16 Output will a MM/DD/YY string.
23 Output will a version string be similar to the example below:
31 Output will a version string be similar to the example below:
38 Control the USB PowerShare Policy. USB PowerShare is a policy
40 (marked with a small lightning bolt or battery icon) when in
43 - In S0, the port will always provide power.
44 - In S0ix, if usb_charge is enabled, then power will be
47 - In S5, if usb_charge is enabled, then power will be supplied
[all …]
|
| /Documentation/litmus-tests/rcu/ |
| D | RCU+sync+free.litmus | 6 * This litmus test demonstrates that an RCU reader can never see a write that
7 * follows a grace period, if it did not see writes that precede that grace
10 * This is a typical pattern of RCU usage, where the write before the grace
11 * period assigns a pointer, and the writes following the grace period destroy
14 * This is one implication of the RCU grace-period guarantee, which says (among
15 * other things) that an RCU read-side critical section cannot span a grace period.
21 int z = 1;
24 P0(int *x, int *z, int **y)
35 P1(int *x, int *z, int **y)
37 rcu_assign_pointer(*y, z);
|
| /Documentation/devicetree/bindings/sound/ |
| D | ti,tas5086.txt | 1 Texas Instruments TAS5086 6-channel PWM Processor
5 - compatible: Should contain "ti,tas5086".
6 - reg: The i2c address. Should contain <0x1b>.
10 - reset-gpio: A GPIO spec to define which pin is connected to the
12 assert a hardware reset at probe time.
14 - ti,charge-period: This property should contain the time in microseconds
15 that closely matches the external single-ended
16 split-capacitor charge period. The hardware chip
23 - ti,mid-z-channel-X: Boolean properties, X being a number from 1 to 6.
24 If given, channel X will start with the Mid-Z start
[all …]
|
| D | tlv320adcx140.yaml | 1 # SPDX-License-Identifier: (GPL-2.0+ OR BSD-2-Clause)
4 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: Texas Instruments TLV320ADCX140 Quad Channel Analog-to-Digital Converter
11 - Andrew Davis <afd@ti.com>
14 The TLV320ADCX140 are multichannel (4-ch analog recording or 8-ch digital
15 PDM microphones recording), high-performance audio, analog-to-digital
17 family supports line and microphone Inputs, and offers a programmable
28 - ti,tlv320adc3140
29 - ti,tlv320adc5140
[all …]
|
| D | cirrus,cs35l41.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - david.rhodes@cirrus.com
13 CS35L41 is a boosted mono Class D amplifier with DSP
19 - cirrus,cs35l40
20 - cirrus,cs35l41
28 '#sound-dai-cells':
33 reset-gpios:
36 VA-supply:
[all …]
|
| /Documentation/arch/s390/ |
| D | monreader.rst | 2 Linux API for read access to z/VM Monitor Records
5 Date : 2004-Nov-26
14 This item delivers a new Linux API in the form of a misc char device that is
15 usable from user space and allows read access to the z/VM Monitor Records
16 collected by the `*MONITOR` System Service of z/VM.
21 The z/VM guest on which you want to access this API needs to be configured in
25 This item will use the IUCV device driver to access the z/VM services, so you
26 need a kernel with IUCV support. You also need z/VM version 4.4 or 5.1.
33 See also "CP Command and Utility Reference" (SC24-6081-00) for more information
35 and Administration" (SC24-6116-00) for more information on DCSSes.
[all …]
|
| /Documentation/devicetree/bindings/iio/magnetometer/ |
| D | ti,tmag5273.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: TI TMAG5273 Low-Power Linear 3D Hall-Effect Sensor
10 - Gerald Loacker <gerald.loacker@wolfvision.net>
13 The TI TMAG5273 is a low-power linear 3D Hall-effect sensor. This device
14 integrates three independent Hall-effect sensors in the X, Y, and Z axes.
19 on-axis and off-axis angle measurement topologies. The angle calculation is
20 performed using two user-selected magnetic axes.
29 "#io-channel-cells":
[all …]
|
| /Documentation/misc-devices/ |
| D | lis3lv02d.rst | 12 - Yan Burman <burman.yan@gmail.com>
13 - Eric Piel <eric.piel@tremplin-utc.net>
17 -----------
31 - 3D position that the accelerometer reports. Format: "(x,y,z)"
33 - read reports the sampling rate of the accelerometer device in HZ.
37 - performs selftest for the chip as specified by chip manufacturer.
40 the laptop to act as a pinball machine-esque joystick. Joystick device can be
42 By default output values are scaled between -32768 .. 32767. In joystick raw
53 to allow adjustment of the limits without a change to the actual driver.
54 Seltest returns either "OK x y z" or "FAIL x y z" where x, y and z are
[all …]
|
| /Documentation/features/scripts/ |
| D | features-refresh.sh | 5 for F_FILE in Documentation/features/*/*/arch-support.txt; do
6 F=$(grep "^# Kconfig:" "$F_FILE" | cut -c26-)
9 # Each feature F is identified by a pair (O, K), where 'O' can
17 K=$(echo $F | sed -e 's/^!//g')
21 # F := (O, K) is 'valid' iff there is a Kconfig file (for some
30 # 2) K does not exist (e.g., it was renamed/mis-typed);
46 K_FILES=$(find $ARCH_DIR -name "Kconfig*")
48 if [ ! -z "$K_GREP" ]; then
54 printf "WARNING: '%s' is not a valid Kconfig\n" "$F"
59 echo " -----------------------" >> $T_FILE
[all …]
|
| /Documentation/riscv/ |
| D | uabi.rst | 1 .. SPDX-License-Identifier: GPL-2.0
3 RISC-V Linux User ABI
7 ------------------------------------
14 #. Single-letter extensions come first, in canonical order.
17 #. All multi-letter extensions will be separated from other extensions by an
20 #. Additional standard extensions (starting with 'Z') will be sorted after
21 single-letter extensions and before any higher-privileged extensions.
23 #. For additional standard extensions, the first letter following the 'Z'
25 extension category. If multiple 'Z' extensions are named, they will be
27 alphabetically within a category.
[all …]
|
| /Documentation/translations/zh_CN/core-api/ |
| D | this_cpu_ops.rst | 1 .. SPDX-License-Identifier: GPL-2.0+
3 .. include:: ../disclaimer-zh_CN.rst
5 :Original: Documentation/core-api/this_cpu_ops.rst
31 读取-修改-写入操作特别值得关注。通常处理器具有特殊的低延迟指令，可以在没有典型同
64 ----------------------
73 int z;
75 z = this_cpu_read(x);
114 ----------
129 -----------------
153 ---------------------
[all …]
|
| /Documentation/devicetree/bindings/net/wireless/ |
| D | brcm,bcm4329-fmac.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/net/wireless/brcm,bcm4329-fmac.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Arend van Spriel <arend@broadcom.com>
15 These chips also have a Bluetooth portion described in a separate
19 - $ref: ieee80211.yaml#
24 - items:
25 - enum:
26 - brcm,bcm43143-fmac
[all …]
|
| /Documentation/hwmon/ |
| D | pmbus.rst | 12 Addresses scanned: -
23 Addresses scanned: -
27 https://www.onsemi.com/pub_link/Collateral/ADP4000-D.PDF
29 https://www.onsemi.com/pub_link/Collateral/NCP4200-D.PDF
31 https://www.onsemi.com/pub_link/Collateral/JUNE%202009-%20REV.%200.PDF
37 Addresses scanned: -
55 Addresses scanned: -
73 Addresses scanned: -
83 Addresses scanned: -
85 Datasheet: n.a.
[all …]
|
| /Documentation/arch/m68k/ |
| D | buddha-driver.rst | 8 ------------------------------------------------------------------------
11 Buddha-part of the Catweasel Zorro-II version
17 a Linux kernel configure the card), look at the Commodore
21 product number: 0 (42 for Catweasel Z-II)
23 Rom-vector: $1000
25 The card should be a Z-II board, size 64K, not for freemem
26 list, Rom-Vektor is valid, no second Autoconfig-board on the
30 as the Amiga Kickstart does: The lower nibble of the 8-Bit
31 address is written to $4a, then the whole Byte is written to
32 $48, while it doesn't matter how often you're writing to $4a
[all …]
|
| /Documentation/process/ |
| D | applying-patches.rst | 14 A frequently asked question on the Linux Kernel Mailing List is how to apply
15 a patch to the kernel or, more specifically, what base kernel a patch for
19 In addition to explaining how to apply and revert patches, a brief
24 What is a patch?
27 A patch is a small text document containing a delta of changes between two
28 different versions of a source tree. Patches are created with the ``diff``
31 To correctly apply a patch you need to know what base it was generated from
37 How do I apply or revert a patch?
40 You apply a patch with the ``patch`` program. The patch program reads a diff
48 names like "a/" and "b/").
[all …]
|
| /Documentation/translations/zh_CN/dev-tools/ |
| D | gcov.rst | 1 .. include:: ../disclaimer-zh_CN.rst
3 :Original: Documentation/dev-tools/gcov.rst
11 以通过gcov的 ``-o`` 选项（如下示例）获得指定文件的代码运行覆盖率统计数据
14 # cd /tmp/linux-out
15 # gcov -o /sys/kernel/debug/gcov/tmp/linux-out/kernel spinlock.c
33 ----
50 mount -t debugfs none /sys/kernel/debug
54 ------
59 - 单独统计单个文件（例如main.o）::
63 - 单独统计某一个路径::
[all …]
|