/linux-6.12.1/include/soc/arc/ |
D | aux.h | 34 #define READ_BCR(reg, into) \ argument 38 if (sizeof(tmp) == sizeof(into)) { \ 39 into = *((typeof(into) *)&tmp); \ 46 #define WRITE_AUX(reg, into) \ argument 49 if (sizeof(tmp) == sizeof(into)) { \ 50 tmp = (*(unsigned int *)&(into)); \
|
/linux-6.12.1/tools/testing/radix-tree/ |
D | test.c | 121 unsigned long into; in item_gang_check_present() local 123 for (into = 0; into < nr; ) { in item_gang_check_present() 128 if (nr_to_find > (nr - into)) in item_gang_check_present() 129 nr_to_find = nr - into; in item_gang_check_present() 132 start + into, nr_to_find); in item_gang_check_present() 135 assert(items[i]->index == start + into + i); in item_gang_check_present() 136 into += hop; in item_gang_check_present() 147 unsigned long into = 0; in item_full_scan() local 154 while ((nfound = radix_tree_gang_lookup(root, (void **)items, into, in item_full_scan() 163 into = this_index; in item_full_scan()
|
/linux-6.12.1/Documentation/ABI/testing/ |
D | sysfs-firmware-turris-mox-rwtm | 5 Description: (Read) Board version burned into eFuses of this Turris Mox board. 12 Description: (Read) MAC addresses burned into eFuses of this Turris Mox board. 20 as pair to the ECDSA private key burned into eFuses of this 29 during manufacturing and burned into eFuses. Can be 512 or 1024. 36 Description: (Read) Serial number burned into eFuses of this Turris Mox device.
|
D | sysfs-ptp | 14 hardware clock registered into the PTP class driver 94 assignment may be changed by two writing numbers into 112 channel index followed by a "1" into the file. 114 index followed by a "0" into the file. 130 integers into the file: channel index, start time 141 events, write a "1" into the file. To disable events, 142 write a "0" into the file.
|
/linux-6.12.1/Documentation/filesystems/ |
D | idmappings.rst | 14 An idmapping is essentially a translation of a range of ids into another or the 37 idmapping is an order isomorphism from ``U`` into ``K``. So ``U`` and ``K`` are 50 dealing with subsets we can embed idmappings into each other, i.e. we can 126 of userspace ids into a range of kernel ids:: 174 immediately translated into a kernel id according to the idmapping associated 212 then translate ``k11000`` into a userspace id in the second idmapping using the 215 /* Map the kernel id up into a userspace id in the second idmapping. */ 221 /* Map the userspace id down into a kernel id in the second idmapping. */ 224 /* Map the kernel id up into a userspace id in the first idmapping. */ 233 into a kernel id according to the idmapping associated with the filesystem. [all …]
|
/linux-6.12.1/rust/kernel/net/phy/ |
D | reg.rs | 111 bindings::mdiobus_read((*phydev).mdio.bus, (*phydev).mdio.addr, self.0.into()) in read() 123 bindings::mdiobus_write((*phydev).mdio.bus, (*phydev).mdio.addr, self.0.into(), val) in write() 202 unsafe { bindings::phy_read_mmd(phydev, self.devad.0.into(), self.regnum.into()) }; in read() 212 bindings::phy_write_mmd(phydev, self.devad.0.into(), self.regnum.into(), val) in write()
|
/linux-6.12.1/Documentation/admin-guide/pm/ |
D | sleep-states.rst | 34 I/O devices into low-power states (possibly lower-power than available in the 58 I/O devices into low-power states, which is done for :ref:`suspend-to-idle 60 are suspended during transitions into this state. For this reason, it should 79 energy savings as everything in the system is put into a low-power state, except 80 for memory, which should be placed into the self-refresh mode to retain its 89 suspended and put into low-power states. In many cases, all peripheral buses 118 It takes three system state changes to put it into hibernation and two system 122 creates a snapshot image of memory to be written into persistent storage. Next, 123 the system goes into a state in which the snapshot image can be saved, the image 124 is written out and finally the system goes into the target low-power state in [all …]
|
/linux-6.12.1/drivers/accessibility/speakup/ |
D | Kconfig | 55 synthesizer. You can say y to build it into the kernel, 64 synthesizer. You can say y to build it into the kernel, 72 synthesizer. You can say y to build it into the kernel, 80 You can say y to build it into the kernel, or m to 88 synthesizer. You can say y to build it into the kernel, 97 synthesizer. You can say y to build it into the kernel, 106 (old) synthesizer. You can say y to build it into the 140 PC synthesizer. You can say y to build it into the 151 PC synthesizer. You can say y to build it into the 161 LT synthesizer. You can say y to build it into the [all …]
|
/linux-6.12.1/arch/mips/include/asm/mach-ip27/ |
D | kernel-entry-init.h | 36 li t0, 0x1c000 # Offset of text into node memory 37 dsll t1, NASID_SHFT # Shift text nasid into place 43 dsll t1, 6 # Get pfn into place 44 dsll t2, 6 # Get pfn into place
|
/linux-6.12.1/drivers/bluetooth/ |
D | Kconfig | 35 Say Y here to compile support for Bluetooth USB devices into the 101 Say Y here to compile support for Bluetooth SDIO devices into the 117 Say Y here to compile support for Bluetooth UART devices into the 298 Say Y here to compile support for HCI BCM203x devices into the 310 Say Y here to compile support for HCI BCM4377 family devices into the 321 Say Y here to compile support for HCI BPA10x devices into the 334 Say Y here to compile support for HCI BFUSB devices into the 347 Say Y here to compile support for HCI DTL1 devices into the 361 Say Y here to compile support for HCI BT3C devices into the 374 Say Y here to compile support for HCI BlueCard devices into the [all …]
|
/linux-6.12.1/Documentation/trace/ |
D | histogram-design.rst | 158 If a map_entry is unused, meaning no key has yet hashed into it, its | | 451 into the tracing_map_elts' .vars[] array containing variable values. | | | 592 just the index into the var_ref_vals[] array that caches the values of | | 735 index into the tracing_map_elt.vars[] array of the actual variable 765 var.idx (into tracing_map_elt.vars[]): 0 822 var.idx (into tracing_map_elt.vars[]): 0 843 var.idx (into tracing_map_elt.vars[]): 0 845 var_ref_idx (into hist_data->var_refs[]): 0 868 them to generate a new wakeup_latency event into the trace stream. 903 next_pid into the wakeup_latency synthetic event invocation, which [all …]
|
/linux-6.12.1/drivers/thermal/renesas/ |
D | Kconfig | 9 Enable this to plug the R-Car thermal sensor driver into the Linux 18 Enable this to plug the R-Car Gen3 or RZ/G2 thermal sensor driver into 27 Enable this to plug the RZ/G2L thermal sensor driver into the Linux
|
/linux-6.12.1/drivers/nfc/nfcmrvl/ |
D | Kconfig | 21 into the kernel or say M to compile it as module. 33 into the kernel or say M to compile it as module. 44 into the kernel or say M to compile it as module. 55 into the kernel or say M to compile it as module.
|
/linux-6.12.1/Documentation/mm/ |
D | arch_pgtable_helpers.rst | 77 | ptep_set_wrprotect | Converts into a write protected PTE | 79 | ptep_set_access_flags | Converts into a more permissive PTE | 154 | pmdp_set_wrprotect | Converts into a write protected PMD | 156 | pmdp_set_access_flags | Converts into a more permissive PMD | 209 | pudp_set_wrprotect | Converts into a write protected PUD | 211 | pudp_set_access_flags | Converts into a more permissive PUD | 235 | huge_ptep_set_wrprotect | Converts into a write protected HugeTLB | 237 | huge_ptep_set_access_flags | Converts into a more permissive HugeTLB |
|
/linux-6.12.1/Documentation/power/ |
D | pci.rst | 31 devices into states in which they draw less power (low-power states) at the 34 Usually, a device is put into a low-power state when it is underutilized or 36 again, it has to be put back into the "fully functional" state (full-power 41 PCI devices may be put into low-power states in two ways, by using the device 46 specific value into one of its standard configuration registers. The second 53 to put the device that sent it into the full-power state. However, the PCI Bus 92 programmed to go into it. The second one, D3cold, is the state that PCI devices 94 to program a PCI device to go into D3cold, although there may be a programmable 95 interface for putting the bus the device is on into a state in which Vcc is 111 programmatically put into D0. Thus the kernel can switch the device back and [all …]
|
/linux-6.12.1/arch/arm/kernel/ |
D | phys2virt.S | 78 @ instructions, where we need to patch in the offset into the 88 @ offset into the immediate field of the MOV instruction, or patch it 94 @ order bits, which can be patched into imm8 directly (and i:imm3 105 ubfx r6, r6, #21, #8 @ put bits 28:21 into the MOVW imm8 field 106 bfi r6, r3, #12, #3 @ put bits 31:29 into the MOVW imm3 field 156 @ instructions, where we need to patch in the offset into the 170 @ word, and patch in the high word of the offset into the immediate 183 mov r3, r6, lsr #16 @ put offset bits 31-16 into r3 184 mov r6, r6, lsr #24 @ put offset bits 31-24 into r6
|
/linux-6.12.1/arch/mips/cavium-octeon/ |
D | Kconfig | 34 Enable locking parts of the kernel into the L2 cache. 41 Lock the low level TLB fast path into L2. 48 Lock the low level exception handler into L2. 55 Lock the low level interrupt handler into L2. 69 Lock the kernel's implementation of memcpy() into L2.
|
/linux-6.12.1/arch/m68k/fpsp040/ |
D | binstr.S | 29 | extracts and shifts. The three msbs from d2 will go into 36 | into d2:d3. D1 will contain the bcd digit formed. 57 | a0: pointer into memory for packed bcd string formation 87 | A3. Multiply d2:d3 by 8; extract msbs into d1. 89 bfextu %d2{#0:#3},%d1 |copy 3 msbs of d2 into d1 91 bfextu %d3{#0:#3},%d6 |copy 3 msbs of d3 into d6 93 orl %d6,%d2 |or in msbs from d3 into d2
|
/linux-6.12.1/Documentation/networking/ |
D | xdp-rx-metadata.rst | 31 An XDP program can use these kfuncs to read the metadata into stack 33 consumers, an XDP program can store it into the metadata area carried 52 An XDP program can store individual metadata items into this ``data_meta`` 61 program that redirects XDP frames into the ``AF_XDP`` socket (``XSK``) and 83 into the kernel. The kernel creates the ``skb`` out of the ``xdp_buff`` 101 into devmaps and cpumaps. 107 in its ``skb``. If such a packet is later redirected into an ``XSK``,
|
/linux-6.12.1/Documentation/rust/ |
D | general-information.rst | 15 kernel must opt into this behavior using the ``#![no_std]`` attribute. 106 into carefully reviewed and documented abstractions. Then users of these 117 By including a C header from ``include/`` into 132 access to the bindings into an as-safe-as-possible API that they expose to their 137 the sense that they turn the C interfaces into "idiomatic" Rust code. Basic 138 examples are to turn the C resource acquisition and release into Rust 139 constructors and destructors or C integer error codes into Rust's ``Result``\ s.
|
/linux-6.12.1/drivers/video/fbdev/geode/ |
D | Kconfig | 18 Framebuffer driver for the display controller integrated into the 31 Framebuffer driver for the display controller integrated into the 44 Framebuffer driver for the display controller integrated into the
|
/linux-6.12.1/Documentation/virt/kvm/s390/ |
D | s390-pv-boot.rst | 27 switch into PV mode itself, the user can load encrypted guest 44 Subcode 10: Move into Protected Virtualization mode 47 that is necessary to move into PV mode. 76 Re-IPL into a protected mode is only possible via a detour into non
|
/linux-6.12.1/Documentation/core-api/ |
D | symbol-namespaces.rst | 24 their exported symbols into separate namespaces. That is useful for 27 kernel. As of today, modules that make use of symbols exported into namespaces, 34 Symbols can be exported into namespace using different methods. All of them are 43 available to export symbols into a certain namespace: EXPORT_SYMBOL_NS() and 46 preprocessor symbol. E.g. to export the symbol ``usb_stor_suspend`` into the 68 export all symbols defined in usb-common into the namespace USB_COMMON, add a 75 still be exported into the namespace that is passed as the namespace argument 90 In order to use symbols that are exported into namespaces, kernel modules need
|
/linux-6.12.1/Documentation/gpu/amdgpu/ |
D | amdgpu-glossary.rst | 36 (memory or MMIO space) into the GPU's address space so the GPU can access 51 allow the GPU to remap VRAM and system resources into GPU virtual address 58 use by the GPU. These addresses can be mapped into the "GART" GPUVM page 59 table for use by the kernel driver or into per process GPUVM page tables
|
/linux-6.12.1/arch/s390/kernel/ |
D | relocate_kernel.S | 45 lgr %r2,%r5 # move it into the right register, 63 la %r4,load_psw-.base(%r13) # load psw-address into the register 64 o %r3,4(%r4) # or load address into psw
|