/openbmc/phosphor-objmgr/src/ |
H A D | processing.hpp | 28 /** @brief Get well known name of input unique name 30 * If user passes in well known name then that will be returned. 34 * @param[out] wellKnown - The well known name if found 36 * @return True if well known name is found, false otherwise 56 * @param[in,out] nameOwners - Map of unique name to well known name 57 * @param[in] wellKnown - Well known name that has new owner 77 * @param[in] wellKnown - Well known name that has new owner
|
/openbmc/linux/drivers/gpu/drm/i915/display/ |
H A D | intel_display_power_well.h | 60 /* unique identifier for this power well */ 63 * Arbitraty data associated with this power well. Platform and power 64 * well specific. 69 * request/status flag index in the PUNIT power well 79 * request/status flag index in the power well 103 * the well enabled. 121 /* power well enable/disable usage count */
|
H A D | intel_display_power.c | 250 * threads can't disable the power well while the caller tries to read a few 302 * This function set the "DC off" power well target_dc_state, 303 * based upon this target_dc_stste, "DC off" power well will 326 * If DC off power well is disabled, need to enable and disable the in intel_display_power_set_target_dc_state() 327 * DC off power well to effect target DC state. in intel_display_power_set_target_dc_state() 650 * power well disabling. in release_async_put_domains() 1167 * expect us to program the abox_ctl0 register as well, even though in icl_mbus_init() 1207 "Display power well on\n"); in assert_can_disable_lcpll() 1377 * well is disabled and most interrupts are disabled, and these are also 1440 struct i915_power_well *well; in skl_display_core_init() local [all …]
|
H A D | intel_vga.c | 67 * at a very early point in our resume sequence, where the power well in intel_vga_redisable() 70 * level, just check if the power well is enabled instead of trying to in intel_vga_redisable() 71 * follow the "don't touch the power well if we don't need it" policy in intel_vga_redisable() 88 * After we re-enable the power well, if we touch VGA register 0x3d5 in intel_vga_reset_io_mem()
|
/openbmc/openbmc/poky/bitbake/lib/toaster/toastergui/templates/ |
H A D | project.html | 63 <div class="well well-transparent" id="machine-section"> 80 <div class="well well-transparent" id="distro-section"> 97 <div class="well well-transparent"> 111 <div class="well well-transparent"> 131 <div class="well well-transparent" id="layer-container">
|
H A D | project_specific.html | 63 <div class="well well-transparent" id="machine-section"> 80 <div class="well well-transparent" id="distro-section"> 96 <div class="well well-transparent"> 109 <div class="well well-transparent"> 129 <div class="well well-transparent" id="layer-container">
|
H A D | builddashboard.html | 83 …<div class="well well-transparent dashboard-section" data-artifacts-for-target="{{target.target.pk… 185 <div class="well well-transparent dashboard-section"> 210 <div class="well well-transparent"> 220 <div class="well well-transparent"> 270 <div class="well well-transparent">
|
/openbmc/linux/drivers/misc/echo/ |
H A D | echo.h | 41 well. However, it only works well for signals of constant amplitude. It works 44 similar to applying AGC - LMS can work as well for a signal of varying 53 the NLMS algorithm works very well. However, speech has more low frequency than 60 An FIR filter adapted using pre-whitened NLMS performs well, provided certain 70 noise like, such as voice) the adaption works very well. If the adaption is 78 since at least it cancels the tones. Allowing a well converged canceller to
|
/openbmc/linux/Documentation/netlabel/ |
H A D | introduction.rst | 24 engine will handle those tasks as well. Other kernel subsystems should 37 formatting of these NetLabel messages as well as the Generic NETLINK family 39 header files as well as in 'include/net/netlabel.h'. 51 'include/net/netlabel.h' header file as well as the 'lsm_interface.txt' file
|
H A D | lsm_interface.rst | 35 on outgoing packets as well as read the labels on incoming packets. Functions 36 exist to operate both on sockets as well as the sk_buffs directly. These high 53 bypassed as well which should result in a significant reduction in overhead.
|
/openbmc/openbmc/poky/documentation/test-manual/ |
H A D | yocto-project-compatible.rst | 12 that while some layers were popular and worked well, others developed a 14 interoperate well with others and tended to assume they controlled all 43 to operate well together. "anti-patterns" were also found, preventing layers 44 from working well together. 47 compatibility tests, it is considered "well behaved" and should operate 48 and cooperate well with other compatible layers.
|
/openbmc/qemu/tests/multiboot/ |
H A D | aout_kludge.S | 46 /* Well-behaved kernel file with explicit bss_end */ 53 /* Well-behaved kernel file with default bss_end */ 60 /* Well-behaved kernel file with default load_end */ 67 /* Well-behaved kernel file with load_end < data_end and bss > data_end */
|
/openbmc/linux/Documentation/maintainer/ |
H A D | rebasing-and-merging.rst | 91 well-known starting point, and they are well tested, the potential for 140 Such merges need to be carefully thought about and well justified, or 155 a well-managed branch. 159 merge to a well-known stable point, rather than to some random commit. 198 merging of your tree as well. Preferable alternatives include agreeing 211 in the tree. As always, such a merge should pick a well-known release
|
/openbmc/u-boot/drivers/firmware/ |
H A D | ti_sci.c | 126 * return corresponding error, else if all goes well, 286 * Return: 0 if all went well, else returns appropriate error value. 336 * Return: 0 if all went well, else returns appropriate error value. 353 * Return: 0 if all went well, else returns appropriate error value. 371 * Return: 0 if all went well, else returns appropriate error value. 389 * Return: 0 if all went well, else returns appropriate error value. 406 * Return: 0 if all went well, else returns appropriate error value. 787 * Return: 0 if all went well, else returns appropriate error value. 842 * Return: 0 if all went well, else returns appropriate error value. 905 * Return: 0 if all went well, else returns appropriate error value. [all …]
|
/openbmc/linux/include/drm/ |
H A D | drm_audio_component.h | 22 * @get_power: get the POWER_DOMAIN_AUDIO power well 24 * Request the power well to be turned on. 31 * @put_power: put the POWER_DOMAIN_AUDIO power well 33 * Allow the power well to be turned off.
|
/openbmc/openbmc/meta-security/meta-tpm/recipes-tpm1/openssl-tpm-engine/files/ |
H A D | 0001-create-tpm-key-support-well-known-key-option.patch | 7 support well-known password in openssl-tpm-engine. 9 Add "-z" option to select well known password in create_tpm_key tool. 21 +#define TPM_WELL_KNOWN_KEY_LEN 20 /*well know key length is 20 bytes zero*/ 30 + "\t\t-z|--zerokey use well known 20 bytes zero as SRK password.\n"
|
/openbmc/docs/designs/ |
H A D | entity-manager-hw-id-vpd-discover-via-device-tree.md | 27 decode IPMI-FRU storage formatted blobs, as well as the Tyan data format. 87 '/serial-number,' which both have well-known paths in the device tree 111 potentially for other hardware as well). 166 1. Has no well-known handles for common properties like /model or /serial-number 168 'well-known' properties 172 'model' instead of the well known device-tree /model handle would add 174 3. Since /model is well described in device-tree documentation, there is 183 1. Is a well-established device-tree node 317 well-defined location? Inventory.Decorator.[Asset] = Model
|
/openbmc/linux/Documentation/admin-guide/cifs/ |
H A D | introduction.rst | 5 This is the client VFS module for the SMB3 NAS protocol as well 16 well as by Samba (which provides excellent CIFS/SMB2/SMB3 server 18 Apple systems also support SMB3 well, as do most Network Attached
|
/openbmc/linux/drivers/input/tablet/ |
H A D | Kconfig | 23 (CONFIG_INPUT_EVDEV) as well. 36 support" (CONFIG_INPUT_EVDEV) as well. 60 (CONFIG_INPUT_EVDEV) as well.
|
/openbmc/linux/drivers/gpu/drm/ci/ |
H A D | build.yml | 66 # Would be good to have DEBUG_KMEMLEAK, but it doesn't work well with any of 78 # Would be good to have DEBUG_KMEMLEAK, but it doesn't work well with any of 90 # Would be good to have DEBUG_KMEMLEAK, but it doesn't work well with any of
|
/openbmc/linux/Documentation/admin-guide/media/ |
H A D | cafe_ccic.rst | 17 well, but that is a debugging aid which will be removed shortly). VGA and 34 loading via sysfs as well: 49 systems, however, it will work well with only two.
|
/openbmc/qemu/tests/keys/ |
H A D | README | 1 This folder contains a well-known ssh key pair used in QEMU tests. 5 run. Because the private key is well-known, care must be taken to use the key
|
/openbmc/linux/drivers/gpu/drm/i915/gt/ |
H A D | intel_gt_pm_debugfs.c | 100 seq_printf(m, "Render Power Well: %s\n", in vlv_drpc() 102 seq_printf(m, "Media Power Well: %s\n", in vlv_drpc() 138 seq_printf(m, "Render Well Gating Enabled: %s\n", in gen6_drpc() 140 seq_printf(m, "Media Well Gating Enabled: %s\n", in gen6_drpc() 173 seq_printf(m, "Render Power Well: %s\n", in gen6_drpc() 176 seq_printf(m, "Media Power Well: %s\n", in gen6_drpc() 277 seq_printf(m, "Media Well Gating Enabled: %s\n", in mtl_drpc() 280 seq_printf(m, "Render Well Gating Enabled: %s\n", in mtl_drpc() 300 seq_printf(m, "Media Power Well: %s\n", in mtl_drpc() 304 seq_printf(m, "Render Power Well: %s\n", in mtl_drpc()
|
/openbmc/linux/drivers/staging/media/ipu3/ |
H A D | TODO | 5 as well as formats and the binary used to a request. Remove the 12 documentation. This may require driver changes as well.
|
/openbmc/linux/arch/x86/include/asm/fpu/ |
H A D | api.h | 45 * 32-bit kernel code may use 387 operations as well as SSE2, etc, in kernel_fpu_begin() 65 * implicitly prevents bottom half processing as well. 106 * Query the presence of one or more xfeatures. Works on any legacy CPU as well. 109 * the feature there as well - this can be used to print error (or success)
|