Searched full:things (Results 1 – 25 of 1958) sorted by relevance
12345678910>>...79
| /Linux-v6.1/Documentation/power/ |
| D | opp.rst | 117 /* Do things */
123 /* Do cpufreq things */
125 /* Do remaining things */
263 /* do things */
269 /* do other things */
280 /* do things.. */
288 /* do other things */
296 /* do things.. */
306 /* Do things */
319 /* Do other things */
|
| D | s2ram.rst | 23 way to debug these things, and it's actually pretty powerful (but
42 holding the power button down, and look at the dmesg output for things
|
| /Linux-v6.1/Documentation/driver-api/ |
| D | frame-buffer.rst | 15 that are user defined. With fb_var_screeninfo, things such as depth
25 importance for fb_monospecs. This allowed for forbidden things such as
27 fb_monospecs prevents such things, and if used correctly, can prevent a
|
| /Linux-v6.1/tools/perf/pmu-events/arch/x86/ivytown/ |
| D | uncore-interconnect.json | 305 …QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting tr…
315 …QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting tr…
326 …QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting tr…
337 …QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting tr…
348 …QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting tr…
359 …QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting tr…
370 …QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting tr…
381 …QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting tr…
392 …QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting tr…
403 …QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting tr…
[all …]
|
| /Linux-v6.1/Documentation/process/ |
| D | 6.Followthrough.rst | 28 process. Life can be made much easier, though, if you keep a few things in
58 understand what the reviewer is trying to say. If possible, fix the things
68 agree with the reviewer, take some time to think things over again. It can
92 What if you've tried to do everything right and things still aren't going
111 things. In particular, there may be more than one tree - one, perhaps,
185 Other things that can happen
|
| D | howto.rst | 56 of doing things.
130 not have a stable API within the kernel, including things like:
385 you want to bring up, before you post it to the list. A lot of things
448 again, sometimes things get lost in the huge volume.
465 of a dozen things you should correct. This does **not** imply that your
475 development environments. Here are a list of things that you can try to
478 Good things to say regarding your proposed changes:
487 Bad things you should avoid saying:
532 The reasons for breaking things up are the following:
602 All of these things are sometimes very hard to do. It can take years to
[all …]
|
| D | management-style.rst | 57 needs to do is to turn the big and painful ones into small things where
71 things that can't be undone. Don't get ushered into a corner from which
219 Things will go wrong, and people want somebody to blame. Tag, you're it.
242 5) Things to avoid
257 Similarly, don't be too polite or subtle about things. Politeness easily
|
| /Linux-v6.1/arch/x86/include/uapi/asm/ |
| D | debugreg.h | 14 /* Define a few things for the status register. We can use this to determine
31 /* Now define a bunch of things for manipulating the control register.
65 /* The second byte to the control register has a few special things.
|
| /Linux-v6.1/Documentation/trace/ |
| D | ftrace-design.rst | 15 code relies on for proper functioning. Things are broken down into increasing
46 We'll make the assumption below that the symbol is "mcount" just to keep things
74 typically the bare minimum with checking things before returning. That also
130 things.
185 be able to skimp on things saved/restored (usually just registers used to pass
235 You need very few things to get the syscalls tracing in an arch.
345 patching multiple things. First, only functions that we actually want to trace
|
| /Linux-v6.1/Documentation/gpu/amdgpu/ |
| D | driver-core.rst | 17 the SoC itself rather than specific IPs. E.g., things like GPU resets
24 their interface to interact with those common components. For things
62 various things including paging and GPU page table updates. It's also
105 SoC and for things like init/fini/suspend/resume, more or less just
|
| /Linux-v6.1/arch/sparc/include/asm/ |
| D | pbm.h | 12 * To put things into perspective, consider sparc64 with a few PCI controllers.
34 /* Now things for the actual PCI bus probes. */
|
| /Linux-v6.1/Documentation/devicetree/bindings/mfd/ |
| D | mfd.txt | 10 silicon) that handles analog drivers for things like audio amplifiers, LED
11 drivers, level shifters, PHY (physical interfaces to things like USB or
|
| /Linux-v6.1/Documentation/security/ |
| D | self-protection.rst | 53 temporary exceptions to this rule to support things like instruction
117 things like compat, user namespaces, BPF creation, and perf limited only
159 the function returns. Other defenses include things like shadow stacks.
207 It should be noted that things like the stack canary discussed earlier
212 Blinding literal values for things like JITs, where the executable
270 addresses or other sensitive things like canary values).
|
| /Linux-v6.1/drivers/misc/echo/ |
| D | echo.h | 40 things like modem line equalisers and line echo cancellers. There it works very
42 very poorly for things like speech echo cancellation, where the signal level
88 and the environment is not, things will be OK. Clearly, it is easy to tell when
|
| /Linux-v6.1/arch/arm64/boot/dts/qcom/ |
| D | sc7280-chrome-common.dtsi | 8 * things that will hold true for any conceivable Chrome design
59 /* The PMIC PON code isn't compatible w/ how Chrome EC/BIOS handle things. */
|
| /Linux-v6.1/include/uapi/linux/ |
| D | rfkill.h | 143 * accessed them, but things should've continued to work.
147 * did all kinds of fun things not in line with this scheme:
155 * things to no longer work correctly on old and new kernels.
|
| /Linux-v6.1/Documentation/dev-tools/kunit/ |
| D | faq.rst | 70 Unfortunately, there are a number of things which can break, but here are some
71 things to try.
91 enable/disable things with ``make ARCH=um menuconfig`` or similar, and then
|
| /Linux-v6.1/arch/x86/platform/efi/ |
| D | efi_thunk_64.S | 9 * has been called. This simplifies things considerably as compared with
16 * 64-bit virtual address space. Things like the stack and instruction
|
| /Linux-v6.1/Documentation/translations/zh_TW/cpu-freq/ |
| D | core.rst | 95 /* Do things */
99 /* Do other things */
|
| /Linux-v6.1/drivers/gpu/drm/msm/disp/mdp5/ |
| D | mdp5_smp.h | 39 * 1) in _prepare_commit() we configure things (via read-modify-write)
42 * 2) in _complete_commit(), after vblank/etc, we clear things for the
|
| /Linux-v6.1/Documentation/translations/zh_CN/cpu-freq/ |
| D | core.rst | 97 /* Do things */
101 /* Do other things */
|
| /Linux-v6.1/Documentation/usb/ |
| D | gadget_multi.rst | 28 As one might expect, things one need to do very from system to system.
72 Things are harder with RDNIS and CDC ACM.
107 things don't work as intended before realising Windows have cached
|
| /Linux-v6.1/Documentation/sound/soc/ |
| D | jack.rst | 18 This is done by splitting the jacks up into three things working
56 update and the set of things to report when the jack is connected.
|
| /Linux-v6.1/Documentation/x86/ |
| D | tlb.rst | 19 Which method to do depends on a few things:
36 There is obviously no way the kernel can know all these things,
|
| /Linux-v6.1/Documentation/ABI/ |
| D | README | 54 with userspace developers to ensure that things do not
69 How things move between levels:
|
12345678910>>...79
