Searched full:could (Results 1 – 25 of 583) sorted by relevance
12345678910>>...24
| /Documentation/ABI/testing/ |
| D | sysfs-driver-ufs | 20 the descriptor could be found at UFS specifications 2.1.
28 the descriptor could be found at UFS specifications 2.1.
36 about the descriptor could be found at UFS specifications 2.1.
44 The full information about the descriptor could be found
53 about the descriptor could be found at UFS specifications 2.1.
61 The full information about the descriptor could be found
70 parameters. The full information about the descriptor could
78 descriptor could be read after partial initialization phase
80 parameters. The full information about the descriptor could
90 about the descriptor could be found at UFS specifications 2.1.
[all …]
|
| D | sysfs-bus-iio-adc-hi8435 | 7 Could be either "GND-Open" or "Supply-Open" mode. Y is a
20 Channels 0..31 have common low threshold values, but could have different
37 Channels 0..31 have common high threshold values, but could have different
|
| D | sysfs-block-zram | 48 "0". Otherwise, you could see -EINVAL.
57 The limit could be changed in run time and "0" means disable
66 it could free fragment space.
138 amount of writeback ZRAM can do. The limit could be changed
|
| D | sysfs-class-fpga-manager | 15 fails, that could be due to not being able to find the firmware
44 If FPGA programming operation fails, it could be caused by crc
|
| /Documentation/media/uapi/v4l/ |
| D | vidioc-query-dv-timings.rst | 64 If the timings could not be detected because there was no signal, then
66 the receiver could not lock to the signal, then ``ENOLCK`` is returned. If
67 the receiver could lock to the signal, but the format is unsupported
69 capabilities), then the driver fills in whatever timings it could find
87 No timings could be detected because no signal was found.
90 The signal was unstable and the hardware could not lock on to it.
|
| D | selection-api-vs-crop-api.rst | 26 image inside a memory buffer. The application could configure a
30 Introducing an image offsets could be done by modifying field
|
| /Documentation/devicetree/bindings/net/ |
| D | brcm,mdio-mux-iproc.txt | 3 This MDIO bus multiplexer defines buses that could be internal as well as
4 external to SoCs and could accept MDIO transaction compatible to C-22 or
13 Every non-ethernet PHY requires a compatible so that it could be probed based
|
| /Documentation/devicetree/bindings/display/hisilicon/ |
| D | hisi-ade.txt | 23 The rate of "clk_ade_core" could be "360000000" or "180000000";
24 The rate of "clk_codec_jpeg" could be or less than "1440000000".
25 These rate values could be configured according to performance and power
|
| /Documentation/driver-api/ |
| D | isa.rst | 13 ISA bus might be best; Russell King agreed and suggested this bus could
59 ALSA would want to keep the old non-load behaviour, it could stick all
63 changeover to platform devices, it could just not provide a .match() and
68 could conceivably succeed, it could use .match() for the prerequisites
|
| D | device_connection.rst | 10 could be a PCI device, may need to be able to get a reference to its PHY
11 component, which could be attached for example to the I2C bus. Some device
|
| /Documentation/devicetree/bindings/pwm/ |
| D | pwm-meson.txt | 17 - clocks: Could contain one or two parents clocks phandle for each of the two
19 - clock-names: Could contain at least the "clkin0" and/or "clkin1" names.
|
| /Documentation/userspace-api/ |
| D | no_new_privs.rst | 9 careful to prevent the parent from doing anything that could subvert the
26 promises not to grant the privilege to do anything that could not have
59 In the future, other potentially dangerous kernel features could become
|
| /Documentation/trace/ |
| D | events-kmem.rst | 65 is triggered. Significant amounts of activity here could indicate that the
70 freed in batch with a page list. Significant amounts of activity here could
96 refills and drains could imply an imbalance between CPUs where too much work
97 is being concentrated in one place. It could also indicate that the per-CPU
99 and drains on another could be a factor in causing large amounts of cache
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-st.txt | 21 - A pinctrl state named "idle" could be defined to set pins in idle state
23 - A pinctrl state named "sleep" could be defined to set pins in sleep state
|
| /Documentation/devicetree/bindings/usb/ |
| D | usb-device.txt | 24 standard binding could also be used, but a device adhering to this binding
40 strings from the above standard binding could also be used, but a device
53 standard binding could also be used, but a device adhering to this binding
|
| /Documentation/i2c/ |
| D | ten-bit-addresses.rst | 8 address 0x10 (though a single device could respond to both of them).
32 listed above could stay for a long time, maybe even forever if nobody
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-single.txt | 52 * Although driver could set PIN_CONFIG_BIAS_DISABLE, there's no property as
53 pinctrl-single,bias-disable. Because pinctrl single driver could implement
99 a pin for a device could be done with:
118 Optional sub-node: In case some pins could be configured as GPIO in the pinmux
119 register, those pins could be defined as a GPIO range. This sub-node is required
180 /* sparse GPIO range could be supported */
|
| /Documentation/arm/nwfpe/ |
| D | todo.rst | 35 so such a method could be promising, but requires more research to
49 bits describing the rounding mode. The emulator could be altered to
69 Hence, the answer is yes, you could do this, but then you will run a high
|
| /Documentation/gpu/ |
| D | vkms.rst | 47 There's lots of plane features we could add support for:
68 features, we could write back the entire composited frame, and expose it as:
106 we could add support for eBPF to validate any kind of atomic state, and
|
| /Documentation/filesystems/ |
| D | erofs.txt | 24 - Metadata & data could be mixed by design;
119 Inode could be 32 or 64 bytes, which can be distinguished from a common
132 proper alignes, and they could be optional for different data mappings,
163 algorithm (could refer to the related source code).
173 \ | * could have
|
| /Documentation/driver-api/pci/ |
| D | p2pdma.rst | 43 In many cases there could be overlap between these three types (i.e.,
59 one could imagine slight tweaks to this that would allow for the same
61 memory behind it, its driver could add support as a P2P provider and
62 then the NVMe Target could use the RNIC's memory instead of the CMB
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | mt6323-poweroff.txt | 3 The power controller which could be found on PMIC is responsible for externally
|
| /Documentation/scheduler/ |
| D | sched-domains.rst | 11 A domain's span MUST be a superset of it child's span (this restriction could
14 although strictly it doesn't have to, but this could lead to a case where some
63 cpumask of a node. Or, you could do multi-level NUMA or Opteron, for example,
|
| /Documentation/driver-api/dmaengine/ |
| D | dmatest.rst | 21 The menuconfig contains an option that could be found by following path:
25 In the configuration file the option called CONFIG_DMATEST. The dmatest could
105 for the first performed test. After user gets a control, the test could be
110 case. You always could check them at run-time by running ::
152 dmatest: Could not start test, no channels configured
|
| /Documentation/locking/ |
| D | lockdep-design.rst | 137 The same lock-class must not be acquired twice, because this could lead
145 because this could lead to a deadlock - referred to as lock inversion
147 could lead to the two contexts waiting for each other permanently. The
159 The first rule comes from the fact that a hardirq-safe lock could be
161 thus could result in a lock inversion deadlock. Likewise, a softirq-safe
162 lock could be taken by an softirq context, interrupting a softirq-unsafe
185 could interrupt _any_ of the irq-unsafe or hardirq-unsafe locks, which
186 could lead to a lock inversion deadlock - even if that lock scenario did
309 We also assume that all NMI/SMM paths [which could interrupt
|
12345678910>>...24