| /linux/drivers/gpu/drm/rockchip/ |
| H A D | Kconfig | 47 bool "Rockchip specific extensions for Analogix DP driver"
53 This selects support for Rockchip SoC specific extensions
64 This selects support for Rockchip SoC specific extensions
70 bool "Rockchip specific extensions for Synopsys DW DP"
73 This selects support for Rockchip SoC specific extensions
79 bool "Rockchip specific extensions for Synopsys DW HDMI"
81 This selects support for Rockchip SoC specific extensions
87 bool "Rockchip specific extensions for Synopsys DW HDMI QP"
90 This selects support for Rockchip SoC specific extensions
95 bool "Rockchip specific extensions for Synopsys DW MIPI DSI"
[all …]
|
| /linux/Documentation/arch/sh/ |
| H A 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/include/linux/mtd/ |
| H A 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
|
| H A 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/Documentation/devicetree/bindings/hwlock/ |
| H A 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/drivers/pinctrl/samsung/ |
| H A D | pinctrl-samsung.h | 143 * @eint_offset: SoC-specific EINT register or interrupt offset of bank.
145 * @eint_con_offset: ExynosAuto SoC-specific EINT control register offset of bank.
146 * @eint_mask_offset: ExynosAuto SoC-specific EINT mask register offset of bank.
147 * @eint_pend_offset: ExynosAuto SoC-specific EINT pend register offset of bank.
148 * @eint_fltcon_offset: GS101 SoC-specific EINT filter config register offset.
178 * @eint_offset: SoC-specific EINT register or interrupt offset of bank.
180 * @eint_con_offset: ExynosAuto SoC-specific EINT register or interrupt offset of bank.
181 * @eint_mask_offset: ExynosAuto SoC-specific EINT mask register offset of bank.
182 * @eint_pend_offset: ExynosAuto SoC-specific EINT pend register offset of bank.
183 * @eint_fltcon_offset: GS101 SoC-specific EINT filter config register offset.
[all …]
|
| /linux/drivers/hid/amd-sfh-hid/hid_descriptor/ |
| H A 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 */
113 /* values specific to human presence sensor */
|
| /linux/drivers/gpio/ |
| H A D | gpio-tangier.h | 24 /* Elkhart Lake specific wake registers */
29 /* Merrifield specific wake registers */
35 * struct tng_wake_regs - Platform specific wake registers
66 * struct tng_gpio_pin_info - Platform specific pinout information
78 * struct tng_gpio_info - Platform specific GPIO and IRQ information
90 * struct tng_gpio - Platform specific private data
97 * @wake_regs: Platform specific wake registers
98 * @pin_info: Platform specific pinout information
99 * @info: Platform specific GPIO and IRQ information
|
| /linux/drivers/leds/ |
| H A D | leds-lp55xx-common.h | 116 * @reg_op_mode : Chip specific OP MODE reg addr
117 * @engine_busy : Chip specific engine busy
119 * @reset : Chip specific reset command
120 * @enable : Chip specific enable command
121 * @prog_mem_base : Chip specific base reg address for chip SMEM programming
122 * @reg_led_pwm_base : Chip specific base reg address for LED PWM conf
123 * @reg_led_current_base : Chip specific base reg address for LED current conf
124 * @reg_master_fader_base : Chip specific base reg address for master fader base
125 * @reg_led_ctrl_base : Chip specific base reg address for LED ctrl base
129 * @post_init_device : Chip specific initialization code
[all …]
|
| /linux/drivers/media/platform/microchip/ |
| H A D | microchip-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/drivers/usb/musb/ |
| H A 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/include/linux/ |
| H A D | intel_pmt_features.h | 24 /* Per Core Performance Telemetry (PCPT) specific masks */
31 /* Per Core Environmental Telemetry (PCET) specific masks */
44 /* Per RMID Performance Telemetry specific masks */
49 /* Accelerator Telemetry specific masks */
53 /* Uncore Telemetry specific masks */
59 /* Crash Log specific masks */
70 /* PeTe Log specific masks */
78 /* TPMI control specific masks */
82 /* Tracing specific masks */
88 /* Per RMID Energy Telemetry specific masks */
|
| H A D | entry-common.h | 42 * arch_ptrace_report_syscall_permit_entry - Architecture specific wrapper for
48 * This allows architecture specific ptrace_report_syscall_permit_entry()
124 * Invoked from architecture specific syscall entry code with interrupts enabled
126 * architecture specific work with the syscall return value preset to -ENOSYS.
161 * Invoked from architecture specific syscall entry code with interrupts
184 * Invoked from architecture specific syscall entry code with interrupts
191 * architecture specific work to be done between the two.
225 * arch_ptrace_report_syscall_exit - Architecture specific ptrace_report_syscall_exit()
229 * This allows architecture specific ptrace_report_syscall_exit()
249 * Do one-time syscall specific work.
[all …]
|
| /linux/include/uapi/linux/ |
| H A 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/drivers/platform/raspberrypi/vchiq-mmal/ |
| H A 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/Documentation/driver-api/rapidio/ |
| H A 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/Documentation/userspace-api/media/v4l/ |
| H A D | ext-ctrls-fm-tx.rst | 28 step are driver-specific.
108 microseconds. Step and range are driver-specific.
112 are driver-specific.
122 range and step are driver-specific.
126 value. The range and step are driver-specific.
130 value. The range and step are driver-specific.
134 microseconds value. The range and step are driver-specific.
141 range and step are driver-specific.
145 step are driver-specific.
167 dBuV. Range and step are driver-specific.
[all …]
|
| /linux/drivers/clk/meson/ |
| H A D | clk-regmap.h | 17 * @hw: handle between common and hardware-specific interfaces
19 * @data: data specific to the clock type
39 * struct clk_regmap_gate_data - regmap backed gate specific data
43 * @flags: hardware-specific flags
64 * struct clk_regmap_div_data - regmap backed adjustable divider specific data
92 * struct clk_regmap_mux_data - regmap backed multiplexer clock specific data
94 * @hw: handle between common and hardware-specific interfaces
99 * @flags: hardware-specific flags
|
| /linux/Documentation/networking/devlink/ |
| H A 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/Documentation/driver-api/usb/ |
| H A 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/Documentation/driver-api/driver-model/ |
| H A D | driver.rst | 42 model because the bus they belong to has a bus-specific structure with
43 bus-specific fields that cannot be generalized.
48 completely bus-specific. Defining them as bus-specific entities would
49 sacrifice type-safety, so we keep bus-specific structures around.
51 Bus-specific drivers should include a generic struct device_driver in
52 the definition of the bus-specific driver. Like this::
59 A definition that included bus-specific fields would look like
85 no bus-specific fields (i.e. don't have a bus-specific driver
89 Most drivers, however, will have a bus-specific structure and will
105 define generic callbacks that forward the call to the bus-specific
[all …]
|
| /linux/include/linux/device-id/ |
| H A D | usb.h | 40 * or be vendor-specific. Device classes specify behavior of all
46 * or be vendor-specific. Interface classes specify behavior only
51 * fixed interface numbers to differentiate between vendor-specific
65 * one or more specific products, or will identify a class of products
66 * which have agreed to behave the same. You should put the more specific
68 * record quirks of specific products.
74 /* Used for product specific matches; range is inclusive */
90 /* Used for vendor-specific interface matches */
|
| /linux/Documentation/devicetree/bindings/sifive/ |
| H A 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/Documentation/driver-api/ |
| H A D | vfio-pci-device-specific-driver-acceptance.rst | 3 Acceptance criteria for vfio-pci device specific driver variants
11 vfio-pci driver does include some device specific support, further
12 extensions for yet more advanced device specific features are not
15 requiring device specific knowledge, ex. saving and loading device
18 In support of such features, it's expected that some device specific
29 documentation for reviewers to understand the device specific
|
| /linux/arch/x86/include/asm/ |
| H A D | cpu_device_id.h | 39 * Declare drivers belonging to specific x86 CPUs
64 * @_data: Driver specific data or NULL. The internal storage
91 * @data: Driver specific data or NULL. The internal storage
104 * @data: Driver specific data or NULL. The internal storage
115 * @data: Driver specific data or NULL. The internal storage
129 * @data: Driver specific data or NULL. The internal storage
142 * @data: Driver specific data or NULL. The internal storage
153 * @data: Driver specific data or NULL. The internal storage
168 * @data: Driver specific data or NULL. The internal storage
181 * @data: Driver specific data or NULL. The internal storage
[all …]
|