Home
last modified time | relevance | path

Searched full:talks (Results 1 – 25 of 73) sorted by relevance

123

/kernel/linux/linux-5.10/arch/mips/include/asm/sgi/
Dmc.h75 #define SGIMC_GIOPAR_HPC64 0x00000001 /* HPC talks to GIO using 64-bits */
76 #define SGIMC_GIOPAR_GFX64 0x00000002 /* GFX talks to GIO using 64-bits */
77 #define SGIMC_GIOPAR_EXP064 0x00000004 /* EXP(slot0) talks using 64-bits */
78 #define SGIMC_GIOPAR_EXP164 0x00000008 /* EXP(slot1) talks using 64-bits */
79 #define SGIMC_GIOPAR_EISA64 0x00000010 /* EISA bus talks 64-bits to GIO */
80 #define SGIMC_GIOPAR_HPC264 0x00000020 /* 2nd HPX talks 64-bits to GIO */
/kernel/linux/linux-5.10/drivers/acpi/pmic/
Dintel_pmic_chtcrc.c18 * Cove Plus" PMIC and talks about Cherry Trail, so presuambly that one
/kernel/linux/linux-5.10/Documentation/hwmon/
Dibmaem.rst4 This driver talks to the IBM Systems Director Active Energy Manager, known
Dacpi_power_meter.rst4 This driver talks to ACPI 4.0 power meters.
/kernel/linux/linux-5.10/arch/m68k/
DKconfig.bus44 name of a bus system, i.e. the way the CPU talks to the other stuff
/kernel/linux/linux-5.10/Documentation/driver-api/
Dspi.rst18 only "master" side interfaces are supported, where Linux talks to SPI
/kernel/linux/linux-5.10/Documentation/core-api/
Dkref.rst11 - http://www.kroah.com/linux/talks/ols_2004_kref_paper/Reprint-Kroah-Hartman-OLS2004.pdf
12 - http://www.kroah.com/linux/talks/ols_2004_kref_talk/
Dbus-virt-phys-mapping.rst140 only talks about "real memory", that is, CPU memory (RAM).
/kernel/linux/linux-5.10/net/netfilter/
Dnf_nat_irc.c83 /* AAA = "us", ie. where server normally talks to. */ in help()
/kernel/linux/linux-5.10/include/linux/usb/
Dusb338x.h4 * Unlike many such controllers, this one talks PCI.
/kernel/linux/linux-5.10/drivers/usb/gadget/udc/
Dpxa27x_udc.h221 * the udc talks on (config=3, interface=0, alt=0)
223 * the udc talks on (config=3, interface=0, alt=1)
225 * the udc talks on (config=2, interface=0, alt=0)
/kernel/linux/linux-5.10/drivers/gpu/drm/msm/adreno/
Da6xx_gmu.h146 * band" means that the CPU talks to the GMU directly and not through HFI.
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/mfd/
Dgoogle,cros-ec.yaml15 Google's ChromeOS EC is a microcontroller which talks to the AP and
/kernel/linux/linux-5.10/drivers/usb/misc/
Dusb_u132.h38 * "u132-hcd" module is a USB host controller driver that talks
DKconfig122 module which is a USB host controller driver that talks to the OHCI
/kernel/linux/linux-5.10/drivers/usb/gadget/legacy/
DKconfig16 # A Linux "Gadget Driver" talks to the USB Peripheral Controller
300 The Serial Gadget talks to the Linux-USB generic serial driver.
/kernel/linux/linux-5.10/drivers/hid/intel-ish-hid/ishtp/
Dishtp-dev.h105 * The ISHTP layer talks to hardware IPC message using the following
/kernel/linux/linux-5.10/arch/hexagon/mm/
Dinit.c150 * The Gorman book also talks about these functions. in setup_arch_memory()
/kernel/linux/linux-5.10/arch/mips/sgi-ip22/
Dip22-mc.c167 tmp |= SGIMC_GIOPAR_EISA64; /* MC talks to EISA at 64bits */ in sgimc_init()
/kernel/linux/linux-5.10/Documentation/networking/device_drivers/ethernet/marvell/
Docteontx2.rst105 links this driver talks to AF and AF gets that info from firmware and responds
/kernel/linux/linux-5.10/drivers/mtd/chips/
Dgen_probe.c33 /* OK we liked it. Now find a driver for the command set it talks */ in mtd_do_chip_probe()
/kernel/linux/linux-5.10/include/xen/
Dxenbus.h4 * Talks to Xen Store to figure out what devices we have.
/kernel/linux/linux-5.10/drivers/xen/xenbus/
Dxenbus_probe_backend.c2 * Talks to Xen Store to figure out what devices we have (backend half).
/kernel/linux/linux-5.10/drivers/usb/serial/
Dkeyspan_usa49msg.h226 disableStatusMessages; // 1=send no status until host talks
/kernel/linux/linux-5.10/Documentation/input/
Dinput.rst215 Much like usbmouse, this module talks to keyboards with a simplified

123