Searched full:there (Results 1 – 25 of 1668) sorted by relevance
12345678910>>...67
| /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
42 There is a big conceptual problem with futex based mutexes though: it is
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
[all …]
|
| /Documentation/timers/ |
| D | no_hz.rst | 12 There are three main ways of managing scheduling-clock interrupts
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
98 There is also a boot parameter "nohz=" that can be used to disable
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
[all …]
|
| /Documentation/gpu/amdgpu/display/ |
| D | dc-debug.rst | 28 configuration changes or a full update occurs there will be a colored bar at
33 * Pipe split can be observed if there are two bars with a difference in height
41 * There should **not** be any visual corruption
42 * There should **not** be any underflow or screen flashes
43 * There should **not** be any black screens
44 * There should **not** be any cursor corruption
|
| /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
18 There are also black-and-white and inverted vector versions at
|
| /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
151 To begin with, the visibility of your patch has increased yet again. There
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
[all …]
|
| D | 8.Conclusion.rst | 6 There are numerous sources of information on Linux kernel development and
30 There are a number of books on kernel development:
42 the shelves for a while now. Still, there is quite a bit of good
43 information to be found there.
66 The kernel can always benefit from a larger developer base, though. There
|
| D | 3.Early-stage.rst | 44 There are a number of very good Linux kernel developers, but they
87 - There may be elements of the proposed solution which will not be
131 the MAINTAINERS file for a relevant place to post. If there is a suitable
132 subsystem list, posting there is often preferable to posting on
138 and not all subsystems are represented there. The person listed in the
140 that role currently. So, when there is doubt about who to contact, a
158 list of people to Cc for your patches. There are a number of options
178 matter is (1) kernel developers tend to be busy, (2) there is no shortage
186 not assume that it means there is no interest in the project.
187 Unfortunately, you also cannot assume that there are no problems with your
[all …]
|
| /Documentation/networking/device_drivers/ethernet/toshiba/ |
| D | spider_net.rst | 28 There are three primary states that a descriptor can be in: "empty",
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
[all …]
|
| /Documentation/livepatch/ |
| D | livepatch.rst | 15 There are many situations where users are reluctant to reboot a system. It may
26 There are multiple mechanisms in the Linux kernel that are directly related
46 a live patch is called with the help of a custom ftrace handler. But there are
53 Functions are there for a reason. They take some input parameters, get or
64 But there are more complex fixes. For example, a patch might change
80 switching combined with kpatch's stack trace switching. There are also
119 (Note there's not yet such an approach for kthreads.)
142 There's also a /proc/<pid>/patch_state file which can be used to
150 actually delivered (there is no data in signal pending structures). Tasks are
155 /sys/kernel/livepatch/<patch>/force attribute. Writing 1 there clears
[all …]
|
| /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
|
| /Documentation/admin-guide/perf/ |
| D | qcom_l2_pmu.rst | 6 Centriq SoCs. There are multiple physical L2 cache clusters, each with their
9 There is one logical L2 PMU exposed, which aggregates the results from
18 a group of events. There are 8 groups. Only one entry from each
25 In addition there is a cycle counter event specified by the value 0xFE
|
| /Documentation/admin-guide/media/ |
| D | dvb_references.rst | 12 There are also some other old lists hosted at:
17 There, you'll find lots of information, from both development and usage
28 In order to get the needed firmware for some drivers to work, there's
|
| /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
|
| /Documentation/filesystems/ |
| D | debugfs.rst | 14 there. The debugfs filesystem is also intended to not serve as a stable
15 ABI to user space; in theory, there are no stability constraints placed on
16 files exported there. The real world is not always so simple, though [1]_;
103 architectures, though, complicating the situation somewhat. There are
112 Similarly, there are helpers for variables of type unsigned long, in decimal
153 can be used to export binary information, but there does not appear to be
200 There is a helper function to create a device-related seq_file::
212 There are a couple of other directory-oriented helper functions::
228 There is one important thing that all debugfs users must take into account:
229 there is no automatic cleanup of any directories created in debugfs. If a
[all …]
|
| /Documentation/driver-api/mmc/ |
| D | mmc-async-req.rst | 45 There is one new public function mmc_start_req().
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
56 There are two optional members in the mmc_host_ops -- pre_req() and
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
|
| /Documentation/power/ |
| D | basic-pm-debugging.rst | 49 there is the file /sys/power/pm_test that can be used to make the hibernation
50 core run in a test mode. There are 5 test modes available:
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,
[all …]
|
| /Documentation/userspace-api/media/rc/ |
| D | rc-protos.rst | 32 This IR protocol uses manchester encoding to encode 14 bits. There is a
77 There is a variant of rc5 called either rc5x or extended rc5
78 where there the second stop bit is the 6th command bit, but inverted.
81 done to keep it compatible with plain rc-5 where there are two start bits.
191 The sony protocol is a pulse-width encoding. There are three variants,
218 The sony protocol is a pulse-width encoding. There are three variants,
245 The sony protocol is a pulse-width encoding. There are three variants,
356 The scancode is the exact 16 bits as in the protocol. There is also a
365 as in the protocol. There is also a toggle bit.
373 as in the protocol. There is also a toggle bit.
[all …]
|
| /Documentation/hid/ |
| D | uhid.rst | 7 relies heavily on the definitions declared there.
13 There is an example user-space application in ./samples/uhid/uhid-example.c
44 The "type" field defines the payload. For each type, there is a
55 followed by a UHID_OPEN event again and so on. There is no need to perform
96 This destroys the internal HID device. No further I/O will be accepted. There
99 You can create a new device by sending UHID_CREATE2 again. There is no need to
158 there is actually no other process that reads your data so there is no need to
162 This is sent when there are no more processes which read the HID data. It is
175 The kernel serializes GET_REPORT requests so there will never be two in
|
| /Documentation/powerpc/ |
| D | pci_iov_resource_on_powernv.rst | 28 There is thus, in HW, a table of PE states that contains a pair of "frozen"
33 return all 1's value. MSIs are also blocked. There's a bit more state that
66 bridge being triggered. There's a PE# in the interrupt controller
75 from the CPU address space to the PCI address space. There is one M32
92 need to ensure Linux doesn't assign anything there, the M32 logic
115 address on the PowerBus). There is a way to also set the top 14
120 has 256 segments; however, there is no table for mapping a segment
124 there's a defined ordering for which window applies.
145 than one segment, we end up with more than one PE#. There is a HW
186 There are several strategies for isolating VFs in PEs:
[all …]
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | twl4030-charger.yaml | 11 charging is permissible, and when there is a connection or disconnection.
13 The choice of phy cannot be configured at a hardware level, so there is no
14 value in explicit configuration in device-tree. Rather if there is a sibling
|
| /Documentation/i2c/ |
| D | gpio-fault-injection.rst | 11 Once the Kconfig option I2C_GPIO_FAULT_INJECTOR is enabled, there will be an
13 mounted at /sys/kernel/debug. There will be a separate subdirectory per GPIO
48 there are I2C client devices which detect a stuck SDA on their side and release
49 it on their own after a few milliseconds. Also, there might be an external
74 because it acknowledges data. However, there are two differences compared to
103 There doesn't need to be a device at this address because arbitration lost
135 Note that there doesn't need to be a device listening to the address you are
|
| /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
|
| /Documentation/sound/cards/ |
| D | cmipci.rst | 12 channels can be used for front/rear playbacks. Since there are two
20 There are slight differences between the two DACs:
47 time.. Maybe there is an unknown register to achieve this...
50 playback should be routed there as default. If not, there is a
55 There are two more controls regarding to the rear output.
94 There are some control switches affecting to the speaker connections:
150 Additionally there are relevant control switches:
214 There are Master, PCM, Synth, CD, Line, Mic and PC Speaker playback
238 There is *no* hardware wavetable function on this chip (except for
|
| /Documentation/arch/openrisc/ |
| D | todo.rst | 6 since 2.6.35. There are, however, remaining items to be completed within
12 - Finish the renaming cleanup... there are references to or32 in the code
|
| /Documentation/ |
| D | Kconfig | 6 bool "Warn if there's a missing documentation file"
16 bool "Warn if there are errors at ABI files"
|
12345678910>>...67