Searched +full:x +full:- +full:rp (Results 1 – 6 of 6) sorted by relevance
| /Documentation/devicetree/bindings/media/ |
| D | video-interface-devices.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/media/video-interface-devices.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Jacopo Mondi <jacopo@jmondi.org> 11 - Sakari Ailus <sakari.ailus@linux.intel.com> 14 flash-leds: 15 $ref: /schemas/types.yaml#/definitions/phandle-array 17 An array of phandles, each referring to a flash LED, a sub-node of the LED 20 lens-focus: [all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-devices-mapping | 6 each dieX file (where X is die number) holds "Segment:Root Bus" 9 For example, on 4-die Xeon platform with up to 6 IIO stacks per 14 -r--r--r-- /sys/devices/uncore_iio_0/die0 15 -r--r--r-- /sys/devices/uncore_iio_0/die1 16 -r--r--r-- /sys/devices/uncore_iio_0/die2 17 -r--r--r-- /sys/devices/uncore_iio_0/die3 31 IIO PMU 0 on die 0 belongs to PCI RP on bus 0x00, domain 0x0000 32 IIO PMU 0 on die 1 belongs to PCI RP on bus 0x40, domain 0x0000 33 IIO PMU 0 on die 2 belongs to PCI RP on bus 0x80, domain 0x0000 34 IIO PMU 0 on die 3 belongs to PCI RP on bus 0xc0, domain 0x0000 [all …]
|
| /Documentation/driver-api/mtd/ |
| D | spi-nor.rst | 6 ----------------------------------- 11 standard set of internal read-only parameter tables. 17 on its SFDP data. All one has to do is to specify the "jedec,spi-nor" 28 ----------------------------- 31 section, after the ``---`` marker. 36 This flash is populated on the X board and was tested at Y 41 root@1:~# cat /sys/bus/spi/devices/spi0.0/spi-nor/partname 43 root@1:~# cat /sys/bus/spi/devices/spi0.0/spi-nor/jedec_id 45 root@1:~# cat /sys/bus/spi/devices/spi0.0/spi-nor/manufacturer 47 root@1:~# xxd -p /sys/bus/spi/devices/spi0.0/spi-nor/sfdp [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 …]
|
| D | whatisRCU.rst | 3 What is RCU? -- "Read, Copy, Update" 21 …ries: Fundamentals https://www.linuxfoundation.org/webinars/unraveling-rcu-usage-mysteries 22 …Cases https://www.linuxfoundation.org/webinars/unraveling-rcu-usage-mysteries-additional-use-cases 28 during the 2.5 development effort that is optimized for read-mostly 47 :ref:`6. ANALOGY WITH READER-WRITER LOCKING <6_whatisRCU>` 67 everything, feel free to read the whole thing -- but if you are really 69 never need this document anyway. ;-) 74 ---------------- 103 b. Wait for all previous readers to complete their RCU read-side 112 use much lighter-weight synchronization, in some cases, absolutely no [all …]
|
| /Documentation/networking/ |
| D | arcnet-hardware.rst | 1 .. SPDX-License-Identifier: GPL-2.0 11 2) This file is no longer Linux-specific. It should probably be moved out 17 e-mail apenwarr@worldvisions.ca with any settings for your particular card, 39 There are two "types" of ARCnet - STAR topology and BUS topology. This 46 well-designed standard. It uses something called "modified token passing" 47 which makes it completely incompatible with so-called "Token Ring" cards, 63 programming interface also means that when high-performance hardware 73 although they are generally kept down to the Ethernet-style 1500 bytes. 91 - Avery Pennraun <apenwarr@worldvisions.ca> 92 - Stephen A. Wood <saw@hallc1.cebaf.gov> [all …]
|