/openbmc/linux/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
|
/openbmc/u-boot/arch/mips/mach-bmips/ |
H A D | Kconfig | 136 Between its different peripherals there's an integrated switch with 4 147 Between its different peripherals there's an integrated switch with 4 158 Between its different peripherals there's an integrated switch with 4 169 Between its different peripherals there's a BCM5325 switch with 4 180 Between its different peripherals there's an integrated switch with 4 191 Between its different peripherals there's a BCM53115 switch with 5 202 Between its different peripherals there's a BCM5325 switch with 4 213 Between its different peripherals there's a BCM53115 switch with 4 224 Between its different peripherals there's a BCM53125 switch with 5 235 Between its different peripherals there's a BCM5325 switch with 4 [all …]
|
/openbmc/linux/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) 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 …]
|
/openbmc/linux/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
|
/openbmc/openbmc/meta-yadro/recipes-phosphor/ipmi/phosphor-ipmi-host/ |
H A D | 0001-Add-support-for-persistent-only-settings.patch | 40 + // If there are no objects implementing the requested interface, 48 + // On the contrary, if there is just one object, that may mean 52 + // If there's just one object, that's the only kind of setting 59 + // Something must be wrong if there are more objects than expected 66 + // We are here because there were exactly two objects implementing the
|
/openbmc/openbmc/poky/meta/recipes-sato/matchbox-keyboard/files/ |
H A D | 0001-desktop-file-Hide-the-keyboard-from-app-list.patch | 6 matchbox-keyboard is not a normal app and there's no need to start 8 * when there's no hardware keyboard, the panel applet can be used to 10 * when there is a hardware keyboard, matchbox-keyboard can still be
|
/openbmc/linux/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
|
/openbmc/u-boot/doc/driver-model/ |
H A D | serial-howto.txt | 11 forward to convert these, at some point there may come a patch to remove them! 19 - Your board should then build, but will not boot since there will be no serial 40 - update the Makefile there 41 - Add stdout-path to your /chosen device tree node if it is not already there
|
H A D | i2c-howto.txt | 21 forward to convert these, at some point there may come a patch to remove them! 29 - Your board should then build, but will not work fully since there will be 50 - update the Makefile there 51 - Add stdout-path to your /chosen device tree node if it is not already there
|
H A D | pci-info.txt | 23 If there is no alias the devices will be numbered sequentially in the device 28 bound to their appropriate driver if available. If there is no driver, then 42 bus, albeit there are justified exceptions. If the compatible string is 96 bus hierarchy: on the root PCI bus, there is a PCIe root port which connects 114 With sandbox we need a device emulator for each device on the bus since there 127 This means that there is a 'sandbox,swap-case' driver at that bus position.
|
/openbmc/linux/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 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 163 4. If there are more perf events pending than the hardware can [all …]
|
/openbmc/linux/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?
|
/openbmc/linux/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. */
|
/openbmc/linux/Documentation/networking/device_drivers/ethernet/toshiba/ |
H A 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,
|
/openbmc/linux/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
|
/openbmc/linux/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
|
/openbmc/openbmc-test-automation/ffdc/docs/ |
H A D | plugin.md | 167 plugin response if there is any will be written to named file, if 185 - exit_on_error : If there was an error in a plugin stacked, the subsequent 187 - continue_on_error : If there was an error and user declare this directive, 200 This error directive would come into force only if there is an error detected by 204 To go further, there is another directive for plugin to check if the plugin
|
/openbmc/linux/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 …]
|
/openbmc/linux/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"
|
/openbmc/linux/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::
|
/openbmc/linux/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
|
/openbmc/linux/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.
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Control/Service/ |
H A D | README.md | 21 each instance of the service there will be a D-Bus object 22 `/xyz/openbmc_project/control/service/<service-name>`. For example, if there are 23 two instances of `phosphor-ipmi-net` then there will be two D-Bus objects 45 if the service is disabled, on the next boot it can be started if there are
|
/openbmc/openbmc/poky/meta/recipes-support/libyaml/ |
H A D | libyaml_0.2.5.bb | 22 CVE_STATUS[CVE-2024-35326] = "upstream-wontfix: Upstream thinks there is no working code that is ex… 23 CVE_STATUS[CVE-2024-35328] = "upstream-wontfix: Upstream thinks there is no working code that is ex…
|