Searched full:cases (Results 1 – 25 of 477) sorted by relevance
12345678910>>...20
| /Documentation/devicetree/bindings/slimbus/ |
| D | bus.txt | 18 In some cases it may be necessary to describe non-probeable device
20 such cases, child nodes for those devices will be present as
28 Instance ID Is for the cases where multiple Devices of the
|
| /Documentation/RCU/ |
| D | rcuref.txt | 7 those unusual cases where percpu-ref would consume too much memory,
76 update (write) stream. In such cases, atomic_inc_not_zero() might be
78 use atomic_inc() in such cases.
81 search_and_reference() code path. In such cases, the
132 In cases where delete() can sleep, synchronize_rcu() can be called from
|
| D | UP.rst | 64 In some cases, it would possible to restructure to code so that
66 there are cases where this can be quite ugly:
73 2. In some cases, the lock will be held across some kernel API,
|
| /Documentation/devicetree/bindings/iommu/ |
| D | iommu.txt | 44 the specific IOMMU. Below are a few examples of typical use-cases:
51 In such cases the number of cells will usually be 1 as in the next case.
53 in order to enable translation for a given master. In such cases the single
54 address cell corresponds to the master device's ID. In some cases more than
62 Note that these are merely examples and real-world use-cases may use different
85 have a means to turn off translation. But it is invalid in such cases to
|
| /Documentation/power/regulator/ |
| D | design.rst | 24 Consumer use cases
36 The consumer API should be structured so that these use cases are
|
| /Documentation/driver-api/ |
| D | device-io.rst | 78 writes have occurred in the specific cases the author cares. This kind
80 cases, the read used to flush the device may be expected to fail (if the
109 complete. In many cases, however, the driver may want to indicate that the
112 these cases, although only some platforms will honor the relaxed
115 provides examples of how to use readX_relaxed(). In many cases, a majority
|
| D | edid.rst | 13 booting or it displays the wrong area. Cases when this happens are:
19 Adding the kernel parameter "nomodeset" helps in most cases, but causes
|
| /Documentation/devicetree/bindings/pci/ |
| D | designware-pcie-ecam.txt | 3 In some cases, firmware may already have configured the Synopsys DesignWare
10 In cases where the IP was synthesized with a minimum ATU window size of
|
| /Documentation/bpf/ |
| D | bpf_devel_QA.rst | 84 from the current review queue. Likewise for cases where patches would
203 at the end of the week. In some cases pull requests could additionally
222 Q: Verifier changes and test cases
224 Q: I made a BPF verifier change, do I need to add test cases for
228 it is absolutely necessary to add test cases to the BPF kernel
233 cases, including a lot of corner cases that LLVM BPF back end may
234 generate out of the restricted C code. Thus, adding test cases is
236 affect prior use-cases. Thus, treat those test cases as: verifier
249 The more test cases we add to BPF selftests, the better the coverage
316 commit is in net-next (or in some cases bpf-next). The ``Fixes:`` tag is
[all …]
|
| D | prog_flow_dissector.rst | 99 the optional VLAN header and should gracefully handle both cases: when single
101 can be called for both cases and would have to be written carefully to
102 handle both cases.
|
| /Documentation/devicetree/bindings/usb/ |
| D | brcm,bcm3384-usb.txt | 7 systems, special handling may be needed in the following cases:
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-s3c2410.txt | 18 Required for all cases except "samsung,s3c2440-hdmiphy-i2c":
22 cases except for "samsung,s3c2440-hdmiphy-i2c" whose input/output
|
| /Documentation/powerpc/ |
| D | ultravisor.rst | 312 Use cases
386 Use cases
437 Use cases
483 Use cases
544 Use cases
593 Use cases
638 Use cases
673 Use cases
720 Use cases
770 Use cases
[all …]
|
| /Documentation/crypto/ |
| D | index.rst | 10 for cryptographic use cases, as well as programming examples.
|
| /Documentation/firmware-guide/acpi/ |
| D | DSD-properties-rules.rst | 61 There are cases in which, even if the general rule given above is followed in
73 In all cases in which kernel code may do something that will confuse AML as a
84 In those cases, however, the above validity considerations must be taken into
|
| /Documentation/i2c/ |
| D | fault-codes.rst | 14 some cases, such as re-initializing (and maybe resetting). After such
34 codes that may be returned, and other cases where these codes should
36 cases (unless the hardware doesn't provide unique fault reports).
|
| /Documentation/livepatch/ |
| D | callbacks.rst | 16 In most cases, (un)patch callbacks will need to be used in conjunction
64 executed. Typical use cases pair a patch handler that acquires and
102 4. Use cases
|
| /Documentation/networking/ |
| D | secid.txt | 11 cases, as may be appropriate.
|
| /Documentation/process/ |
| D | 3.Early-stage.rst | 17 clear description of the problem to be solved. In some cases, this step is
63 - Who are the users affected by this problem? Which use cases should the
121 In each of these cases, a great deal of pain and extra work could have been
205 mailing list may not be a viable option. In cases like this, it is worth
209 That said, there are also cases where a company legitimately cannot
|
| /Documentation/devicetree/bindings/serial/ |
| D | qcom,msm-uart.txt | 3 The MSM serial UART hardware is designed for low-speed use cases where a
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | cirrus,lochnagar.txt | 9 to be used in a variety of possible use cases.
|
| /Documentation/driver-api/soundwire/ |
| D | error_handling.rst | 42 3. Timeouts: In a number of cases such as ChannelPrepare or
61 written in valid registers. In a number of cases the standard even mentions
|
| /Documentation/filesystems/ |
| D | btrfs.txt | 30 questions, use cases, mount options, comprehensible changelogs, features,
|
| /Documentation/devicetree/bindings/regmap/ |
| D | regmap.txt | 20 blob in both cases.
|
| /Documentation/devicetree/bindings/clock/ |
| D | qcom,lpasscc.txt | 18 The below node has to be defined in the cases where the LPASS peripheral loader
|
12345678910>>...20