Searched full:specific (Results 1 – 25 of 6560) sorted by relevance
12345678910>>...263
| /Linux-v5.4/tools/perf/pmu-events/arch/x86/cascadelakex/ |
| D | other.json | 181 …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…
220 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
233 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
246 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
259 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
272 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
285 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
298 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
[all …]
|
| D | memory.json | 469 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
483 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
497 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
511 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
525 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
539 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
553 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
567 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
581 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
595 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
[all …]
|
| D | cache.json | 393 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
396 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
774 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
788 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
802 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
816 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
830 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
844 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
858 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
872 …core response can be programmed only with a specific pair of event select and counter MSR, and wit…
[all …]
|
| /Linux-v5.4/arch/sparc/include/uapi/asm/ |
| D | ioctls.h | 40 #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 …]
|
| /Linux-v5.4/arch/x86/include/asm/ |
| D | x86_init.h | 13 * struct x86_init_mpparse - platform specific mpparse ops
14 * @mpc_record: platform specific mpc record accounting
15 * @setup_ioapic_ids: platform specific ioapic id override
16 * @mpc_apic_id: platform specific mpc apic id assignment
17 * @smp_read_mpc_oem: platform specific oem mpc table setup
18 * @mpc_oem_pci_bus: platform specific pci bus setup (default NULL)
19 * @mpc_oem_bus_info: platform specific mpc bus info
35 * struct x86_init_resources - platform specific resource related ops
39 * @memory_setup: platform specific memory setup
49 * struct x86_init_irqs - platform specific interrupt setup
[all …]
|
| /Linux-v5.4/drivers/gpu/drm/rockchip/ |
| D | Kconfig | 24 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"
50 This selects support for Rockchip SoC specific extensions
56 bool "Rockchip specific extensions for Innosilicon HDMI"
58 This selects support for Rockchip SoC specific extensions
83 bool "Rockchip specific extensions for RK3066 HDMI"
[all …]
|
| /Linux-v5.4/Documentation/sh/ |
| D | new-machine.txt | 16 of the board-specific code (with the exception of stboards) ended up
17 in arch/sh/kernel/ directly, with board-specific headers ending up in
22 Board-specific code:
29 | | `-- board-specific files
31 | | `-- board-specific files
38 | `-- board-specific headers
40 | `-- board-specific headers
51 `-- cchip-specific files
54 board-specific headers. Thus, include/asm-sh/hd64461 is home to all of the
55 hd64461-specific headers.
[all …]
|
| /Linux-v5.4/arch/arm/mach-imx/ |
| D | Kconfig | 92 Include support for MX21ADS platform. This includes specific
107 Include support for MX27ADS platform. This includes specific
127 Include support for MX27PDK platform. This includes specific
144 This includes specific configurations for the board and its
164 includes specific configurations for the module and its peripherals.
187 Include support for MX31ADS platform. This includes specific
210 specific configurations for the board and its peripherals.
225 Include support for MX31 LITEKIT platform. This includes specific
243 specific configurations for the board and its peripherals.
272 Include support for MX31PDK (3DS) platform. This includes specific
[all …]
|
| /Linux-v5.4/include/linux/mtd/ |
| D | platnand.h | 41 * @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
|
| D | onenand.h | 54 * @readw: [REPLACEABLE] hardware specific function for read short
55 * @writew: [REPLACEABLE] hardware specific function for write short
56 * @command: [REPLACEABLE] hardware specific function for writing
58 * @wait: [REPLACEABLE] hardware specific function for wait on ready
59 * @bbt_wait: [REPLACEABLE] hardware specific function for bbt wait on ready
60 * @unlock_all: [REPLACEABLE] hardware specific function for unlock all
61 * @read_bufferram: [REPLACEABLE] hardware specific function for BufferRAM Area
62 * @write_bufferram: [REPLACEABLE] hardware specific function for BufferRAM Area
63 * @read_word: [REPLACEABLE] hardware specific function for read
65 * @write_word: [REPLACEABLE] hardware specific function for write
[all …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/hwlock/ |
| D | hwlock.txt | 4 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:
|
| /Linux-v5.4/Documentation/arm/samsung/ |
| D | overview.rst | 24 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
|
| /Linux-v5.4/Documentation/hwmon/ |
| D | pmbus-core.rst | 29 device specific extensions in addition to the core PMBus driver, since it is
30 simply unknown what new device specific functionality PMBus device developers
33 To make device specific extensions as scalable as possible, and to avoid having
35 split into core, generic, and device specific code. The core code (in
37 provides support for generic PMBus devices. Device specific code is responsible
38 for device specific initialization and, if needed, maps device specific
52 For this reason, it often makes sense to provide a device specific driver if not
65 The API between core and device specific PMBus code is defined in
84 than 0xff). Support for virtual PMBus commands is device specific and thus has
85 to be implemented in device specific code.
[all …]
|
| /Linux-v5.4/Documentation/driver-api/driver-model/ |
| D | driver.rst | 43 model because the bus they belong to has a bus-specific structure with
44 bus-specific fields that cannot be generalized.
49 completely bus-specific. Defining them as bus-specific entities would
50 sacrifice type-safety, so we keep bus-specific structures around.
52 Bus-specific drivers should include a generic struct device_driver in
53 the definition of the bus-specific driver. Like this::
60 A definition that included bus-specific fields would look like
86 no bus-specific fields (i.e. don't have a bus-specific driver
90 Most drivers, however, will have a bus-specific structure and will
106 define generic callbacks that forward the call to the bus-specific
[all …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/mmc/ |
| D | exynos-dw-mshc.txt | 1 * Samsung Exynos specific extensions to the Synopsys Designware Mobile
7 by synopsys-dw-mshc.txt and the properties used by the Samsung Exynos specific
14 specific extensions.
16 specific extensions.
18 specific extensions.
20 specific extensions.
22 specific extensions.
24 specific extensions having an SMU.
69 The MSHC controller node can be split into two portions, SoC specific and
70 board specific portions as listed below.
|
| D | samsung-sdhci.txt | 8 Required SoC Specific Properties:
15 Required Board Specific Properties:
30 Note: This example shows both SoC specific and board specific properties
32 into SoC specific node and board specific node.
|
| /Linux-v5.4/drivers/scsi/ufs/ |
| D | Kconfig | 87 This selects the Cadence-specific additions to UFSHCD platform driver.
100 tristate "QCOM specific hooks to UFS controller platform driver"
104 This selects the QCOM specific additions to UFSHCD platform driver.
105 UFS host on QCOM needs some vendor specific configuration before
107 specific registers.
113 tristate "Mediatek specific hooks to UFS controller platform driver"
117 This selects the Mediatek specific additions to UFSHCD platform driver.
118 UFS host on Mediatek needs some vendor specific configuration before
120 specific registers.
127 tristate "Hisilicon specific hooks to UFS controller platform driver"
[all …]
|
| /Linux-v5.4/drivers/staging/vc04_services/bcm2835-camera/ |
| D | mmal-msg-format.h | 61 u32 encoding_variant; /* FourCC specifying the specific
66 union mmal_es_specific_format *es; /* Type specific
76 u32 extradata_size; /* Size of the codec specific data */
77 u8 *extradata; /* Codec specific data */
87 u32 encoding_variant; /* FourCC specifying the specific
92 u32 es; /* Type specific
102 u32 extradata_size; /* Size of the codec specific data */
103 u32 extradata; /* Codec specific data */
|
| /Linux-v5.4/drivers/thunderbolt/ |
| D | nhi.h | 34 * struct tb_nhi_ops - NHI specific optional operations
35 * @init: NHI specific initialization
36 * @suspend_noirq: NHI specific suspend_noirq hook
37 * @resume_noirq: NHI specific resume_noirq hook
38 * @runtime_suspend: NHI specific runtime_suspend hook
39 * @runtime_resume: NHI specific runtime_resume hook
40 * @shutdown: NHI specific shutdown
|
| /Linux-v5.4/include/uapi/linux/ |
| D | chio.h | 11 #define CHET_V1 4 /* vendor specific #1 */
12 #define CHET_V2 5 /* vendor specific #2 */
13 #define CHET_V3 6 /* vendor specific #3 */
14 #define CHET_V4 7 /* vendor specific #4 */
22 * query vendor-specific element types
37 int cvp_n1; /* number of vendor specific elems (CHET_V1) */
39 int cvp_n2; /* number of vendor specific elems (CHET_V2) */
41 int cvp_n3; /* number of vendor specific elems (CHET_V3) */
43 int cvp_n4; /* number of vendor specific elems (CHET_V4) */
84 * move the transport element (robot arm) to a specific element.
[all …]
|
| /Linux-v5.4/Documentation/driver-api/rapidio/ |
| D | rapidio.rst | 17 into the kernel similarly to other buses by defining RapidIO-specific device and
21 architecture-specific interfaces that provide support for common RapidIO
38 by a rio_mport data structure. This structure contains master port specific
43 RapidIO master ports are serviced by subsystem specific mport device drivers
46 includes rio_ops data structure which contains pointers to hardware specific
64 data structure, which contains switch specific information such as copy of the
65 routing table and pointers to switch specific functions.
68 specific switch drivers that are designed to provide hardware-specific
83 RapidIO device-specific drivers follow Linux Kernel Driver Model and are
84 intended to support specific RapidIO devices attached to the RapidIO network.
[all …]
|
| /Linux-v5.4/drivers/clk/meson/ |
| D | clk-regmap.h | 16 * @hw: handle between common and hardware-specific interfaces
18 * @data: data specific to the clock type
32 * struct clk_regmap_gate_data - regmap backed gate specific data
36 * @flags: hardware-specific flags
57 * struct clk_regmap_div_data - regmap backed adjustable divider specific data
85 * struct clk_regmap_mux_data - regmap backed multiplexer clock specific data
87 * @hw: handle between common and hardware-specific interfaces
92 * @flags: hardware-specific flags
|
| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | ext-ctrls-fm-tx.rst | 34 step are driver-specific.
114 useconds. Step and range are driver-specific.
118 are driver-specific.
128 range and step are driver-specific.
132 value. The range and step are driver-specific.
136 value. The range and step are driver-specific.
140 useconds value. The range and step are driver-specific.
147 range and step are driver-specific.
151 step are driver-specific.
180 dBuV. Range and step are driver-specific.
[all …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/sifive/ |
| D | sifive-blocks-ip-versioning.txt | 9 IP block-specific DT compatible strings are contained within the HDL,
26 match on these IP block-specific compatible strings.
29 continue to specify an SoC-specific compatible string value, such as
30 "sifive,fu540-c000-uart". This way, if SoC-specific
31 integration-specific bug fixes or workarounds are needed, the kernel
33 IP block-specific compatible string (such as "sifive,uart0") should
|
| /Linux-v5.4/include/net/ |
| D | rtnetlink.h | 36 * @maxtype: Highest device specific netlink attribute number
37 * @policy: Netlink policy for device specific attribute validation
45 * specific netlink attributes
46 * @fill_info: Function to dump device specific netlink attributes
48 * specific statistics
49 * @fill_xstats: Function to dump device specific statistics
56 * dumping device-specific extended link stats
57 * @fill_linkxstats: Function to dump device-specific extended link stats
127 * specific netlink attributes.
128 * @get_link_af_size: Function to calculate size of address family specific
|
12345678910>>...263
