Home
last modified time | relevance | path

Searched full:accessing (Results 1 – 25 of 1078) sorted by relevance

12345678910>>...44

/Linux-v5.15/drivers/mfd/
DKconfig30 accessing the external gpio extender (LEDs & buttons) and
109 This driver provides common support for accessing the device,
141 This driver provides common support for accessing the device,
324 for accessing the device, additional drivers must be enabled in
336 for accessing the device, additional drivers must be enabled in
348 accessing the device as well as the I2C interface to the chip itself.
388 chip. This driver provides common support for accessing the device.
433 This driver provides common support for accessing the device.
444 This driver provides common support for accessing the device,
482 processors. This driver provides common support for accessing the
[all …]
/Linux-v5.15/arch/x86/include/asm/
Diosf_mbi.h106 * the PMIC bus while another driver is also accessing the PMIC bus various bad
115 * P-Unit for exclusive access to the PMIC bus when i2c drivers are accessing
161 * process context) before other drivers start accessing the PMIC bus.
164 * the window the other driver is accessing the PMIC, before hand.
/Linux-v5.15/drivers/gpu/drm/amd/display/dc/dcn20/
Ddcn20_optc.c304 /* accessing slave OTG registers */ in optc2_align_vblanks()
327 /* accessing master OTG registers */ in optc2_align_vblanks()
367 /* accessing slave OTG registers */ in optc2_align_vblanks()
377 /* accessing master OTG registers */ in optc2_align_vblanks()
387 /* accessing slave OTG registers */ in optc2_align_vblanks()
395 /* accessing master OTG registers */ in optc2_align_vblanks()
411 /* accessing slave OTG registers */ in optc2_align_vblanks()
/Linux-v5.15/drivers/scsi/ufs/
DKconfig108 accessing the hardware which includes PHY configuration and vendor
122 accessing the hardware which includes PHY configuration and vendor
154 accessing flash storage on digital cameras, mobile phones and
/Linux-v5.15/arch/mips/loongson2ef/common/
Dpci.c36 * local to PCI mapping for CPU accessing PCI space in setup_pcimap()
37 * CPU address space [256M,448M] is window for accessing pci space in setup_pcimap()
/Linux-v5.15/include/linux/
Ddevm-helpers.h42 * driver is detached to avoid accessing removed resources.
67 * is detached to avoid accessing removed resources.
Ddma-buf-map.h33 * accessing the buffer. Use the returned instance and the helper functions
45 * considered bad style. Rather then accessing its fields directly, use one
240 * method of accessing the memory.
/Linux-v5.15/drivers/net/ethernet/qlogic/qed/
Dqed_hw.h186 * accessing the ptt window. There is no way to unpretend
201 * accessing the ptt window
223 * when accessing the ptt window
/Linux-v5.15/arch/xtensa/include/asm/
Duaccess.h6 * These routines provide basic accessing functions to the user memory
126 * accessing user space so we don't crash the kernel. Both
147 * We don't tell gcc that we are accessing memory, but this is OK
269 * returns zero if a problem occurs while accessing user-space memory.
/Linux-v5.15/Documentation/devicetree/bindings/mtd/
Ddavinci-nand.txt17 - offset and length for accessing the AEMIF
22 for accessing the nand.
/Linux-v5.15/drivers/net/ethernet/mellanox/mlx5/core/steering/
Dmlx5dr.h154 /* This is the list of used chunks. HW may be accessing this memory */
158 /* Hardware may be accessing this memory but at some future,
/Linux-v5.15/Documentation/core-api/
Dunaligned-memory-access.rst40 When accessing N bytes of memory, the base memory address must be evenly
95 not be unreasonable to expect that accessing field2 would cause an unaligned
110 At this point, it should be clear that accessing a single byte (u8 or char)
136 lead to unaligned accesses when accessing fields that do not satisfy
/Linux-v5.15/include/uapi/linux/
Ddma-buf.h34 * Prior to accessing the map, the client must call DMA_BUF_IOCTL_SYNC
41 * accessing the memory at the same time. If synchronization with a GPU or
/Linux-v5.15/Documentation/powerpc/
Ddscr.rst63 Accessing DSCR through privileged SPR number (0x11) from user space
67 Accessing DSCR through user level SPR (0x03) from user space will first
/Linux-v5.15/drivers/mtd/nand/raw/brcmnand/
Diproc_nand.c84 * the APB bus to LE mode before accessing the FIFO and back to BE mode in iproc_nand_apb_access()
92 } else { /* when in LE accessing the parameter page, keep APB in BE */ in iproc_nand_apb_access()
/Linux-v5.15/drivers/net/wireless/intel/iwlegacy/
Dcsr.h77 * The MAC (uCode processor, etc.) does not need to be powered up for accessing
258 * MAC_CLOCK_READY (and !GOING_TO_SLEEP) before accessing non-CSR
371 * to make sure the MAC (uCode processor, etc.) is powered up for accessing
380 * Registers for accessing device's internal SRAM memory (e.g. SCD SRAM
398 * Registers for accessing device's internal peripheral registers
/Linux-v5.15/arch/arm/mach-omap2/
Dvp.c51 pr_err("%s: No read/write API for accessing vdd_%s regs\n", in omap_vp_init()
209 pr_err("%s: No read/write API for accessing vdd_%s regs\n", in omap_vp_enable()
254 pr_err("%s: No read/write API for accessing vdd_%s regs\n", in omap_vp_disable()
/Linux-v5.15/Documentation/trace/coresight/
Dcoresight-cpu-debug.rst69 Before accessing debug registers, we should ensure the clock and power domain
111 In this case, accessing to the debug registers while they are not powered
150 ensure the accessing to debug logic.
/Linux-v5.15/Documentation/admin-guide/
Dsysfs-rules.rst15 abstractions these programs provide instead of accessing sysfs directly.
88 - accessing attributes reached by a symlink pointing to another device,
148 Accessing ``/sys/class/net/eth0/device`` is a bug in the application.
/Linux-v5.15/drivers/target/tcm_fc/
DKconfig6 Say Y here to enable the TCM FC plugin for accessing FC fabrics in TCM
/Linux-v5.15/arch/m68k/include/asm/
Dio_no.h30 * type of address range we are accessing. Include the ColdFire platform
43 * determine if we are accessing an internal peripheral device given the
/Linux-v5.15/arch/powerpc/include/asm/book3s/64/
Dkup.h212 * access restrictions. Because of this ignore AMR value when accessing
352 * We do have exception table entry, but accessing the
356 * in catching the use case of accessing without unlocking
/Linux-v5.15/drivers/md/
Ddm-cache-metadata.h41 * A new feature that is not compatible with old code accessing the
134 * neccessarily have a fast way of accessing efficiently via cblock. So
/Linux-v5.15/drivers/staging/media/atomisp/pci/base/circbuf/interface/
Dia_css_circbuf.h65 * to avoid accessing to an empty buffer.
78 * to avoid accessing to an empty buffer.
296 * to avoid accessing to a full buffer.
/Linux-v5.15/arch/ia64/include/asm/
Duaccess.h10 * trick us into accessing kernel memory that would normally be
23 * fault while accessing it. This is handled by filling out an
56 * When accessing user memory, we need to make sure the entire area really is in

12345678910>>...44