Searched full:specifically (Results 1 – 25 of 551) sorted by relevance
12345678910>>...23
| /Linux-v5.15/tools/perf/pmu-events/arch/x86/goldmont/ |
| D | frontend.json | 4 …e accesses which hit in a single cache line count as one ICACHE.HIT. Specifically, the event coun…
14 …accesses which miss in a single cache line count as one ICACHE.MISS. Specifically, the event coun…
24 … multiple fetches to a single cache line count as one ICACHE.ACCESS. Specifically, the event coun…
|
| /Linux-v5.15/tools/perf/pmu-events/arch/x86/goldmontplus/ |
| D | frontend.json | 4 …e accesses which hit in a single cache line count as one ICACHE.HIT. Specifically, the event coun…
16 …accesses which miss in a single cache line count as one ICACHE.MISS. Specifically, the event coun…
28 … multiple fetches to a single cache line count as one ICACHE.ACCESS. Specifically, the event coun…
|
| /Linux-v5.15/Documentation/driver-api/surface_aggregator/ |
| D | overview.rst | 24 host. On the Surface Book 2, specifically, it additionally provides an
28 restructured for 7th generation devices and on those, specifically Surface
50 communicate via HID, specifically using a HID-over-I2C device, whereas on
|
| D | internal.rst | 73 It, specifically, distinguishes events from request responses, matches
257 Specifically, the packet priority must only be accessed while holding the
275 them, specifically priority and state for tracing. In those cases, proper
451 them, specifically the state for tracing. In those cases, proper access is
470 layer takes on more of a management role. Specifically, it handles device
497 number of request IDs is reserved for use in events only, specifically one
532 for them. Specifically, they will, by default, receive all events from the
|
| /Linux-v5.15/tools/perf/pmu-events/arch/x86/tremontx/ |
| D | frontend.json | 4 …accesses which miss in a single cache line count as one ICACHE.MISS. Specifically, the event coun…
16 … multiple fetches to a single cache line count as one ICACHE.ACCESS. Specifically, the event coun…
|
| /Linux-v5.15/Documentation/devicetree/bindings/arm/ |
| D | arm,versatile.yaml | 23 evaluation board specifically for the ARM926EJ-S. It can be connected
30 PCI host controller. Like the sibling board, it is done specifically
|
| /Linux-v5.15/drivers/platform/surface/aggregator/ |
| D | Kconfig | 35 only 5th and later generations are currently supported. Specifically,
64 Specifically, exports error injection hooks to be used with the
|
| /Linux-v5.15/drivers/platform/surface/ |
| D | Kconfig | 59 Specifically, this driver may be needed for battery status reporting,
125 some devices, specifically the Surface Book 3, will not be supported.
163 More specifically, this driver provides ACPI platform profile support
|
| /Linux-v5.15/tools/perf/pmu-events/arch/x86/elkhartlake/ |
| D | frontend.json | 77 …ack fetches to the exact same cache line or byte chunk count as one. Specifically, the event coun…
89 …ck fetches to the exact same cache line and byte chunk count as one. Specifically, the event coun…
|
| /Linux-v5.15/drivers/scsi/esas2r/ |
| D | esas2r_log.h | 74 * the following macros are provided specifically for debugging and tracing
76 * debugging and tracing events. esas2r_hdebug is provided specifically for
|
| /Linux-v5.15/arch/arm/mach-pxa/ |
| D | mfp-pxa2xx.h | 17 * and adds the below two bits specifically for pxa2xx:
42 /* specifically for enabling wakeup on keypad GPIOs */
|
| /Linux-v5.15/Documentation/powerpc/ |
| D | booting.rst | 6 During the development of the Linux/ppc64 kernel, and more specifically, the
26 to define nodes for on chip devices and other buses that don't specifically fit
|
| /Linux-v5.15/drivers/net/wan/lmc/ |
| D | Makefile | 4 # Specifically the 1000,1200,5200,5245
|
| /Linux-v5.15/include/drm/ |
| D | drm_utils.h | 4 * Specifically this file is for function prototypes for functions which
|
| /Linux-v5.15/scripts/ |
| D | gcc-x86_32-has-stack-protector.sh | 4 # This requires GCC 8.1 or better. Specifically, we require
|
| /Linux-v5.15/include/linux/surface_aggregator/ |
| D | device.h | 66 * SSAM_SDEV() exclusively. Specifically, they are used to initialize the
333 * client device, specifically its UID, supplied when calling this function.
366 * are provided via the client device, specifically its UID, supplied when
400 * are provided via the client device, specifically its UID, supplied when
|
| /Linux-v5.15/Documentation/ABI/obsolete/ |
| D | sysfs-class-dax | 9 Specifically this interface:
|
| /Linux-v5.15/tools/memory-model/litmus-tests/ |
| D | WRC+pooncerelease+fencermbonceonce+Once.litmus | 9 * specifically, this litmus test is forbidden because smp_store_release()
|
| /Linux-v5.15/arch/arm/include/asm/ |
| D | compiler.h | 12 * For compatibility with clang, we have to specifically take the equivalence
|
| /Linux-v5.15/Documentation/devicetree/bindings/media/ |
| D | img-ir-rev1.txt | 4 specifically major revision 1.
|
| /Linux-v5.15/Documentation/scheduler/ |
| D | schedutil.txt | 16 Specifically:
58 For Intel specifically, we use:
|
| /Linux-v5.15/drivers/media/usb/pvrusb2/ |
| D | pvrusb2-wm8775.c | 10 This source file is specifically designed to interface with the
|
| /Linux-v5.15/Documentation/nios2/ |
| D | nios2.rst | 17 Nios II is a 32-bit embedded-processor architecture designed specifically for the
|
| /Linux-v5.15/Documentation/devicetree/bindings/arm/freescale/ |
| D | fsl,imx7ulp-pm.yaml | 14 the MCU into and out of all stop and run power modes. Specifically, it
|
| /Linux-v5.15/security/apparmor/ |
| D | path.c | 41 * specifically directed to connect the path,
45 * of chroot) and specifically directed to connect paths to
|
12345678910>>...23
