Home
last modified time | relevance | path

Searched full:well (Results 1 – 25 of 5252) sorted by relevance

12345678910>>...211

/OK3568_Linux_fs/kernel/drivers/gpu/drm/i915/display/
H A Dintel_display_power.h119 * Synchronize the well's hw state to match the current sw state, for
127 * Enable the well and resources that depend on it (for example
128 * interrupts located on the well). Called after the 0->1 refcount
134 * Disable the well and resources that depend on it. Called after
151 /* Power well structure for haswell */
156 /* unique identifier for this power well */
159 * Arbitraty data associated with this power well. Platform and power
160 * well specific.
165 * request/status flag index in the PUNIT power well
176 * request/status flag index in the power well
[all …]
H A Dintel_display_power.c189 "Use count on power well %s is already zero", in intel_power_well_put()
243 * threads can't disable the power well while the caller tries to read a few
265 * Starting with Haswell, we have a "Power Down Well" that can be turned off
266 * when not needed anymore. We have 4 registers that can request the power well
339 drm_dbg_kms(&dev_priv->drm, "%s power well enable timeout\n", in hsw_wait_for_power_well_enable()
374 * - a KVMR request on any power well via the KVMR request register in hsw_wait_for_power_well_disable()
415 * before enabling the power well and PW1/PG1's own fuse in hsw_power_well_enable()
690 * We should only use the power well if we explicitly asked the hardware to
731 "Power well 2 on.\n"); in assert_can_enable_dc9()
979 * the first power well and hope the WARN gets reported so we can fix in lookup_power_well()
[all …]
H A Dintel_vga.c61 * at a very early point in our resume sequence, where the power well in intel_vga_redisable()
64 * level, just check if the power well is enabled instead of trying to in intel_vga_redisable()
65 * follow the "don't touch the power well if we don't need it" policy in intel_vga_redisable()
82 * After we re-enable the power well, if we touch VGA register 0x3d5 in intel_vga_reset_io_mem()
/OK3568_Linux_fs/yocto/poky/bitbake/lib/toaster/toastergui/templates/
H A Dproject_specific.html63 <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 Dproject.html63 <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 Dbuilddashboard.html83 …<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">
/OK3568_Linux_fs/kernel/drivers/misc/echo/
H A Decho.h41 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
/OK3568_Linux_fs/yocto/poky/documentation/test-manual/
H A Dyocto-project-compatible.rst12 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.
/OK3568_Linux_fs/kernel/Documentation/netlabel/
H A Dintroduction.rst24 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 Dlsm_interface.rst35 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.
/OK3568_Linux_fs/kernel/drivers/input/tablet/
H A DKconfig23 (CONFIG_INPUT_EVDEV) as well.
36 support" (CONFIG_INPUT_EVDEV) as well.
48 (CONFIG_INPUT_EVDEV) as well.
72 (CONFIG_INPUT_EVDEV) as well.
/OK3568_Linux_fs/kernel/include/drm/
H A Ddrm_audio_component.h19 * @get_power: get the POWER_DOMAIN_AUDIO power well
21 * Request the power well to be turned on.
28 * @put_power: put the POWER_DOMAIN_AUDIO power well
30 * Allow the power well to be turned off.
/OK3568_Linux_fs/kernel/Documentation/maintainer/
H A Drebasing-and-merging.rst91 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
/OK3568_Linux_fs/kernel/drivers/usb/gadget/udc/
H A DKconfig153 It has fifteen fixed-function endpoints, as well as endpoint
214 It has up to 23 endpoints, as well as endpoint zero (for
227 endpoints, as well as endpoint zero (for control transfers).
242 8 endpoints, as well as endpoint zero.
351 It has three configurable endpoints, as well as endpoint zero
374 It has six configurable endpoints, as well as endpoint zero
384 It has eight configurable endpoints, as well as endpoint zero
438 endpoints(bulk or interrupt or isochronous), as well as
/OK3568_Linux_fs/kernel/Documentation/admin-guide/cifs/
H A Dintroduction.rst5 This is the client VFS module for the SMB3 NAS protocol as well
16 Server), as well as by Samba (which provides excellent
18 operating systems). Apple systems also support SMB3 well, as
/OK3568_Linux_fs/kernel/Documentation/networking/
H A Dframerelay.rst17 The configuration script will ask you how many DLCIs you need, as well as
29 them as well.
33 to specify the types of boards to be configured as FRADs, as well as perform
/OK3568_Linux_fs/kernel/Documentation/admin-guide/media/
H A Dcafe_ccic.rst17 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.
/OK3568_Linux_fs/u-boot/drivers/tpm/
H A DKconfig90 The functionality is available via the 'tpm' command as well.
98 The functionality is available via the 'tpm' command as well.
105 The functionality is available via the 'tpm' command as well.
/OK3568_Linux_fs/kernel/Documentation/i2c/busses/
H A Di2c-sis96x.rst47 chipsets as well: 635, and 635T. If anyone owns a board with those chips
48 AND is willing to risk crashing & burning an otherwise well-behaved kernel
51 reports and/or success stories as well.
/OK3568_Linux_fs/u-boot/doc/driver-model/
H A Dfdt-fixup.txt45 well, is being used in more and more drivers, the same problem of altering the
46 device tree starts cropping up in U-Boot itself as well.
111 detected components are added to the device tree, as well as a "subtractive"
113 as well as a combination of both approaches should work.
/OK3568_Linux_fs/yocto/poky/documentation/
H A Dtransitioning-to-a-custom-environment.rst13 important information learned from other users. You're well prepared. But
53 well. Each layer has a ``README`` document that you can look at for this type of
101 well as the package feed and possibly the update solution. You would create
113 #. **Congratulations! You're well on your way.**
/OK3568_Linux_fs/kernel/Documentation/x86/
H A Dkernel-stacks.rst74 Using a separate stack allows the kernel to recover from it well enough
140 or not - but in most cases we'll get the call chain right as well. The
142 information from that as well.
147 we still print out the real call chain as well - just with more question
/OK3568_Linux_fs/kernel/Documentation/bpf/
H A Dbpf_devel_QA.rst22 A: Since all BPF kernel development as well as bpftool and iproute2 BPF
38 the actual commit authors in Cc as well for the report. They can
55 lists and maintainers from there as well, so they are able to review
263 bpftool should be extended as well to support dumping them.
269 iproute2's BPF loader as well from user space side. This is not only
274 Q: Do you accept patches as well for iproute2's BPF loader?
281 please keep them in Cc as well, so they can be reviewed.
333 that would require BPF JIT and/or LLVM integration as well?
381 Q: The BPF patch I am about to submit needs to go to stable as well
458 from that kernel ``xyz`` as well. Do not expect that the BPF selftest
[all …]
/OK3568_Linux_fs/kernel/drivers/staging/media/ipu3/
H A DTODO5 as well as formats and the binary used to a request. Remove the
12 documentation. This may require driver changes as well.
/OK3568_Linux_fs/buildroot/boot/grub2/
H A D0133-kern-efi-Add-initial-stack-protector-implementation.patch54 +[# `$CC -c -o ...' might not be portable. But, oh, well... Is calling
58 + [# Should we clear up other files as well, having called `AC_LANG_CONFTEST'?
71 +[# `$CC -c -o ...' might not be portable. But, oh, well... Is calling
75 + [# Should we clear up other files as well, having called `AC_LANG_CONFTEST'?
136 +# `$CC -c -o ...' might not be portable. But, oh, well... Is calling
141 + # Should we clear up other files as well, having called `AC_LANG_CONFTEST'?
159 +# `$CC -c -o ...' might not be portable. But, oh, well... Is calling
164 + # Should we clear up other files as well, having called `AC_LANG_CONFTEST'?

12345678910>>...211