Searched +full:2 +full:a (Results 1 – 25 of 1340) sorted by relevance
12345678910>>...54
/Documentation/userspace-api/media/v4l/ |
D | pixfmt-rgb.rst | 14 These are all packed-pixel formats, meaning all the data for a pixel lie 21 \setlength{\tabcolsep}{2pt} 27 :header-rows: 2 34 - :cspan:`7` Byte 2 43 - 2 52 - 2 61 - 2 70 - 2 78 - r\ :sub:`2` 81 - g\ :sub:`2` [all …]
|
D | pixfmt-packed-yuv.rst | 20 \setlength{\tabcolsep}{2pt} 27 :header-rows: 2 37 - :cspan:`7` Byte 2 48 - 2 57 - 2 66 - 2 75 - 2 85 - Cb\ :sub:`2` 89 - Cr\ :sub:`2` 93 - a\ :sub:`3` [all …]
|
/Documentation/filesystems/spufs/ |
D | spufs.rst | 20 The file system provides a name space similar to posix shared memory or 22 can use spu_create(2) to establish SPU contexts in the spufs root. 24 Every SPU context is represented by a directory containing a predefined 44 tem calls like read(2) or write(2), but often support only a subset of 49 All files that support the read(2) operation also support readv(2) and 50 all files that support the write(2) operation also support writev(2). 51 All files support the access(2) and stat(2) family of operations, but 55 All files support the chmod(2)/fchmod(2) and chown(2)/fchown(2) opera- 64 accessed like a regular shared memory file and contains both code and 68 read(2), pread(2), write(2), pwrite(2), lseek(2) [all …]
|
/Documentation/admin-guide/device-mapper/ |
D | dm-service-time.rst | 5 dm-service-time is a path selector module for device-mapper targets, 6 which selects a path with the shortest estimated service time for 10 of in-flight I/Os on a path with the performance value of the path. 11 The performance value is a relative throughput value among all paths 12 in a path-group, and it can be specified as a table argument. 30 other paths having a positive value are available. 36 'A' if the path is active, 'F' if the path is failed. 51 Basically, dm-service-time selects a path having minimum service time 62 2. If the paths have the same 'in-flight-size', skip the division 78 In case that 2 paths (sda and sdb) are used with repeat_count == 128 [all …]
|
D | switch.rst | 5 The device-mapper switch target creates a device that supports an 6 arbitrary mapping of fixed-size regions of I/O across a fixed set of 8 dynamically by sending the target a message. 10 It maps I/O to underlying block devices efficiently when there is a large 12 that would allow for a compact representation of the mapping such as 18 Dell EqualLogic and some other iSCSI storage arrays use a distributed 20 consists of a number of distinct storage arrays ("members") each having 21 independent controllers, disk storage and network adapters. When a LUN 24 The storage group exposes a single target discovery portal, no matter 26 session is connected to an eth port on a single member. Data to a LUN [all …]
|
/Documentation/devicetree/bindings/clock/ |
D | brcm,iproc-clocks.txt | 11 Required properties for a PLL and its leaf clocks: 14 Should have a value of the form "brcm,<soc>-<pll>". For example, GENPLL on 15 Cygnus has a compatible string of "brcm,cygnus-genpll" 18 Have a value of <1> since there are more than 1 leaf clock of a given PLL 26 onboard crystal with a fixed rate 50 ASIU clocks are a special case. These clocks are derived directly from the 54 Should have a value of the form "brcm,<soc>-asiu-clk". For example, ASIU 55 clocks for Cygnus have a compatible string of "brcm,cygnus-asiu-clk" 58 Have a value of <1> since there are more than 1 ASIU clocks 103 crystal N/A N/A N/A [all …]
|
/Documentation/filesystems/ext4/ |
D | blocks.rst | 6 ext4 allocates storage space in units of “blocks”. A block is a group of 8 integral power of 2. Blocks are in turn grouped into larger units called 11 page size (i.e. 64KiB blocks on a i386 which only has 4KiB memory 12 pages). By default a filesystem can contain 2^32 blocks; if the '64bit' 13 feature is enabled, then a filesystem can have 2^64 blocks. The location 25 - 2KiB 29 - 2^32 30 - 2^32 31 - 2^32 32 - 2^32 [all …]
|
/Documentation/filesystems/ |
D | configfs.rst | 16 configfs is a ram-based filesystem that provides the converse of 17 sysfs's functionality. Where sysfs is a filesystem-based view of 18 kernel objects, configfs is a filesystem-based manager of kernel 21 With sysfs, an object is created in kernel (for example, when a device 24 readdir(3)/read(2). It may allow some attributes to be modified via 25 write(2). The important point is that the object is created and 27 representation, and sysfs is merely a window on all this. 29 A configfs config_item is created via an explicit userspace operation: 30 mkdir(2). It is destroyed via rmdir(2). The attributes appear at 31 mkdir(2) time, and can be read or modified via read(2) and write(2). [all …]
|
D | hpfs.rst | 33 - there is a list of text extensions (I thing it's better to not convert 49 When to mark filesystem dirty so that OS/2 checks it. 57 one hour more, than under os/2, use timeshift=-3600. 63 As in OS/2, filenames are case insensitive. However, shell thinks that names 64 are case sensitive, so for example when you create a file FOO, you can use 70 OS/2 ignores dots and spaces at the end of file name, so this driver does as 71 well. If you create 'a. ...', the file 'a' will be created, but you can still 72 access it under names 'a.', 'a..', 'a . . . ' etc. 78 On HPFS partitions, OS/2 can associate to each file a special information called 81 variable length. OS/2 stores window and icon positions and file types there. So [all …]
|
D | dlmfs.rst | 8 A minimal DLM userspace interface implemented via a virtual file 30 DLM implementations should not be a major issue. 48 place. Please download ocfs2-tools from the above url and configure a 51 You'll want to start heartbeating on a volume which all the nodes in 69 system calls and presents a more traditional locking api. 71 dlmfs handles lock caching automatically for the user, so a lock 77 Also supported is a Trylock operation. 82 Lock value blocks can be read and written to a resource via read(2) 83 and write(2) against the fd obtained via your open(2) call. The 88 mkdir(2) signals dlmfs to join a domain (which will have the same name [all …]
|
/Documentation/gpu/ |
D | afbc.rst | 7 AFBC is a proprietary lossless image compression protocol and format. 21 AFBC streams can contain several components - where a component 22 corresponds to a color channel (i.e. R, G, B, X, A, Y, Cb, Cr). 33 * Component 2: B 44 * Component 2: B(8) 45 * Component 3: A(8) 51 * Component 2: B(8) 56 * Component 1: Cb(8, 2x1 subsampled) 57 * Component 2: Cr(8, 2x1 subsampled) 67 * Component 2: B(8) [all …]
|
/Documentation/networking/ |
D | j1939.rst | 10 SAE J1939 defines a higher layer protocol on CAN. It implements a more 13 J1939 on the application level, like MilCAN A, NMEA2000, and especially 16 results in a maximum packet size of ((2 ^ 24) - 1) * 7 bytes == 111 MiB. 31 sockets, we found some reasons to justify a kernel implementation for the 34 * **Addressing:** when a process on an ECU communicates via J1939, it should 44 negotiation. Putting this functionality in the kernel eliminates it as a 46 results in a consistent J1939 bus with proper addressing. 52 properly and eliminates the serialization (synchronization) as a requirement 61 Since such a library does not communicate with the in-kernel implementation, care 63 cannot share ECU addresses. A single ECU (or virtual ECU) address is used by [all …]
|
/Documentation/driver-api/media/ |
D | csi2.rst | 5 MIPI CSI-2 8 CSI-2 is a data bus intended for transferring images from cameras to 17 be used for CSI-2 interfaces. 22 CSI-2 transmitter, such as a sensor or a TV tuner, drivers need to 23 provide the CSI-2 receiver with information on the CSI-2 bus 28 CSI-2 transmitter. 39 pixel_rate = link_freq * 2 * nr_of_lanes / bits_per_sample 51 - Number of data lanes used on the CSI-2 link. This can 53 * - 2 58 The transmitter drivers must, if possible, configure the CSI-2 [all …]
|
/Documentation/input/devices/ |
D | elantech.rst | 9 Version 2 (EeePC) hardware support based on patches 16 2. Extra knobs 22 5. Hardware version 2 26 5.2.2 One/Three finger touch 32 6.2.2 Two finger touch 37 7.2.2 Head packet 50 hardware versions unimaginatively called version 1,version 2, version 3 52 packet. Version 2 seems to be introduced with the EeePC and uses 6 bytes 55 for 2 fingers the concatenation of two 6 bytes packets) and allows tracking 57 combine a status packet with multiple head or motion packets. Hardware version [all …]
|
/Documentation/devicetree/bindings/soundwire/ |
D | soundwire-controller.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 14 SoundWire busses can be described with a node for the SoundWire controller 15 device and a set of child nodes for each SoundWire slave on the bus. 22 const: 2 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}$" 43 CID is 2 nibbles 65 #address-cells = <2>; 72 powerdown-gpios = <&wcdpinctrl 2 0>; 77 speaker@0,2 { [all …]
|
/Documentation/vm/ |
D | mmu_notifier.rst | 6 When clearing a pte/pmd we are given a choice to notify the event through 11 thing like ATS/PASID to get the IOMMU to walk the CPU page table to access a 12 process virtual address space). There is only 2 cases when you need to notify 13 those secondary TLB while holding page table lock when clearing a pte/pmd: 15 A) page backing address is free before mmu_notifier_invalidate_range_end() 16 B) a page table entry is updated to point to a new page (COW, write fault 19 Case A is obvious you do not want to take the risk for the device to write to 20 a page that might now be used by some completely different task. 29 If clearing the page table entry is not followed by a notify before setting 33 Consider the following scenario (device use a feature similar to ATS/PASID): [all …]
|
/Documentation/devicetree/bindings/sound/ |
D | tlv320adcx140.yaml | 1 # SPDX-License-Identifier: (GPL-2.0+ OR BSD-2-Clause) 16 converter (ADC) with analog inputs supporting up to 2V RMS. The TLV320ADCX140 17 family supports line and microphone Inputs, and offers a programmable 60 2 - Set VREF to 1.375V 62 enum: [0, 1, 2] 74 PDMIN1 - PDMCLK latching edge used for channel 1 and 2 data 92 1 - GPIX is configured as a general-purpose input (GPI) 93 2 - GPIX is configured as a master clock input (MCLK) 95 4 - GPIX is configured as a PDM data input for channel 1 and channel 97 5 - GPIX is configured as a PDM data input for channel 3 and channel [all …]
|
/Documentation/admin-guide/media/ |
D | imx.rst | 27 packed <--> planar conversion. The IDMAC can also perform a simple 32 camera sensors over Parallel, BT.656/1120, and MIPI CSI-2 buses. 52 rotation operation is carried out on 8x8 pixel blocks at a time. This 60 contains a Combiner that combines two image planes, with alpha blending 66 - MIPI CSI-2 Receiver for camera sensors with the MIPI CSI-2 bus 67 interface. This is a Synopsys DesignWare core. 69 to send to a CSI. 84 - Supports parallel, BT.565, and MIPI CSI-2 interfaces. 99 VDIC from memory buffers via a output/mem2mem devices. 101 - Includes a Frame Interval Monitor (FIM) that can correct vertical sync [all …]
|
D | qcom_camss.rst | 20 The driver is implemented using as a reference the Qualcomm Camera Subsystem 30 - 2 / 3 CSIPHY modules. They handle the Physical layer of the CSI2 receivers. 31 A separate camera sensor can be connected to each of the CSIPHY module; 32 - 2 / 4 CSID (CSI Decoder) modules. They handle the Protocol and Application 33 layer of the CSI2 receivers. A CSID can decode data stream from any of the 34 CSIPHY. Each CSID also contains a TG (Test Generator) block which can generate 38 - 1 / 2 VFE (Video Front End) module(s). Contain a pipeline of image processing 41 processing pipeline contains also a scale and crop module at the end. Three 60 - YUYV/UYVY/YVYU/VYUY (packed YUV 4:2:2 - V4L2_PIX_FMT_YUYV / 88 - YUYV/UYVY/YVYU/VYUY (packed YUV 4:2:2 - V4L2_PIX_FMT_YUYV / [all …]
|
D | dvb_intro.rst | 17 video) is an analogue encoding of a sequence of image frames (25 frames 20 Analogue TV card for a PC has the following purpose: 22 * Tune the receiver to receive a broadcast signal 29 some countries employ a digital audio signal 37 circuitry on the card and is often presented uncompressed. For a PAL TV 38 signal encoded at a resolution of 768x576 24-bit color pixels over 25 39 frames per second - a fair amount of data is generated and must be 46 The purpose of a simple budget digital TV card (DVB-T,C or S) is to 49 * Tune the received to receive a broadcast signal. * Extract the encoded 55 digital TV card spits out a compressed encoded digital datastream. As [all …]
|
/Documentation/devicetree/bindings/pinctrl/ |
D | brcm,bcm2835-gpio.txt | 3 The BCM2835 GPIO module is a combined GPIO controller, (GPIO) interrupt 14 - gpio-controller: Marks the device node as a GPIO controller. 23 - #interrupt-cells : Should be 2. 28 2 = high-to-low edge triggered. 31 Valid combinations are 1, 2, 3, 4, 8. 33 Please refer to ../gpio/gpio.txt for a general description of GPIO bindings. 42 listed. In other words, a subnode that lists only a mux function implies no 43 information about any pull configuration. Similarly, a subnode that lists only 44 a pul parameter implies no information about the mux function. 65 - brcm,pins: An array of cells. Each cell contains the ID of a pin. Valid IDs [all …]
|
/Documentation/devicetree/bindings/mfd/ |
D | kontron,sl28cpld.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 14 watchdog, fan monitoring, PWM controller, interrupt controller and a 33 const: 2 41 "^gpio(@[0-9a-f]+)?$": 44 "^hwmon(@[0-9a-f]+)?$": 47 "^interrupt-controller(@[0-9a-f]+)?$": 50 "^pwm(@[0-9a-f]+)?$": 53 "^watchdog(@[0-9a-f]+)?$": 71 sl28cpld@4a { 91 #pwm-cells = <2>; [all …]
|
/Documentation/x86/ |
D | usb-legacy-support.rst | 11 Also known as "USB Keyboard" or "USB Mouse support" in the BIOS Setup is a 13 their classic PS/2 counterparts. This means one can use an USB keyboard to 18 1) On some machines, the emulated PS/2 mouse takes over even when no USB 19 mouse is present and a real PS/2 mouse is present. In that case the extra 20 features (wheel, extra buttons, touchpad mode) of the real PS/2 mouse may 23 2) If CONFIG_HIGHMEM64G is enabled, the PS/2 mouse emulation can cause 25 The Intel E7505 is a typical machine where this happens. 36 PS/2 mouse driver. Since the PS/2 mouse driver is in 2.6 compiled into 40 Problem 2) 42 in the kernel config or USB Legacy support in the BIOS. A BIOS update [all …]
|
/Documentation/devicetree/bindings/mailbox/ |
D | arm,mhu.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 13 The ARM's Message-Handling-Unit (MHU) is a mailbox controller that has 3 15 are hardwired on a platform. A link raises interrupt for any received data. 19 be a 'Secure' resource, hence can't be used by Linux running NS. 22 interrupt signal using a 32-bit register, with all 32-bits logically ORed 23 together. It provides a set of registers to enable software to set, clear and 27 be associated with a type of event that can contribute to raising the 31 # We need a select here so we don't match all nodes with 'arm,primecell' 76 Set to 2 in doorbell mode and represents index of the channel and doorbell 78 enum: [ 1, 2 ] [all …]
|
/Documentation/devicetree/bindings/misc/ |
D | xlnx,sd-fec.txt | 3 The Soft Decision Forward Error Correction (SDFEC) Engine is a Hard IP block 5 The LDPC decode & encode functionality is capable of covering a range of 27 - xlnx,sdfec-din-words : A value 0 indicates that the DIN_WORDS interface is 28 driven with a fixed value and is not present on the device, a value of 1 29 configures the DIN_WORDS to be block based, while a value of 2 configures the 31 - xlnx,sdfec-din-width : Configures the DIN AXI stream where a value of 1 32 configures a width of "1x128b", 2 a width of "2x128b" and 4 configures a width 34 - xlnx,sdfec-dout-words : A value 0 indicates that the DOUT_WORDS interface is 35 driven with a fixed value and is not present on the device, a value of 1 36 configures the DOUT_WORDS to be block based, while a value of 2 configures the [all …]
|
12345678910>>...54