Home
last modified time | relevance | path

Searched full:specific (Results 1 – 25 of 10184) sorted by relevance

12345678910>>...408

/kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/cascadelakex/
Dother.json11 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
24 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
37 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
50 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
63 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
76 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
89 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
102 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
115 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
128 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
[all …]
Dmemory.json11 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
24 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
37 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
51 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
65 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
79 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
92 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
106 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
120 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
134 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
[all …]
Dcache.json12 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
26 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
40 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
54 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
78 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
92 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
118 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
132 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
166 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
180 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
[all …]
/kernel/linux/linux-6.6/drivers/ufs/host/
DKconfig45 This selects the Cadence-specific additions to UFSHCD platform driver.
58 tristate "QCOM specific hooks to UFS controller platform driver"
64 This selects the QCOM specific additions to UFSHCD platform driver.
65 UFS host on QCOM needs some vendor specific configuration before
67 specific registers.
73 tristate "Mediatek specific hooks to UFS controller platform driver"
79 This selects the Mediatek specific additions to UFSHCD platform driver.
80 UFS host on Mediatek needs some vendor specific configuration before
82 specific registers.
89 tristate "Hisilicon specific hooks to UFS controller platform driver"
[all …]
/kernel/linux/linux-5.10/arch/sparc/include/uapi/asm/
Dioctls.h40 #define __TIOCHPCL _IO('t', 2) /* SunOS Specific */
41 #define __TIOCMODG _IOR('t', 3, int) /* SunOS Specific */
42 #define __TIOCMODS _IOW('t', 4, int) /* SunOS Specific */
43 #define __TIOCGETP _IOR('t', 8, struct sgttyb) /* SunOS Specific */
44 #define __TIOCSETP _IOW('t', 9, struct sgttyb) /* SunOS Specific */
45 #define __TIOCSETN _IOW('t', 10, struct sgttyb) /* SunOS Specific */
48 #define __TIOCFLUSH _IOW('t', 16, int) /* SunOS Specific */
49 #define __TIOCSETC _IOW('t', 17, struct tchars) /* SunOS Specific */
50 #define __TIOCGETC _IOR('t', 18, struct tchars) /* SunOS Specific */
51 #define __TIOCTCNTL _IOW('t', 32, int) /* SunOS Specific */
[all …]
/kernel/linux/linux-6.6/arch/sparc/include/uapi/asm/
Dioctls.h40 #define __TIOCHPCL _IO('t', 2) /* SunOS Specific */
41 #define __TIOCMODG _IOR('t', 3, int) /* SunOS Specific */
42 #define __TIOCMODS _IOW('t', 4, int) /* SunOS Specific */
43 #define __TIOCGETP _IOR('t', 8, struct sgttyb) /* SunOS Specific */
44 #define __TIOCSETP _IOW('t', 9, struct sgttyb) /* SunOS Specific */
45 #define __TIOCSETN _IOW('t', 10, struct sgttyb) /* SunOS Specific */
48 #define __TIOCFLUSH _IOW('t', 16, int) /* SunOS Specific */
49 #define __TIOCSETC _IOW('t', 17, struct tchars) /* SunOS Specific */
50 #define __TIOCGETC _IOR('t', 18, struct tchars) /* SunOS Specific */
51 #define __TIOCTCNTL _IOW('t', 32, int) /* SunOS Specific */
[all …]
/kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/skylakex/
Dmemory.json11 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
24 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
47 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
60 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
73 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
95 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
118 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
141 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
154 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
167 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
[all …]
Dcache.json11 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
34 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
67 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
112 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
125 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
138 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
194 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
207 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
253 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
266 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
[all …]
/kernel/linux/linux-5.10/arch/x86/include/asm/
Dx86_init.h16 * struct x86_init_mpparse - platform specific mpparse ops
17 * @setup_ioapic_ids: platform specific ioapic id override
28 * struct x86_init_resources - platform specific resource related ops
32 * @memory_setup: platform specific memory setup
42 * struct x86_init_irqs - platform specific interrupt setup
59 * struct x86_init_oem - oem platform specific customizing functions
60 * @arch_setup: platform specific architecture setup
61 * @banner: print a platform specific banner
69 * struct x86_init_paging - platform specific paging functions
70 * @pagetable_init: platform specific paging initialization call to setup
[all …]
/kernel/linux/linux-6.6/arch/x86/include/asm/
Dx86_init.h16 * struct x86_init_mpparse - platform specific mpparse ops
17 * @setup_ioapic_ids: platform specific ioapic id override
28 * struct x86_init_resources - platform specific resource related ops
32 * @memory_setup: platform specific memory setup
33 * @dmi_setup: platform specific DMI setup
43 * struct x86_init_irqs - platform specific interrupt setup
60 * struct x86_init_oem - oem platform specific customizing functions
61 * @arch_setup: platform specific architecture setup
62 * @banner: print a platform specific banner
70 * struct x86_init_paging - platform specific paging functions
[all …]
/kernel/linux/linux-5.10/drivers/gpu/drm/rockchip/
DKconfig24 bool "Rockchip specific extensions for Analogix DP driver"
26 This selects support for Rockchip SoC specific extensions
34 This selects support for Rockchip SoC specific extensions
40 bool "Rockchip specific extensions for Synopsys DW HDMI"
42 This selects support for Rockchip SoC specific extensions
48 bool "Rockchip specific extensions for Synopsys DW MIPI DSI"
51 This selects support for Rockchip SoC specific extensions
57 bool "Rockchip specific extensions for Innosilicon HDMI"
59 This selects support for Rockchip SoC specific extensions
84 bool "Rockchip specific extensions for RK3066 HDMI"
[all …]
/kernel/linux/linux-6.6/drivers/gpu/drm/rockchip/
DKconfig38 bool "Rockchip specific extensions for Analogix DP driver"
43 This selects support for Rockchip SoC specific extensions
53 This selects support for Rockchip SoC specific extensions
59 bool "Rockchip specific extensions for Synopsys DW HDMI"
61 This selects support for Rockchip SoC specific extensions
67 bool "Rockchip specific extensions for Synopsys DW MIPI DSI"
70 This selects support for Rockchip SoC specific extensions
76 bool "Rockchip specific extensions for Innosilicon HDMI"
78 This selects support for Rockchip SoC specific extensions
103 bool "Rockchip specific extensions for RK3066 HDMI"
[all …]
/kernel/linux/linux-5.10/lib/crypto/
DKconfig14 Declares whether the architecture provides an arch-specific
23 fallback, e.g., for SIMD implementations. If no arch specific
30 Declares whether the architecture provides an arch-specific
39 fallback, e.g., for SIMD implementations. If no arch specific
50 by either the generic implementation or an arch-specific one, if one
56 Declares whether the architecture provides an arch-specific
65 fallback, e.g., for SIMD implementations. If no arch specific
76 fulfilled by either the generic implementation or an arch-specific
92 Declares whether the architecture provides an arch-specific
101 fallback, e.g., for SIMD implementations. If no arch specific
[all …]
/kernel/linux/linux-6.6/lib/crypto/
DKconfig26 Declares whether the architecture provides an arch-specific
35 fallback, e.g., for SIMD implementations. If no arch specific
42 Declares whether the architecture provides an arch-specific
52 fallback, e.g., for SIMD implementations. If no arch specific
62 by either the generic implementation or an arch-specific one, if one
68 Declares whether the architecture provides an arch-specific
77 fallback, e.g., for SIMD implementations. If no arch specific
88 fulfilled by either the generic implementation or an arch-specific
104 Declares whether the architecture provides an arch-specific
113 fallback, e.g., for SIMD implementations. If no arch specific
[all …]
/kernel/linux/linux-6.6/Documentation/arch/sh/
Dnew-machine.rst18 of the board-specific code (with the exception of stboards) ended up
19 in arch/sh/kernel/ directly, with board-specific headers ending up in
24 Board-specific code::
31 | | `-- board-specific files
33 | | `-- board-specific files
40 | `-- board-specific headers
42 | `-- board-specific headers
54 `-- cchip-specific files
57 board-specific headers. Thus, include/asm-sh/hd64461 is home to all of the
58 hd64461-specific headers.
[all …]
/kernel/linux/linux-5.10/Documentation/sh/
Dnew-machine.rst18 of the board-specific code (with the exception of stboards) ended up
19 in arch/sh/kernel/ directly, with board-specific headers ending up in
24 Board-specific code::
31 | | `-- board-specific files
33 | | `-- board-specific files
40 | `-- board-specific headers
42 | `-- board-specific headers
54 `-- cchip-specific files
57 board-specific headers. Thus, include/asm-sh/hd64461 is home to all of the
58 hd64461-specific headers.
[all …]
/kernel/linux/linux-5.10/include/linux/
Dentry-common.h76 * arch_check_user_regs - Architecture specific sanity check for user mode regs
80 * specific code.
99 * architecture specific code.
116 * Invoked from architecture specific syscall entry code with interrupts
123 * This is invoked when there is extra architecture specific functionality
134 * Invoked from architecture specific syscall entry code with interrupts
136 * architecture specific work.
159 * Invoked from architecture specific syscall entry code with interrupts
176 * Defaults to local_irq_enable(). Can be supplied by architecture specific
191 * Defaults to local_irq_disable(). Can be supplied by architecture specific
[all …]
/kernel/linux/linux-5.10/drivers/scsi/ufs/
DKconfig88 This selects the Cadence-specific additions to UFSHCD platform driver.
101 tristate "QCOM specific hooks to UFS controller platform driver"
106 This selects the QCOM specific additions to UFSHCD platform driver.
107 UFS host on QCOM needs some vendor specific configuration before
109 specific registers.
115 tristate "Mediatek specific hooks to UFS controller platform driver"
119 This selects the Mediatek specific additions to UFSHCD platform driver.
120 UFS host on Mediatek needs some vendor specific configuration before
122 specific registers.
129 tristate "Hisilicon specific hooks to UFS controller platform driver"
[all …]
/kernel/linux/linux-5.10/include/linux/mtd/
Dplatnand.h41 * @probe: platform specific function to probe/setup hardware
42 * @remove: platform specific function to remove/teardown hardware
43 * @dev_ready: platform specific function to read ready/busy pin
44 * @select_chip: platform specific chip select function
45 * @cmd_ctrl: platform specific function for controlling
47 * @write_buf: platform specific function for write buffer
48 * @read_buf: platform specific function for read buffer
49 * @priv: private data to transport driver specific settings
65 * struct platform_nand_data - container structure for platform-specific data
/kernel/linux/linux-6.6/include/linux/mtd/
Dplatnand.h41 * @probe: platform specific function to probe/setup hardware
42 * @remove: platform specific function to remove/teardown hardware
43 * @dev_ready: platform specific function to read ready/busy pin
44 * @select_chip: platform specific chip select function
45 * @cmd_ctrl: platform specific function for controlling
47 * @write_buf: platform specific function for write buffer
48 * @read_buf: platform specific function for read buffer
49 * @priv: private data to transport driver specific settings
65 * struct platform_nand_data - container structure for platform-specific data
/kernel/linux/linux-6.6/include/linux/
Dentry-common.h66 * arch_enter_from_user_mode - Architecture specific sanity check for user mode regs
70 * specific code.
92 * Invoked from architecture specific syscall entry code with interrupts
97 * This is invoked when there is architecture specific functionality to be
107 * Invoked from architecture specific syscall entry code with interrupts
115 * This is invoked when there is extra architecture specific functionality
126 * Invoked from architecture specific syscall entry code with interrupts
128 * architecture specific work.
151 * Invoked from architecture specific syscall entry code with interrupts
168 * Defaults to local_irq_enable(). Can be supplied by architecture specific
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/hwlock/
Dhwlock.txt4 Generic bindings that are common to all the hwlock platform specific driver
7 Please also look through the individual platform specific hwlock binding
8 documentations for identifying any additional properties specific to that
16 specific lock.
21 Consumers that require specific hwlock(s) should specify them using the
34 use the hwlock-names to match and get a specific hwlock.
37 1. Example of a node using a single specific hwlock:
49 2. Example of a node using multiple specific hwlocks:
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/hwlock/
Dhwlock.txt4 Generic bindings that are common to all the hwlock platform specific driver
7 Please also look through the individual platform specific hwlock binding
8 documentations for identifying any additional properties specific to that
16 specific lock.
21 Consumers that require specific hwlock(s) should specify them using the
34 use the hwlock-names to match and get a specific hwlock.
37 1. Example of a node using a single specific hwlock:
49 2. Example of a node using multiple specific hwlocks:
/kernel/linux/linux-5.10/Documentation/arm/samsung/
Doverview.rst24 deals with the architecture and drivers specific to these devices.
27 on the implementation details and specific support.
37 - S5PC110 specific default configuration
39 - S5PV210 specific default configuration
46 several platform directories and then the machine specific directories
51 specific information. It contains the base clock, GPIO and device definitions
54 plat-s3c24xx is for s3c24xx specific builds, see the S3C24XX docs.
56 plat-s5p is for s5p specific builds, and contains common support for the
57 S5P specific systems. Not all S5Ps use all the features in this directory
/kernel/linux/linux-6.6/drivers/hid/amd-sfh-hid/hid_descriptor/
Damd_sfh_hid_desc.h39 /* properties specific to this sensor */
47 /* values specific to this sensor */
57 /* properties specific to this sensor */
65 /* values specific to this sensor */
73 /*properties specific to this sensor */
92 /* properties specific to this sensor */
100 /* values specific to this sensor */
110 /* values specific to human presence sensor */

12345678910>>...408