Lines Matching +full:test +full:- +full:rules

1 /* SPDX-License-Identifier: MIT */
28  * Macros to encode rules to match against platform, IP version, stepping, etc.
29  * Shouldn't be used directly - see XE_RTP_RULES()
51  * XE_RTP_RULE_PLATFORM - Create rule matching platform
60  * XE_RTP_RULE_SUBPLATFORM - Create rule matching platform and sub-platform
62  * @sub_: sub-platform to match
70  * XE_RTP_RULE_GRAPHICS_STEP - Create rule matching graphics stepping
83  * XE_RTP_RULE_MEDIA_STEP - Create rule matching media stepping
96  * XE_RTP_RULE_ENGINE_CLASS - Create rule matching an engine class
105  * XE_RTP_RULE_FUNC - Create rule using callback function for match
119  * XE_RTP_RULE_GRAPHICS_VERSION - Create rule matching graphics version
129  * XE_RTP_RULE_GRAPHICS_VERSION_RANGE - Create rule matching a range of graphics version
143  * XE_RTP_RULE_GRAPHICS_VERSION_ANY_GT - Create rule matching graphics version on any GT
157  * XE_RTP_RULE_MEDIA_VERSION - Create rule matching media version
167  * XE_RTP_RULE_MEDIA_VERSION_RANGE - Create rule matching a range of media version
181  * XE_RTP_RULE_MEDIA_VERSION_ANY_GT - Create rule matching media version on any GT
195  * XE_RTP_RULE_IS_INTEGRATED - Create a rule matching integrated graphics devices
203  * XE_RTP_RULE_IS_DISCRETE - Create a rule matching discrete graphics devices
211  * XE_RTP_RULE_OR - Create an OR condition for rtp rules
213  * RTP rules are AND'ed when evaluated and all of them need to match.
214  * XE_RTP_RULE_OR allows to create set of rules where any of them matching is
217  * .. code-block:: c
221  *		{ XE_RTP_NAME("test-entry"),
232  * XE_RTP_ACTION_WR - Helper to write a value to the register, overriding all
248  * XE_RTP_ACTION_SET - Set bits from @val_ in the register.
306  * XE_RTP_ACTION_WHITELIST - Add register to userspace whitelist
308  * @val_: Whitelist-specific flags to set
322  * XE_RTP_NAME - Helper to set the name in xe_rtp_entry
323  * @s_: Name describing this rule, often a HW-specific number
330  * XE_RTP_ENTRY_FLAG - Helper to add multiple flags to a struct xe_rtp_entry_sr
336  * .. code-block:: c
340  *		{ XE_RTP_NAME("test-entry"),
352  * XE_RTP_ACTION_FLAG - Helper to add multiple flags to a struct xe_rtp_action
358  * .. code-block:: c
362  *		{ XE_RTP_NAME("test-entry"),
374  * XE_RTP_RULES - Helper to set multiple rules to a struct xe_rtp_entry_sr entry
375  * @...: Rules
377  * At least one rule is needed and up to 12 are supported. Multiple rules are
378  * AND'ed together, i.e. all the rules must evaluate to true for the entry to
379  * be processed. See XE_RTP_MATCH_* for the possible match rules. Example:
381  * .. code-block:: c
385  *		{ XE_RTP_NAME("test-entry"),
394 	.rules = (const struct xe_rtp_rule[]) {					\
399  * XE_RTP_ACTIONS - Helper to set multiple actions to a struct xe_rtp_entry_sr
405  * .. code-block:: c
409  *		{ XE_RTP_NAME("test-entry"),
441  * xe_rtp_match_even_instance - Match if engine instance is even
451  * xe_rtp_match_first_render_or_compute - Match if it's first render or compute
457  * Registers on the render reset domain need to have their values re-applied
469  * xe_rtp_match_first_gslice_fused_off - Match when first gslice is fused off
480  * xe_rtp_match_not_sriov_vf - Match when not on SR-IOV VF device