| /linux-6.15/tools/memory-model/litmus-tests/ |
| H A 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.15/Documentation/locking/ |
| H A 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) 96 In the common case, at do_exit() time, there is no list registered, so 109 list is done after the futex is acquired by glibc, there is a few 110 instructions window for the thread (or process) to die there, leaving 145 - the implementation and the locking is "obvious", and there are no [all …]
|
| /linux-6.15/Documentation/devicetree/bindings/regulator/ |
| H A 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.15/Documentation/ABI/testing/ |
| H A 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
|
| H A 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
|
| /linux-6.15/Documentation/timers/ |
| H A 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 160 4. If there are more perf events pending than the hardware can 256 * Adaptive-ticks does not do anything unless there is only one 257 runnable task for a given CPU, even though there are a number 264 this CPU, so there is no point in sending a scheduling-clock 270 And even when there are multiple runnable tasks on a given CPU, 271 there is little point in interrupting that CPU until the current 280 runtime, there would need to be an earthshakingly good reason. [all …]
|
| /linux-6.15/Documentation/devicetree/bindings/power/supply/ |
| H A 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
|
| /linux-6.15/arch/arm/vfp/ |
| H A 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.15/arch/arm64/boot/dts/qcom/ |
| H A D | apq8094-sony-xperia-kitakami-karin_windy.dts | 8 /* As the names may imply, there is quite a bunch of duplication there. */
|
| /linux-6.15/Documentation/userspace-api/media/v4l/ |
| H A 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.15/Documentation/trace/coresight/ |
| H A 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.15/Documentation/ |
| H A D | Kconfig | 6 bool "Warn if there's a missing documentation file" 16 bool "Warn if there are errors at ABI files"
|
| /linux-6.15/Documentation/process/ |
| H A 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.15/Documentation/devicetree/bindings/i2c/ |
| H A D | i2c-gate.yaml | 16 there are no competing masters to consider for gates and therefore there is
|
| /linux-6.15/Documentation/maintainer/ |
| H A 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.15/Documentation/filesystems/ext4/ |
| H A 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
|
| H A 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.15/drivers/gpu/drm/i915/ |
| H A 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.15/Documentation/images/ |
| H A 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.15/Documentation/ABI/stable/ |
| H A 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.15/Documentation/driver-api/mmc/ |
| H A 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.15/Documentation/devicetree/bindings/ |
| H A 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.15/Documentation/driver-api/media/drivers/ |
| H A 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.15/Documentation/devicetree/bindings/interconnect/ |
| H A D | samsung,exynos-bus.yaml | 33 bus device. If there are three blocks which share the VDD_xxx power line, 48 - In case of Exynos3250, there are two power line as following:: 92 - In case of Exynos4210, there is one power line as following:: 109 - In case of Exynos4x12, there are two power line as following:: 127 - In case of Exynos5422, there are two power line as following:: 146 - In case of Exynos5433, there is VDD_INT power line as following::
|
| /linux-6.15/Documentation/power/ |
| H A 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 …]
|