Searched full:specific (Results 1 – 25 of 5597) sorted by relevance
12345678910>>...224
| /Linux-v6.1/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-v6.1/drivers/ufs/host/ |
| D | Kconfig | 45 This selects the Cadence-specific additions to UFSHCD platform driver.
58 tristate "QCOM specific hooks to UFS controller platform driver"
63 This selects the QCOM specific additions to UFSHCD platform driver.
64 UFS host on QCOM needs some vendor specific configuration before
66 specific registers.
72 tristate "Mediatek specific hooks to UFS controller platform driver"
77 This selects the Mediatek specific additions to UFSHCD platform driver.
78 UFS host on Mediatek needs some vendor specific configuration before
80 specific registers.
87 tristate "Hisilicon specific hooks to UFS controller platform driver"
[all …]
|
| /Linux-v6.1/arch/x86/include/asm/ |
| D | x86_init.h | 16 * 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 …]
|
| /Linux-v6.1/lib/crypto/ |
| D | Kconfig | 17 Declares whether the architecture provides an arch-specific
26 fallback, e.g., for SIMD implementations. If no arch specific
33 Declares whether the architecture provides an arch-specific
43 fallback, e.g., for SIMD implementations. If no arch specific
53 by either the generic implementation or an arch-specific one, if one
59 Declares whether the architecture provides an arch-specific
68 fallback, e.g., for SIMD implementations. If no arch specific
79 fulfilled by either the generic implementation or an arch-specific
95 Declares whether the architecture provides an arch-specific
104 fallback, e.g., for SIMD implementations. If no arch specific
[all …]
|
| /Linux-v6.1/drivers/gpu/drm/rockchip/ |
| D | Kconfig | 38 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 …]
|
| /Linux-v6.1/Documentation/sh/ |
| D | new-machine.rst | 18 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 …]
|
| /Linux-v6.1/include/linux/ |
| D | entry-common.h | 66 * 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 …]
|
| /Linux-v6.1/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-v6.1/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-v6.1/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-v6.1/drivers/hid/amd-sfh-hid/hid_descriptor/ |
| D | amd_sfh_hid_desc.h | 39 /* 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 */
|
| /Linux-v6.1/drivers/usb/musb/ |
| D | musb_io.h | 19 * @ep_offset: platform specific function to get end point offset
20 * @ep_select: platform specific function to select end point
21 * @fifo_offset: platform specific function to get fifo offset
22 * @read_fifo: platform specific function to read fifo
23 * @write_fifo: platform specific function to write fifo
24 * @busctl_offset: platform specific function to get busctl offset
25 * @get_toggle: platform specific function to get toggle
26 * @set_toggle: platform specific function to set toggle
|
| /Linux-v6.1/drivers/media/platform/atmel/ |
| D | atmel-isc-regs.h | 226 /* Offset for CSC register specific to sama5d2 product */
228 /* Offset for CSC register specific to sama7g5 product */
252 /* Offset for CBC register specific to sama5d2 product */
254 /* Offset for CBC register specific to sama7g5 product */
276 /* Offset for SUB422 register specific to sama5d2 product */
278 /* Offset for SUB422 register specific to sama7g5 product */
284 /* Offset for SUB420 register specific to sama5d2 product */
286 /* Offset for SUB420 register specific to sama7g5 product */
291 /* Offset for RLP register specific to sama5d2 product */
293 /* Offset for RLP register specific to sama7g5 product */
[all …]
|
| /Linux-v6.1/include/uapi/linux/ |
| D | chio.h | 14 #define CHET_V1 4 /* vendor specific #1 */
15 #define CHET_V2 5 /* vendor specific #2 */
16 #define CHET_V3 6 /* vendor specific #3 */
17 #define CHET_V4 7 /* vendor specific #4 */
25 * query vendor-specific element types
40 int cvp_n1; /* number of vendor specific elems (CHET_V1) */
42 int cvp_n2; /* number of vendor specific elems (CHET_V2) */
44 int cvp_n3; /* number of vendor specific elems (CHET_V3) */
46 int cvp_n4; /* number of vendor specific elems (CHET_V4) */
87 * move the transport element (robot arm) to a specific element.
[all …]
|
| /Linux-v6.1/drivers/staging/vc04_services/vchiq-mmal/ |
| D | mmal-msg-format.h | 63 u32 encoding_variant; /* FourCC specifying the specific
68 union mmal_es_specific_format *es; /* Type specific
78 u32 extradata_size; /* Size of the codec specific data */
79 u8 *extradata; /* Codec specific data */
89 u32 encoding_variant; /* FourCC specifying the specific
94 u32 es; /* Type specific
104 u32 extradata_size; /* Size of the codec specific data */
105 u32 extradata; /* Codec specific data */
|
| /Linux-v6.1/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-v6.1/drivers/net/wireless/intel/iwlwifi/ |
| D | iwl-drv.h | 33 * bus specific files (transport files). This is the code that is common among
42 * 1) The bus specific component is called from module_init
43 * 2) The bus specific component registers the bus driver
45 * 4) The bus specific component configures the bus
46 * 5) The bus specific component calls to the drv bus agnostic part
62 * specific system flows implementations. For example, the bus specific probe
73 * Stop the driver. This should be called by bus specific system flows
74 * implementations. For example, the bus specific remove function should first
|
| /Linux-v6.1/Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-fm-tx.rst | 27 step are driver-specific.
107 useconds. Step and range are driver-specific.
111 are driver-specific.
121 range and step are driver-specific.
125 value. The range and step are driver-specific.
129 value. The range and step are driver-specific.
133 useconds value. The range and step are driver-specific.
140 range and step are driver-specific.
144 step are driver-specific.
173 dBuV. Range and step are driver-specific.
[all …]
|
| /Linux-v6.1/drivers/pci/controller/dwc/ |
| D | Kconfig | 32 host-specific features PCI_DRA7XX_HOST must be selected and in order
33 to enable device-specific features PCI_DRA7XX_EP must be selected.
47 host-specific features PCI_DRA7XX_HOST must be selected and in order
48 to enable device-specific features PCI_DRA7XX_EP must be selected.
64 host-specific features PCIE_DW_PLAT_HOST must be selected and in
65 order to enable device-specific features PCI_DW_PLAT_EP must be
79 host-specific features PCIE_DW_PLAT_HOST must be selected and in
80 order to enable device-specific features PCI_DW_PLAT_EP must be
178 PCIe controller uses the DesignWare core plus Qualcomm-specific
189 plus Qualcomm-specific hardware wrappers.
[all …]
|
| /Linux-v6.1/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-v6.1/Documentation/networking/devlink/ |
| D | devlink-dpipe.rst | 46 modeled as a graph of match/action tables. Each table represents a specific
75 the actual content of a specific table.
77 The hardware pipeline is not port specific, but rather describes the whole
85 is hardware counting for a specific table.
111 and specific ASIC metadata. The protocol headers should be declared in the
112 ``devlink`` core API. On the other hand ASIC meta data is driver specific
113 and should be defined in the driver. Additionally, each driver-specific
114 devlink documentation file should document the driver-specific ``dpipe``
130 * ``field_exact``: Exact match on a specific field.
131 * ``field_exact_mask``: Exact match on a specific field after masking.
[all …]
|
| /Linux-v6.1/Documentation/driver-api/usb/ |
| D | typec_bus.rst | 10 The communication is SVID (Standard or Vendor ID) specific, i.e. specific for
29 specific commands from the alternate mode drivers to the partner, and from the
30 partners to the alternate mode drivers. No direct SVID specific communication is
47 will be used to deliver all the SVID specific commands from the partner to the
49 the SVID specific commands to each other using :c:func:`typec_altmode_vdm()`.
51 If the communication with the partner using the SVID specific commands results
54 passes the negotiated SVID specific pin configuration value to the function as
58 NOTE: The SVID specific pin configuration values must always start from
67 An example of working definitions for SVID specific pin configurations would
|
| /Linux-v6.1/drivers/clk/meson/ |
| D | clk-regmap.h | 16 * @hw: handle between common and hardware-specific interfaces
18 * @data: data specific to the clock type
35 * struct clk_regmap_gate_data - regmap backed gate specific data
39 * @flags: hardware-specific flags
60 * struct clk_regmap_div_data - regmap backed adjustable divider specific data
88 * struct clk_regmap_mux_data - regmap backed multiplexer clock specific data
90 * @hw: handle between common and hardware-specific interfaces
95 * @flags: hardware-specific flags
|
| /Linux-v6.1/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
|
12345678910>>...224
