| /Linux-v5.15/drivers/gpu/drm/amd/display/modules/hdcp/ |
| D | hdcp2_transition.c | 68 /* 1A-08: consider ake timeout a failure */ in mod_hdcp_hdcp2_transition()
84 * 1A-09: consider invalid ake cert a failure in mod_hdcp_hdcp2_transition()
85 * 1A-10: consider receiver id listed in SRM a failure in mod_hdcp_hdcp2_transition()
115 /* 1A-11-3: consider h' timeout a failure */ in mod_hdcp_hdcp2_transition()
135 /* 1A-12: consider pairing info timeout in mod_hdcp_hdcp2_transition()
147 /* 1A-11-1: consider invalid h' a failure */ in mod_hdcp_hdcp2_transition()
167 /* 1A-11-2: consider h' timeout a failure */ in mod_hdcp_hdcp2_transition()
179 /* 1A-11-1: consider invalid h' a failure */ in mod_hdcp_hdcp2_transition()
194 * 1A-05: consider disconnection after LC init a failure in mod_hdcp_hdcp2_transition()
195 * 1A-13-1: consider invalid l' a failure in mod_hdcp_hdcp2_transition()
[all …]
|
| D | hdcp1_transition.c | 59 /* 1A-05: consider invalid bksv a failure */ in mod_hdcp_hdcp1_transition()
73 /* 1A-06: consider invalid r0' a failure */ in mod_hdcp_hdcp1_transition()
74 /* 1A-08: consider bksv listed in SRM a failure */ in mod_hdcp_hdcp1_transition()
97 /* 1A-07: consider invalid ri' a failure */ in mod_hdcp_hdcp1_transition()
98 /* 1A-07a: consider read ri' not returned a failure */ in mod_hdcp_hdcp1_transition()
132 /* 1B-06: consider MAX_CASCADE_EXCEEDED a failure */ in mod_hdcp_hdcp1_transition()
133 /* 1B-05: consider MAX_DEVS_EXCEEDED a failure */ in mod_hdcp_hdcp1_transition()
134 /* 1B-04: consider invalid v' a failure */ in mod_hdcp_hdcp1_transition()
185 /* 1A-05: consider invalid bksv a failure */ in mod_hdcp_hdcp1_dp_transition()
218 * 1A-06: consider invalid r0' a failure in mod_hdcp_hdcp1_dp_transition()
[all …]
|
| /Linux-v5.15/Documentation/process/ |
| D | botching-up-ioctls.rst | 142 performance counter sampling instructions) consider exposing those also.
159 * Consider ditching any synchronous wait ioctls with timeouts and just deliver
177 lifetime of a file descriptor. Consider using a 1:1 mapping if your resource
197 of objects, but consider using inode numbers on your shared file descriptors
214 * Consider other interfaces than ioctls. A sysfs attribute is much better for
|
| /Linux-v5.15/scripts/coccinelle/misc/ |
| D | orplus.cocci | 64 cocci.print_main("sum of probable bitmasks, consider |",p)
70 msg = "WARNING: sum of probable bitmasks, consider |"
|
| /Linux-v5.15/include/linux/ |
| D | instrumentation.h | 21 * When the value is greater than 0, we consider instrumentation allowed.
42 * If we then consider the sum of the !cond path, we'll see that the call to
|
| /Linux-v5.15/drivers/media/test-drivers/vidtv/ |
| D | vidtv_demod.h | 23 * @cnr_ok: S/N threshold to consider the signal as OK. Below that, there's
25 * @cnr_good: S/N threshold to consider the signal strong.
|
| /Linux-v5.15/Documentation/filesystems/ |
| D | directory-locking.rst | 90 Now consider the minimal deadlock. Each process is blocked on
92 consider the set of contended locks. First of all, filesystem lock is
115 Consider the object blocking the cross-directory rename. One
|
| D | idmappings.rst | 101 To see whether the simple formulas above work, consider the following two
176 For instance, consider a file that is stored on disk by a filesystem as being
204 the same kernel id in their kernel idmapsets. For example, consider the
523 idmapping it would be trivial. So we only consider a filesystem with an
540 workloads. For a more complex but common example, consider two containers
572 Or consider another increasingly popular example. Some service managers such as
651 Note that these two functions invert each other. Consider the following
874 Consider our previous example where a user has their home directory on portable
982 Let's consider ``mapped_fs*id()`` first. This function translates the
|
| /Linux-v5.15/tools/perf/Documentation/ |
| D | perf-top.txt | 152 Only consider symbols in these dsos. This option will affect the
156 Only consider symbols in these comms. This option will affect the
160 Only consider these symbols. This option will affect the
297 Only consider events after this event is found.
309 Start perf top and ask it to only consider the cycles events when a
|
| D | perf-diff.txt | 43 Only consider symbols in these dsos. CSV that understands
49 Only consider symbols in these comms. CSV that understands
55 Only consider these symbols. CSV that understands
|
| /Linux-v5.15/Documentation/devicetree/bindings/ |
| D | writing-bindings.rst | 25 defined in the DT Spec. If there isn't one, consider adding it.
47 - DO use a vendor prefix on device specific property names. Consider if
|
| /Linux-v5.15/Documentation/arm64/ |
| D | perf.rst | 40 For a VHE host this attribute is ignored as we consider the host kernel to
43 For a non-VHE host this attribute will exclude EL2 as we consider the
|
| /Linux-v5.15/drivers/block/paride/ |
| D | Transition-notes | 7 Consider the sequnce of these events. A can not be preceded by
23 consider the following area:
58 Proof: consider the first moment when the above is not true.
|
| /Linux-v5.15/scripts/coccinelle/api/ |
| D | vma_pages.cocci | 51 msg="WARNING: Consider using vma_pages helper on %s" % (x)
59 msg="WARNING: Consider using vma_pages helper on %s" % (x)
|
| /Linux-v5.15/Documentation/staging/ |
| D | speculation.rst | 21 checks to be ignored by code which is speculatively executed. Consider the
48 result in sensitive information being leaked. Consider the following
|
| /Linux-v5.15/Documentation/scheduler/ |
| D | sched-capacity.rst | 58 Consider an hypothetical dual-core asymmetric CPU capacity system where
93 OPPs. Consider the same CPUs as above (i.e. same work_per_hz()) with:
152 directly impacted by the current OPP the CPU is running at. Consider running a
162 Now, consider running the *same* workload at frequency F/2::
187 Consider the system described in 1.3.2., i.e.::
376 sleeps, if at all - it thus rarely wakes up, if at all. Consider::
|
| /Linux-v5.15/arch/s390/include/asm/fpu/ |
| D | api.h | 6 * Consider these guidelines before using in-kernel FPU functions:
12 * use with the KERNEL_VXR_* constants. Consider these usage guidelines:
|
| /Linux-v5.15/drivers/net/wireless/intel/iwlwifi/fw/api/ |
| D | filter.h | 72 * @BCAST_FILTER_FRAME_TYPE_ALL: consider all frames.
73 * @BCAST_FILTER_FRAME_TYPE_IPV4: consider only ipv4 frames
|
| /Linux-v5.15/drivers/nfc/st-nci/ |
| D | st-nci.h | 66 * are activated. It does not consider any NFC_ATTR_VENDOR_DATA.
68 * It does not consider any NFC_ATTR_VENDOR_DATA.
|
| /Linux-v5.15/arch/arm/probes/kprobes/ |
| D | checkers-thumb.c | 52 /* Only consider U == 0 and P == 1: strx rx, [sp, #-<imm>] */ in t32_check_stack()
60 * Only consider U == 0 and P == 1. in t32_check_stack()
|
| /Linux-v5.15/arch/x86/kernel/ |
| D | setup_percpu.c | 58 * pcpu_need_numa - determine percpu allocation needs to consider NUMA
61 * there is no reason to consider NUMA. This function determines
62 * whether percpu allocation should consider NUMA or not.
|
| /Linux-v5.15/Documentation/doc-guide/ |
| D | contributing.rst | 166 have fixed a few, please consider moving on to more advanced tasks, leaving
180 As with any patch to any project, please consider whether your change is
191 Whenever you are working with a document, please consider whether it is
219 this information with caution, and please consider sending patches
|
| /Linux-v5.15/drivers/nfc/st21nfca/ |
| D | st21nfca.h | 75 * are activated. It does not consider any NFC_ATTR_VENDOR_DATA.
77 * It does not consider any NFC_ATTR_VENDOR_DATA.
|
| /Linux-v5.15/kernel/irq/ |
| D | autoprobe.c | 90 /* It triggered already - consider it spurious. */ in probe_irq_on()
107 * @val: mask of interrupts to consider
|
| /Linux-v5.15/drivers/gpu/drm/amd/display/ |
| D | TODO | 74 a few indirections, and consider removing entirely and using the
77 14. core/dc_debug.c, consider switching to the atomic state debug helpers and
|
