Searched full:considering (Results 1 – 25 of 38) sorted by relevance
12
| /Documentation/driver-api/ |
| D | wbrf.rst | 72 current active frequency bands considering some producers may broadcast
|
| /Documentation/gpu/ |
| D | drm-usage-stats.rst | 124 considering the CPU sleep time between 2 samples.
134 time active without considering what frequency the engine is operating as a
|
| /Documentation/process/ |
| D | 3.Early-stage.rst | 68 Only then does it make sense to start considering possible solutions.
207 considering whether the secrecy is really necessary; there is often no real
|
| D | 6.Followthrough.rst | 185 is insufficient motivation, though, it's also worth considering that the
|
| D | 1.Intro.rst | 190 before considering any sort of binary-only kernel code distribution. These
|
| /Documentation/devicetree/bindings/spi/ |
| D | spi-controller.yaml | 52 driven (not considering potential gpio inversions by pinmux):
|
| /Documentation/trace/rv/ |
| D | da_monitor_synthesis.rst | 94 stored in an 'unsigned char' type. Considering that the preemption control
|
| D | runtime-verification.rst | 108 buffer, not even considering collecting the trace for user-space analysis.
|
| /Documentation/networking/ |
| D | operstates.rst | 183 considering the interface / querying a DHCP address.
|
| D | iso15765-2.rst | 54 inside one single CAN message or not, also considering the overhead the protocol
|
| D | nexthop-group-resilient.rst | 105 underweight next hops. If, after considering all buckets in this manner,
|
| /Documentation/admin-guide/hw-vuln/ |
| D | srso.rst | 135 Considering the performance implications of each mitigation type, the
|
| /Documentation/gpu/amdgpu/display/ |
| D | display-manager.rst | 179 MPCC blend configuration considering the :c:type:`dc_plane_info
|
| /Documentation/devicetree/ |
| D | of_unittest.rst | 98 considering only child and sibling pointers. There exists another pointer,
|
| /Documentation/devicetree/bindings/opp/ |
| D | opp-v2-base.yaml | 85 The maximum current drawn by the device in microamperes considering
|
| /Documentation/userspace-api/media/mediactl/ |
| D | request-api.rst | 23 dequeuing before considering the next frame. This defeats the purpose of having
|
| /Documentation/livepatch/ |
| D | reliable-stacktrace.rst | 180 trampoline or return trampoline. For example, considering the x86_64
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-coresight-devices-etm3x | 132 Description: (RW) Number of byte left in the fifo before considering it full.
|
| /Documentation/admin-guide/media/ |
| D | dvb_intro.rst | 96 On this example, we're considering tuning into DVB-T channels in
|
| /Documentation/locking/ |
| D | lockdep-design.rst | 426 readers could get blocked by a write lock *waiter*. Considering the follow
601 could cause deadlocks, so we call it "strong", considering there are dependency
|
| /Documentation/filesystems/nfs/ |
| D | localio.rst | 165 standard, nor does it need to be considering it is Linux-to-Linux
|
| /Documentation/filesystems/ |
| D | erofs.rst | 12 of just focusing on storage space saving without considering any side effects
|
| /Documentation/scheduler/ |
| D | sched-capacity.rst | 249 considering a "true" task utilization (using a crystal ball), the implementation
|
| D | sched-deadline.rst | 351 WCET_i/P_i over all the real-time tasks in the system. When considering
583 sched_setattr()). Scheduling is then performed considering actual tasks'
|
| /Documentation/power/ |
| D | energy-model.rst | 119 registration method should be preferred in case considering EM static power
|
12