Home
last modified time | relevance | path

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

12345678910>>...42

/linux-5.10/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,
481 processors. This driver provides common support for accessing the
[all …]
/linux-5.10/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-5.10/drivers/scsi/ufs/
DKconfig107 accessing the hardware which includes PHY configuration and vendor
120 accessing the hardware which includes PHY configuration and vendor
152 accessing flash storage on digital cameras, mobile phones and
/linux-5.10/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-5.10/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-5.10/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-5.10/Documentation/devicetree/bindings/mtd/
Ddavinci-nand.txt17 - offset and length for accessing the AEMIF
22 for accessing the nand.
/linux-5.10/Documentation/driver-api/
Ddevice-io.rst39 should call ioremap(). An address suitable for accessing
48 Accessing the device
133 Accessing Port Space
/linux-5.10/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-5.10/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-5.10/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-5.10/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-5.10/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-5.10/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-5.10/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-5.10/drivers/target/tcm_fc/
DKconfig6 Say Y here to enable the TCM FC plugin for accessing FC fabrics in TCM
/linux-5.10/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-5.10/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-5.10/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-5.10/Documentation/filesystems/
Dext3.rst12 filesystem is a subset of ext4 filesystem so use ext4 driver for accessing
/linux-5.10/include/linux/
Dtoshiba.h2 /* toshiba.h -- Linux driver for accessing the SMM on Toshiba laptops
/linux-5.10/Documentation/networking/device_drivers/ethernet/huawei/
Dhinic.rst38 for accessing the PCI NIC.
46 The interface for accessing the pci device (DMA memory and PCI BARs).
/linux-5.10/arch/openrisc/kernel/
Dprom.c12 * Architecture specific procedures for creating, accessing and
/linux-5.10/Documentation/devicetree/bindings/security/tpm/
Dtpm_tis_mmio.txt3 The TCG defines multi vendor standard for accessing a TPM chip, this
/linux-5.10/arch/riscv/include/asm/
Dclint.h15 * any overhead when accessing the MMIO timer.

12345678910>>...42