Searched refs:there (Results 1 – 25 of 1603) sorted by relevance
12345678910>>...65
| /linux-6.12.1/tools/memory-model/litmus-tests/ |
| D | Z6.0+pooncerelease+poacquirerelease+fencembonceonce.litmus | 7 * when there is but one non-reads-from (AKA non-rf) link, does not suffice
8 * if there is more than one. Of the three processes, only P1() reads from
9 * P0's write, which means that there are two non-rf links: P1() to P2()
12 * When there are two or more non-rf links, you typically will need one
|
| /linux-6.12.1/Documentation/locking/ |
| D | robust-futexes.rst | 18 that says "there's a waiter pending", and the sys_futex(FUTEX_WAIT)
23 value) that there were waiter(s) pending, and does the
26 state, and there's no in-kernel state associated with it. The kernel
27 completely forgets that there ever was a futex at that address. This
44 the kernel cannot help with the cleanup: if there is no 'futex queue'
45 (and in most cases there is none, futexes being fast lightweight locks)
75 because the kernel has no knowledge about how many robust futexes there
89 At the heart of this new approach there is a per-thread private list of
93 time, the kernel checks this user-space list: are there any robust futex
96 In the common case, at do_exit() time, there is no list registered, so
[all …]
|
| /linux-6.12.1/Documentation/devicetree/bindings/regulator/ |
| D | nvidia,tegra-regulators-coupling.txt | 5 Thus on Tegra20 there are 3 coupled regulators and on NVIDIA Tegra30
6 there are 2.
11 On Tegra20 SoC's there are 3 coupled regulators: CORE, RTC and CPU.
18 On Tegra30 SoC's there are 2 coupled regulators: CORE and CPU. The CORE
|
| /linux-6.12.1/Documentation/ABI/testing/ |
| D | sysfs-firmware-lefi-boardinfo | 7 and BIOS version when there exists problems related with
29 By the way, using dmidecode command can get the similar info if there
30 exists SMBIOS in firmware, but the fact is that there is no SMBIOS on
|
| D | sysfs-bus-i2c-devices-pca954x | 12 channel, which is useful when there is a device
19 which is useful if there is one channel that is
|
| D | sysfs-kernel-boot_params | 9 If there's no setup_data in boot_params the subdirectory will
19 as a link list. In "setup_data" subdirectory there's one
|
| D | sysfs-platform-eeepc-laptop | 34 On the Eee PC 1000H there are three available clock configuration:
40 On Eee PC 701 there is only 2 available clock configurations.
|
| /linux-6.12.1/Documentation/timers/ |
| D | no_hz.rst | 38 there are some situations where this old-school approach is still the
40 that use short bursts of CPU, where there are very frequent idle
43 clock interrupts will normally be delivered any way because there
68 If a CPU is idle, there is little point in sending it a scheduling-clock
84 unnecessary scheduling-clock interrupts. In these situations, there
107 If a CPU has only one runnable task, there is little point in sending it
108 a scheduling-clock interrupt because there is no other task to switch to.
121 by one less than the number of CPUs. In these situations, there is
131 (This is not an issue for CONFIG_NO_HZ_IDLE=y because there are no running
160 4. If there are more perf events pending than the hardware can
[all …]
|
| /linux-6.12.1/arch/arm/vfp/ |
| D | vfphw.S | 40 tst r0, #FPEXC_EX @ is there additional state to restore?
43 tst r0, #FPEXC_FP2V @ is there an FPINST2 to write?
58 tst r1, #FPEXC_EX @ is there additional state to save?
61 tst r1, #FPEXC_FP2V @ is there an FPINST2 to read?
|
| /linux-6.12.1/arch/arm64/boot/dts/qcom/ |
| D | apq8094-sony-xperia-kitakami-karin_windy.dts | 8 /* As the names may imply, there is quite a bunch of duplication there. */
|
| /linux-6.12.1/Documentation/networking/device_drivers/ethernet/toshiba/ |
| D | spider_net.rst | 46 marks it full, and advances the GDACTDPA by one. Thus, when there is
55 and advance the tail pointer. Thus, when there is flowing RX traffic,
67 then mark the descr as "empty", ready to receive data. Thus, when there
117 the hardware can fill them, there is no problem. If, for some reason,
136 and is filling the next descrs. Since the OS doesn't see this, there
157 marked xa... which is "empty". Thus, from the OS point of view, there
158 is nothing to be done. In particular, there is the implicit assumption
168 and there can be no forward progress; the OS thinks there's nothing
177 operations there. Since this will leave "holes" in the ring, there
191 is full, the netdev is stopped. When there is room in the ring,
|
| /linux-6.12.1/Documentation/userspace-api/media/v4l/ |
| D | vidioc-g-edid.rst | 56 pad of the subdevice. If there is no EDID support for the given ``pad``
66 If there are fewer blocks than specified, then the driver will set
67 ``blocks`` to the actual number of blocks. If there are no EDID blocks
77 there are.
81 If there are no EDID blocks available at all, then
90 The driver assumes that the full EDID is passed in. If there are more
|
| /linux-6.12.1/Documentation/trace/coresight/ |
| D | coresight-tpda.rst | 45 integration_test (by cat tmc_etf0/mgmt/rwp), it means there is data
48 There must be a tpda between tpdm and the sink. When there are some
51 there is only tpdm trace hw in the HW block, tpdm will connect to
|
| /linux-6.12.1/Documentation/ |
| D | Kconfig | 6 bool "Warn if there's a missing documentation file"
16 bool "Warn if there are errors at ABI files"
|
| /linux-6.12.1/Documentation/process/ |
| D | 6.Followthrough.rst | 13 It is a rare patch which is so good at its first posting that there is no
40 people remember who wrote kernel code, but there is little lasting fame
101 but there are times when somebody simply has to make a decision. If you
118 things. In particular, there may be more than one tree - one, perhaps,
122 For patches applying to areas for which there is no obvious subsystem tree
131 there's a good chance that you will get more comments from a new set of
153 the patch before. It may be tempting to ignore them, since there is no
162 where there are testers, there will be bug reports.
173 After any regressions have been dealt with, there may be other, ordinary
181 And don't forget that there are other milestones which may also create bug
[all …]
|
| /linux-6.12.1/Documentation/maintainer/ |
| D | messy-diffstat.rst | 30 Here, there are two clear points in the history; Git will essentially
43 the mainline branch (let's call it "linus") and cN, there are still two
59 What is happening here is that there are no longer two clear end points for
63 starts at vN-rc1, it may end up including all of the changes between there
78 shame. Create a new, throwaway branch and do the merge there::
|
| /linux-6.12.1/drivers/gpu/drm/i915/ |
| D | TODO.txt | 6 improved a lot the past 2 years, there's no reason anymore not to use it.
8 - Come up with a plan what to do with drm/scheduler and how to get there.
28 maybe even remove it if there's nothing left.
|
| /linux-6.12.1/Documentation/filesystems/ext4/ |
| D | orphan.rst | 6 In unix there can inodes that are unlinked from directory hierarchy but that
37 RO_COMPAT_ORPHAN_PRESENT feature in the superblock to indicate there may
40 there as usual. When cleanly unmounting the filesystem we remove the
|
| D | special_inodes.rst | 15 - Doesn't exist; there is no inode 0.
39 Note that there are also some inodes allocated from non-reserved inode numbers
|
| /linux-6.12.1/Documentation/driver-api/media/drivers/ |
| D | bttv-devel.rst | 14 To handle the grabber boards correctly, there is a array tvcards[] in
27 If your card isn't listed there, you might check the source code for
28 new entries which are not listed yet. If there isn't one for your
35 module like ``msp3400`` to make sound work. If there isn't one for the
63 As mentioned above, there is a array which holds the required
|
| /linux-6.12.1/Documentation/driver-api/mmc/ |
| D | mmc-async-req.rst | 48 truly non-blocking. If there is an ongoing async request it waits
50 doesn't wait for the new request to complete. If there is no ongoing
67 with the previous transfer, since there is no previous request.
69 The argument is_first_req in pre_req() indicates that there is no previous
|
| /linux-6.12.1/Documentation/devicetree/bindings/ |
| D | writing-bindings.rst | 8 every rule, there are exceptions and bindings have many gray areas.
25 defined in the DT Spec. If there isn't one, consider adding it.
44 of prior implementations. DO add new compatibles in case there are new
65 explicitly ordered. Include the {clock,dma,interrupt,reset}-names if there is
|
| /linux-6.12.1/Documentation/ABI/stable/ |
| D | sysfs-firmware-opal-elog | 15 Linux if there is no room for more log entries.
38 For each log entry (directory), there are the following
48 In the future there may be additional types.
|
| /linux-6.12.1/Documentation/images/ |
| D | COPYING-logo | 2 ("currently unofficial" just means that there has been no paperwork and
7 Note that there are black-and-white versions of this available that
|
| /linux-6.12.1/Documentation/power/ |
| D | basic-pm-debugging.rst | 49 there is the file /sys/power/pm_test that can be used to make the hibernation
109 If the "freezer" test fails, there is a task that cannot be frozen (in that case
112 that there is a problem with the tasks freezer subsystem that should be
115 If the "devices" test fails, most likely there is a driver that cannot suspend
126 Once you have found the failing driver (there can be more than just one of
136 If the "platform" test fails, there is a problem with the handling of the
162 "reboot", "shutdown" and "platform" modes. If that does not work, there
165 individually. Otherwise, there is a problem with a modular driver and you can
168 - if there are n modules loaded and the attempt to suspend and resume fails,
171 - if there are n modules loaded and the attempt to suspend and resume succeeds,
[all …]
|
12345678910>>...65