Searched refs:there (Results 1 – 25 of 1437) sorted by relevance
12345678910>>...58
| /Linux-v5.4/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-v5.4/Documentation/ |
| D | robust-futexes.txt | 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 …]
|
| 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-v5.4/Documentation/devicetree/bindings/power/supply/ |
| D | twl-charger.txt | 4 to know when charging is permissible, and when there is a connection
7 The choice of phy cannot be configured at a hardware level, so there
9 if there is a sibling of the BCI node which is compatible with
|
| /Linux-v5.4/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
80 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
163 4. If there are more perf events pending than the hardware can
[all …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/net/ |
| D | brcm,unimac-mdio.txt | 16 Ethernet switch this MDIO block is integrated from, or must be two, if there
19 - interrupt-names: must be "mdio_done_error" when there is a share interrupt fed
21 "mdio_error" for the second when there are separate interrupts
|
| /Linux-v5.4/Documentation/networking/device_drivers/toshiba/ |
| D | spider_net.txt | 44 marks it full, and advances the GDACTDPA by one. Thus, when there is
53 and advance the tail pointer. Thus, when there is flowing RX traffic,
65 then mark the descr as "empty", ready to receive data. Thus, when there
115 the hardware can fill them, there is no problem. If, for some reason,
134 and is filling the next descrs. Since the OS doesn't see this, there
155 marked xa... which is "empty". Thus, from the OS point of view, there
156 is nothing to be done. In particular, there is the implicit assumption
166 and there can be no forward progress; the OS thinks there's nothing
175 operations there. Since this will leave "holes" in the ring, there
189 is full, the netdev is stopped. When there is room in the ring,
|
| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | vidioc-g-edid.rst | 62 pad of the subdevice. If there is no EDID support for the given ``pad``
72 If there are fewer blocks than specified, then the driver will set
73 ``blocks`` to the actual number of blocks. If there are no EDID blocks
83 there are.
87 If there are no EDID blocks available at all, then
96 The driver assumes that the full EDID is passed in. If there are more
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-bus-i2c-devices-pca954x | 10 channel, which is useful when there is a device
17 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 | 32 On the Eee PC 1000H there are three available clock configuration:
36 On Eee PC 701 there is only 2 available clock configurations.
|
| /Linux-v5.4/Documentation/devicetree/bindings/i2c/ |
| D | i2c-gate.txt | 4 there are no competing masters to consider for gates and therefore there is
|
| /Linux-v5.4/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
94 but there are times when somebody simply has to make a decision. If you
111 things. In particular, there may be more than one tree - one, perhaps,
115 For patches applying to areas for which there is no obvious subsystem tree
124 there's a good chance that you will get more comments from a new set of
146 the patch before. It may be tempting to ignore them, since there is no
155 where there are testers, there will be bug reports.
166 After any regressions have been dealt with, there may be other, ordinary
174 And don't forget that there are other milestones which may also create bug
[all …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/sound/ |
| D | imx-audio-spdif.txt | 16 indicating there's a physical S/PDIF out connector
22 function of S/PDIF will be enabled, indicating there
|
| /Linux-v5.4/drivers/block/paride/ |
| D | Transition-notes | 50 be preempted there.
51 2) When there is such a thread, pd_busy is set or pd_lock is held by
53 3) When there is such a thread, ps_tq_active is 0 or ps_spinlock is
55 4) When there is such a thread, all PIA belonging to pd.c have NULL
60 (1) can become not true if some thread enters that area while another is there.
72 case that needs consideration is call from pi_wake_up() and there
123 We don't need to reset it to NULL, since we are guaranteed that there
|
| /Linux-v5.4/Documentation/devicetree/bindings/misc/ |
| D | idt_89hpesx.txt | 5 Basically there is only one manufacturer: idt, but some
22 Optionally there can be EEPROM-compatible subnode:
|
| /Linux-v5.4/drivers/staging/isdn/ |
| D | TODO | 1 TODO: Remove in late 2019 unless there are users
8 months, there is very little you can actually do with this hardware. The
|
| /Linux-v5.4/Documentation/devicetree/bindings/arm/hisilicon/ |
| D | hisilicon-low-pin-count.txt | 4 Hip06 is based on arm64 architecture where there is no I/O space. So, the
5 I/O ports here are not CPU addresses, and there is no 'ranges' property in
|
| /Linux-v5.4/Documentation/devicetree/bindings/gpio/ |
| D | nvidia,tegra20-gpio.txt | 7 there should be 7 interrupts specified, and for Tegra30, there should
|
| /Linux-v5.4/tools/lib/traceevent/Documentation/ |
| D | libtraceevent-event_get.txt | 35 NULL is returned in case of error, in case there are no events or _index_ is
39 returned in case of error, or in case there are no events.
42 returned in case of error, or in case there are no events.
|
| /Linux-v5.4/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
47 In the future there may be additional types.
|
| /Linux-v5.4/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-v5.4/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 …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/ |
| D | writing-bindings.txt | 4 every rule, there are exceptions and bindings have many gray areas.
20 defined in the DT Spec. If there isn't one, consider adding it.
38 of prior implementations. DO add new compatibles in case there are new
|
| /Linux-v5.4/Documentation/scsi/ |
| D | sym53c500_cs.txt | 15 of the New Media Bus Toaster PCMCIA SCSI controller. Presumably there are
19 Through the years, there have been a number of downloads of the pcmcia-cs
|
12345678910>>...58
