Searched +full:40 +full:a (Results 1 – 25 of 305) sorted by relevance
12345678910>>...13
| /Documentation/core-api/ |
| D | packing.rst | 10 One can memory-map a pointer to a carefully crafted struct over the hardware 20 A more robust alternative to struct field definitions would be to extract the 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. 47 The following examples cover the memory layout of a packed u64 field. 55 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 71 56 57 58 59 60 61 62 63 48 49 50 51 52 53 54 55 40 41 42 43 44 45 46 47 32 33 34 35 36 37 38 39 77 inverts bit offsets inside a byte. 84 39 38 37 36 35 34 33 32 47 46 45 44 43 42 41 40 55 54 53 52 51 50 49 48 63 62 61 60 59 58 57 56 [all …]
|
| /Documentation/tools/rtla/ |
| D | rtla-osnoise-hist.rst | 5 Display a histogram of the osnoise tracer samples 19 occurrence in a histogram, displaying the results in a user-friendly way. 48 …40 0 0 0 0 0 4 2 7 2 … 54 …max: 30 30 20 20 30 40 40 40 40 …
|
| /Documentation/arch/powerpc/ |
| D | associativity.rst | 7 of that domain. Resources subsets of a given domain that exhibit better 9 are represented as being members of a sub-grouping domain. This performance 19 A value of 1 indicates the usage of Form 1 associativity. For Form 2 associativity 28 With Form 1 a combination of ibm,associativity-reference-points, and ibm,associativity 31 The “ibm,associativity” property contains a list of one or more numbers (domainID) 34 The “ibm,associativity-reference-points” property contains a list of one or more numbers 52 "ibm,associativity-reference-points" property, Form 2 allows a large number of primary domain 59 "ibm,numa-lookup-index-table" property contains a list of one or more numbers representing 71 "ibm,numa-distance-table" property contains a list of one or more numbers representing the NUMA 80 ibm,numa-lookup-index-table = <3 0 8 40>; [all …]
|
| /Documentation/devicetree/bindings/mtd/ |
| D | rockchip,nand-controller.yaml | 73 enum: [16, 24, 40, 60, 70] 76 NFC v600 ECC 16, 24, 40, 60 79 NFC v622 ECC 16, 24, 40, 60 85 NFC v900 ECC 16, 40, 60, 70 101 enum: [16, 24, 40, 60, 70] 104 If specified it indicates that a different BCH/ECC setting is 109 NFC v622 ECC 16, 24, 40, 60
|
| /Documentation/devicetree/bindings/ |
| D | numa.txt | 9 Systems employing a Non Uniform Memory Access (NUMA) architecture contain 11 that comprise what is commonly known as a NUMA node. 21 For the purpose of identification, each NUMA node is associated with a unique 22 token known as a node id. For the purpose of this binding 23 a node id is a 32-bit integer. 25 A device node is associated with a NUMA node by the presence of a 45 This property defines a matrix to describe the relative distances 47 It is represented as a list of node pairs and their relative distance. 52 2. The distance from a node to self (local distance) is represented 54 a value greater than 10. [all …]
|
| /Documentation/devicetree/bindings/ufs/ |
| D | snps,tc-dwc-g210.yaml | 18 - snps,dwc-ufshcd-1.40a 30 - snps,g210-tc-6.00-40bit 31 - const: snps,dwc-ufshcd-1.40a 46 compatible = "snps,g210-tc-6.00-40bit", 47 "snps,dwc-ufshcd-1.40a",
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | mpc5121-psc.txt | 18 - interrupts : <a b> where a is the interrupt number of the 19 PSC FIFO Controller and b is a field that represents an 23 - fsl,rx-fifo-size : the size of the RX fifo slice (a multiple of 4) 24 - fsl,tx-fifo-size : the size of the TX fifo slice (a multiple of 4) 29 Similar to the UART mode a PSC can be operated in SPI mode. The compatible used 30 for that is fsl,mpc5121-psc-spi. It requires a fsl,mpc5121-psc-fifo as well. 43 - interrupts : <a b> where a is the interrupt number of the 44 PSC FIFO Controller and b is a field that represents an 51 Example for a board using PSC0 and PSC1 devices in serial mode: 57 interrupts = <40 0x8>; [all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | pwm-clock.yaml | 7 title: An external clock signal driven by a PWM pin. 43 pwms = <&pwm2 0 40>; /* 1 / 40 ns = 25 MHz */
|
| /Documentation/input/devices/ |
| D | cma3000_d0x.rst | 8 CMA3000-D0X Product Family Specification 8281000A.02.pdf 26 axis and supports 400, 100, 40 Hz sample frequency. 99 Event code 40 (Misc) 114 3: 40 Hz Measurement mode 117 6: 40 Hz Free fall mode
|
| /Documentation/devicetree/bindings/regulator/ |
| D | samsung,s2mps13.yaml | 13 This is a part of device tree bindings for S2M and S5M family of Power 22 # 40 LDOs 23 "^LDO([1-9]|[1-3][0-9]|40)$":
|
| /Documentation/filesystems/ext4/ |
| D | directory.rst | 6 In an ext4 filesystem, a directory is more or less a flat file that maps 12 associated with a directory file for the particular directory entry that 19 array. I write “almost” because it's not a linear array in the memory 21 Therefore, it is more accurate to say that a directory is a series of 22 data blocks and that each block contains a linear array of directory 24 end of the block; the last entry in the block has a record length that 37 :widths: 8 8 24 40 51 - Length of this directory entry. Must be a multiple of 4. 62 entry format shortens the name_len field and uses the space for a file 69 :widths: 8 8 24 40 [all …]
|
| D | ifork.rst | 14 The target of a symbolic link will be stored in this field if the target 23 that stores a particular file block, the code would navigate through 24 this increasingly complicated structure. Notice that there is neither a 25 magic number nor a checksum to provide any level of confidence that the 36 Note that with this block mapping scheme, it is necessary to fill out a 37 lot of mapping data even for a large contiguous file! This inefficiency 40 Notice also that a file using this mapping scheme cannot be placed 47 tree. Under the old scheme, allocating a contiguous run of 1,000 blocks 49 mapping is reduced to a single ``struct ext4_extent`` with 51 very large files with a single extent, at a considerable reduction in [all …]
|
| D | journal.rst | 6 Introduced in ext3, the ext4 filesystem employs a journal to protect the 7 filesystem against metadata inconsistencies in the case of a system crash. Up 9 size limits) can be reserved inside the filesystem as a place to land 12 cache, a record of the data being committed is also written to the journal. At 14 final locations on disk (this could involve a lot of seeking or a lot of small 19 guarantee that the filesystem does not become stuck midway through a 24 guaranteed to be in any consistent state after a crash. If this default 25 guarantee level (``data=ordered``) is not satisfactory, there is a mount 37 or if JBD2 commit timer goes off, Ext4 performs a traditional full commit. 38 A full commit invalidates all the fast commits that happened before [all …]
|
| D | attributes.rst | 6 Extended attributes (xattrs) are typically stored in a separate data 21 block to contain a pointer to a second extended attribute block (or even 22 the remaining blocks of a cluster). In theory it is possible for each 23 attribute's value to be stored in a separate data block, though as of 29 Extended attributes, when stored after the inode, have a header 33 :widths: 8 8 24 40 50 :widths: 8 8 24 40 95 :widths: 8 8 24 40 109 - Attribute name index. There is a discussion of this below. 115 this value is relative to the start of the first entry; for a block this [all …]
|
| /Documentation/hwmon/ |
| D | w83773g.rst | 27 The chip is wired over I2C/SMBus and specified over a temperature 28 range of -40 to +125 degrees Celsius (for local sensor) and -40 to +127
|
| /Documentation/devicetree/bindings/hwmon/pmbus/ |
| D | infineon,tda38640.yaml | 14 The Infineon TDA38640 is a 40A Single-voltage Synchronous Buck 63 tda38640@40 {
|
| /Documentation/userspace-api/ioctl/ |
| D | ioctl-number.rst | 21 system calls 'write' and 'read'. For example, a SET_FOO ioctl would 23 a GET_FOO ioctl would be _IOR, although the kernel would actually write 28 many drivers share a partial letter with other drivers. 30 If you are writing a driver for a new device and need a letter, pick an 36 The second argument to _IO, _IOW, _IOR, or _IOWR is a sequence number 50 if a program calls an ioctl on the wrong device, it will get an 116 'A' 00-1F linux/apm_bios.h conflict! 117 'A' 00-0F linux/agpgart.h, conflict! 119 'A' 00-7F sound/asound.h conflict! 128 'D' 40-5F drivers/scsi/dpt/dtpi_ioctl.h Dead since 2022 [all …]
|
| /Documentation/driver-api/media/drivers/ |
| D | tuners.rst | 15 - A= ALPS_API (VHF_LO=0x14, VHF_HI=0x12, UHF=0x11) 27 A= BG+DK 43 A= F-connector 82 40x2: Tuner (5V/33V), TEMIC_API. 83 40x6: Tuner 5V 85 40x9: Tuner+FM compact 97 Note: Only 40x2 series has TEMIC_API, all newer tuners have PHILIPS_API.
|
| /Documentation/devicetree/bindings/timer/ |
| D | marvell,armada-370-xp-timer.txt | 16 - clocks : Must contain a single entry describing the clock input 32 interrupts = <37>, <38>, <39>, <40>, <5>, <6>; 41 interrupts = <37>, <38>, <39>, <40>, <5>, <6>;
|
| /Documentation/leds/ |
| D | leds-lp5562.rst | 58 To run a blinking white pattern:: 88 .max_current = 40, 94 .max_current = 40, 100 .max_current = 40, 106 .max_current = 40,
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | rockchip,rk3399-dmc.yaml | 44 The CPU interrupt number. It should be a DCF interrupt. When DDR DVFS 45 finishes, a DCF interrupt is triggered. 53 datasheet; DO NOT use a smaller "Speed Bin" than specified for the DDR3 140 default: 40 156 default: 40 164 default: 40 204 default: 40 212 default: 40 243 default: 40 251 default: 40 [all …]
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | ti,tmp513.yaml | 15 that include remote sensors, a local temperature sensor, and a high-side 39 rshunt <= pga-gain * 40 * 1000 * 1000. 40 If not, it's not possible to compute a valid calibration value. 47 The range will be equal to: pga-gain * 40mV
|
| /Documentation/devicetree/bindings/xillybus/ |
| D | xillybus.txt | 4 - compatible: Should be "xillybus,xillybus-1.00.a" 14 compatible = "xillybus,xillybus-1.00.a"; 16 interrupts = < 0 40 1 >;
|
| /Documentation/ABI/testing/ |
| D | sysfs-platform-intel-wmi-sbl-fw-update | 1 What: /sys/bus/wmi/devices/44FADEB1-B204-40F2-8581-394BBDC1B651/firmware_update_request 7 Bootloader (SBL). This attribute normally has a value 9 on next reboot, by writing a value of 1.
|
| /Documentation/devicetree/bindings/sound/ |
| D | socionext,uniphier-aio.yaml | 42 Specifies a phandle to soc-glue, which is used for changing mode of S/PDIF 97 clocks = <&sys_clk 40>; 99 resets = <&sys_rst 40>;
|
12345678910>>...13