| /linux/drivers/gpu/drm/amd/display/modules/hdcp/ |
| H A 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 …]
|
| H A 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/Documentation/process/ |
| H A 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
|
| H A D | handling-regressions.rst | 77 to the list. Consider checking the list archives beforehand, if the reporter
81 When doing either, consider making the Linux kernel regression tracking bot
168 * Do not consider regressions from the current cycle as something that can wait
197 * Always consider reverting the culprit, as it's often the quickest and least
207 * Consider CCing Linus on discussions or patch review, if a regression seems
212 * For urgent regressions, consider asking Linus to pick up the fix straight
219 CC; in it, summarize the situation while asking him to consider picking up
262 the particular fix. Also consider sending git pull requests more often than
275 search in Linux distributions and Git forges. Also consider asking other
408 regzbot consider your mail as a regressions report added to the tracking, as
[all …]
|
| /linux/scripts/coccinelle/misc/ |
| H A D | orplus.cocci | 64 cocci.print_main("sum of probable bitmasks, consider |",p)
70 msg = "WARNING: sum of probable bitmasks, consider |"
|
| /linux/drivers/media/test-drivers/vidtv/ |
| H A 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/include/linux/ |
| H A 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/arch/x86/kernel/ |
| H A D | setup_percpu.c | 55 * pcpu_need_numa - determine percpu allocation needs to consider NUMA
58 * there is no reason to consider NUMA. This function determines
59 * whether percpu allocation should consider NUMA or not.
|
| /linux/Documentation/scheduler/ |
| H A D | sched-capacity.rst | 59 Consider an hypothetical dual-core asymmetric CPU capacity system where
94 OPPs. Consider the same CPUs as above (i.e. same work_per_hz()) with:
153 directly impacted by the current OPP the CPU is running at. Consider running a
163 Now, consider running the *same* workload at frequency F/2::
188 Consider the system described in 1.3.2., i.e.::
377 sleeps, if at all - it thus rarely wakes up, if at all. Consider::
|
| /linux/scripts/coccinelle/api/ |
| H A 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/Documentation/staging/ |
| H A 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/tools/perf/Documentation/ |
| H A D | perf-top.txt | 154 Only consider symbols in these dsos. This option will affect the
158 Only consider symbols in these comms. This option will affect the
162 Only consider these symbols. This option will affect the
339 Only consider events after this event is found.
351 Start perf top and ask it to only consider the cycles events when a
|
| H 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/Documentation/doc-guide/ |
| H A D | contributing.rst | 171 have fixed a few, please consider moving on to more advanced tasks, leaving
185 As with any patch to any project, please consider whether your change is
196 Whenever you are working with a document, please consider whether it is
224 this information with caution, and please consider sending patches
|
| /linux/Documentation/filesystems/ |
| H A D | directory-locking.rst | 72 There is one more thing to consider - splicing. It's not an operation
163 Suppose deadlocks are possible. Consider the minimal deadlocked
213 Consider the order in which directories are locked by the
270 Now consider the loop created by the operation. It passes through either
|
| H A D | idmappings.rst | 101 To see whether the simple formulas above work, consider the following two
177 For instance, consider a file that is stored on disk by a filesystem as being
205 the same kernel id in their kernel idmapsets. For example, consider the
540 idmapping it would be trivial. So we only consider a filesystem with an
557 workloads. For a more complex but common example, consider two containers
589 Or consider another increasingly popular example. Some service managers such as
670 To illustrate why this helper currently exists, consider what happens when we
731 Note that these two functions invert each other. Consider the following
958 Consider our previous example where a user has their home directory on portable
|
| /linux/Documentation/devicetree/bindings/pci/ |
| H A D | snps,dw-pcie-common.yaml | 114 Vendor-specific clock names. Consider using the generic names
171 Vendor-specific reset names. Consider using the generic names
198 Vendor-specific PHY names. Consider using the generic
|
| /linux/drivers/nfc/st-nci/ |
| H A 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/arch/arm/probes/kprobes/ |
| H A 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/Documentation/devicetree/bindings/ |
| H A 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/drivers/nfc/st21nfca/ |
| H A 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/Documentation/admin-guide/ |
| H A D | reporting-issues.rst | 136 process, consider searching again for existing reports about the issue.
138 * If your failure involves a 'panic', 'Oops', 'warning', or 'BUG', consider
241 above steps. Consider this as reference documentation: it's possible to read it
264 * If you never reported an issue to a FLOSS project before you should consider
302 or might not what you want. You thus might want to consider circumventing the
323 those often get rejected or ignored, so consider yourself warned. But it's still
348 If you get flooded with results consider telling your search engine to limit
373 the issue already got reported as outlined in this document and if not consider
397 What qualifies as security issue is left to your judgment. Consider reading
816 proper release with a version number like '5.7'. If that happens, consider
[all …]
|
| /linux/tools/memory-model/Documentation/ |
| H A D | locking.txt | 23 previously holding this same lock". For example, consider the following
152 seen as ordered by CPUs not holding that lock. Consider this example:
227 For example, consider a spin loop preceding a lock-based critical section.
|
| /linux/kernel/irq/ |
| H A D | autoprobe.c | 90 /* It triggered already - consider it spurious. */ in probe_irq_on()
107 * @val: mask of interrupts to consider
|
| /linux/drivers/cpuidle/governors/ |
| H A D | ladder.c | 87 /* consider promotion */ in ladder_select_state()
100 /* consider demotion */ in ladder_select_state()
|