Home
last modified time | relevance | path

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

1234

/Linux-v6.1/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 */
/Linux-v6.1/tools/perf/pmu-events/arch/x86/jaketown/
Duncore-interconnect.json208 …, and therefore it takes twice as many fits to transmit a flit. When one talks about QPI 'speed' …
218 …, and therefore it takes twice as many fits to transmit a flit. When one talks about QPI 'speed' …
228 …, and therefore it takes twice as many fits to transmit a flit. When one talks about QPI 'speed' …
239 …, and therefore it takes twice as many fits to transmit a flit. When one talks about QPI 'speed' …
250 …, and therefore it takes twice as many fits to transmit a flit. When one talks about QPI 'speed' …
261 …, and therefore it takes twice as many fits to transmit a flit. When one talks about QPI 'speed' …
272 …, and therefore it takes twice as many fits to transmit a flit. When one talks about QPI 'speed' …
283 …, and therefore it takes twice as many fits to transmit a flit. When one talks about QPI 'speed' …
294 …, and therefore it takes twice as many fits to transmit a flit. When one talks about QPI 'speed' …
305 …, and therefore it takes twice as many fits to transmit a flit. When one talks about QPI 'speed' …
[all …]
/Linux-v6.1/tools/perf/pmu-events/arch/x86/ivytown/
Duncore-interconnect.json446 …, and therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (f…
456 …, and therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (f…
466 …, and therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (f…
477 …, and therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (f…
488 …, and therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (f…
499 …, and therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (f…
510 …, and therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (f…
521 …, and therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (f…
532 …, and therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (f…
543 …, and therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (f…
[all …]
/Linux-v6.1/drivers/virt/acrn/
DKconfig8 communicates with ACRN userspace through ioctls and talks to
/Linux-v6.1/Documentation/translations/zh_CN/core-api/
Dkref.rst25 - http://www.kroah.com/linux/talks/ols_2004_kref_paper/Reprint-Kroah-Hartman-OLS2004.pdf
26 - http://www.kroah.com/linux/talks/ols_2004_kref_talk/
/Linux-v6.1/drivers/acpi/pmic/
Dintel_pmic_chtcrc.c18 * Cove Plus" PMIC and talks about Cherry Trail, so presumably that one
/Linux-v6.1/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.
/Linux-v6.1/arch/m68k/
DKconfig.bus44 name of a bus system, i.e. the way the CPU talks to the other stuff
/Linux-v6.1/Documentation/driver-api/
Dspi.rst18 only "master" side interfaces are supported, where Linux talks to SPI
/Linux-v6.1/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/
/Linux-v6.1/net/netfilter/
Dnf_nat_irc.c71 /* AAA = "us", ie. where server normally talks to. */ in help()
/Linux-v6.1/include/linux/usb/
Dusb338x.h4 * Unlike many such controllers, this one talks PCI.
/Linux-v6.1/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)
/Linux-v6.1/drivers/gpu/drm/msm/adreno/
Da6xx_gmu.h150 * band" means that the CPU talks to the GMU directly and not through HFI.
/Linux-v6.1/drivers/usb/misc/
Dusb_u132.h38 * "u132-hcd" module is a USB host controller driver that talks
/Linux-v6.1/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.
/Linux-v6.1/drivers/hid/intel-ish-hid/ishtp/
Dishtp-dev.h106 * The ISHTP layer talks to hardware IPC message using the following
/Linux-v6.1/Documentation/devicetree/bindings/mfd/
Dgoogle,cros-ec.yaml14 Google's ChromeOS EC is a microcontroller which talks to the AP and
/Linux-v6.1/arch/mips/sgi-ip22/
Dip22-mc.c167 tmp |= SGIMC_GIOPAR_EISA64; /* MC talks to EISA at 64bits */ in sgimc_init()
/Linux-v6.1/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()
/Linux-v6.1/arch/hexagon/mm/
Dinit.c147 * The Gorman book also talks about these functions. in setup_arch_memory()
/Linux-v6.1/drivers/xen/xenbus/
Dxenbus_probe_backend.c2 * Talks to Xen Store to figure out what devices we have (backend half).
/Linux-v6.1/include/xen/
Dxenbus.h4 * Talks to Xen Store to figure out what devices we have.
/Linux-v6.1/drivers/usb/serial/
Dkeyspan_usa49msg.h226 disableStatusMessages; // 1=send no status until host talks

1234