Home
last modified time | relevance | path

Searched refs:well (Results 1 – 25 of 1015) sorted by relevance

12345678910>>...41

/linux-6.6.21/Documentation/netlabel/
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
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.
/linux-6.6.21/drivers/staging/media/ipu3/
DTODO5 as well as formats and the binary used to a request. Remove the
12 documentation. This may require driver changes as well.
/linux-6.6.21/Documentation/devicetree/bindings/net/
Dbrcm,bcm6368-mdio-mux.yaml13 This MDIO bus multiplexer defines buses that could be internal as well as
15 properties as well to generate desired MDIO transaction on appropriate bus.
Dbrcm,mdio-mux-iproc.yaml13 This MDIO bus multiplexer defines buses that could be internal as well as
16 properties as well to generate desired MDIO transaction on appropriate bus.
Dfaraday,ftmac.txt5 - compatible : Must contain "faraday,ftmac", as well as one of
/linux-6.6.21/drivers/gpu/drm/i915/display/
Dintel_display_power.c1440 struct i915_power_well *well; in skl_display_core_init() local
1453 well = lookup_power_well(dev_priv, SKL_DISP_PW_1); in skl_display_core_init()
1454 intel_power_well_enable(dev_priv, well); in skl_display_core_init()
1456 well = lookup_power_well(dev_priv, SKL_DISP_PW_MISC_IO); in skl_display_core_init()
1457 intel_power_well_enable(dev_priv, well); in skl_display_core_init()
1472 struct i915_power_well *well; in skl_display_core_uninit() local
1495 well = lookup_power_well(dev_priv, SKL_DISP_PW_1); in skl_display_core_uninit()
1496 intel_power_well_disable(dev_priv, well); in skl_display_core_uninit()
1506 struct i915_power_well *well; in bxt_display_core_init() local
1524 well = lookup_power_well(dev_priv, SKL_DISP_PW_1); in bxt_display_core_init()
[all …]
/linux-6.6.21/drivers/gpu/drm/ci/
Dbuild.yml65 # Would be good to have DEBUG_KMEMLEAK, but it doesn't work well with any of
77 # Would be good to have DEBUG_KMEMLEAK, but it doesn't work well with any of
89 # Would be good to have DEBUG_KMEMLEAK, but it doesn't work well with any of
/linux-6.6.21/Documentation/i2c/busses/
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.
/linux-6.6.21/Documentation/admin-guide/cifs/
Dintroduction.rst5 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
/linux-6.6.21/Documentation/admin-guide/laptops/
Dtoshiba_haps.rst28 userspace tools or daemons act accordingly, as well as providing a sysfs
48 any "protection" as well as failing during the evaluation of the _STA method
77 level, as well as set the desired protection level, the
/linux-6.6.21/Documentation/admin-guide/media/
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.
/linux-6.6.21/drivers/input/tablet/
DKconfig23 (CONFIG_INPUT_EVDEV) as well.
36 support" (CONFIG_INPUT_EVDEV) as well.
60 (CONFIG_INPUT_EVDEV) as well.
/linux-6.6.21/Documentation/hwmon/
Daquacomputer_d5next.rst29 virtual temperature sensors, as well as two flow sensors. The fans expose their
34 and current, as well as coolant temperature and eight virtual temp sensors. Also
46 The Octo exposes four physical and sixteen virtual temperature sensors, as well as
67 and fan IC. It also exposes pump and fan speeds (in RPM), voltages, as well as pump
Ddrivetemp.rst28 as well as historic minimum and maximum temperatures. If SCT Command
38 drives as well. The same behavior is observed if the 'hdtemp' or 'smartd'
/linux-6.6.21/Documentation/devicetree/bindings/nvmem/layouts/
Donie,tlv-layout.yaml15 content is well specified and gives many information about the manufacturer
16 (name, country of manufacture, etc) as well as device caracteristics (serial
/linux-6.6.21/drivers/net/wireless/cisco/
DKconfig27 - with or without encryption) as well as card before the Cisco
50 - with or without encryption) as well as card before the Cisco
/linux-6.6.21/drivers/comedi/
DTODO7 - cleanup the individual comedi drivers as well
/linux-6.6.21/Documentation/sound/cards/
Dpcmtest.rst7 testing/fuzzing of the userspace ALSA applications, as well as for testing/fuzzing of
26 RESET ioctl, and the selftest covers this PCM API functionality as well.
49 for each channel, as well as entries which contain the pattern buffer length.
/linux-6.6.21/Documentation/driver-api/media/drivers/ccs/
Dccs.rst19 The pixel array sub-device represents the camera sensor's pixel matrix, as well
43 sink pad (0) as well.
108 capabilities as well as board configuration and user specified configuration. As
/linux-6.6.21/Documentation/RCU/
DNMI-RCU.rst9 handlers, as well as dynamic irq handlers. This document describes
82 dummy_nmi_handler(). However, there may well be an NMI handler
109 The caller to set_nmi_callback() might well have
/linux-6.6.21/Documentation/admin-guide/
Dnumastat.rst9 The numa_hit, numa_miss and numa_foreign counters reflect how well processes
46 well right now on machines with a small number of CPUs.
/linux-6.6.21/Documentation/crypto/
Dindex.rst10 for cryptographic use cases, as well as programming examples.
/linux-6.6.21/net/netlabel/
DKconfig14 Documentation/netlabel as well as the NetLabel SourceForge project
/linux-6.6.21/Documentation/maintainer/
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

12345678910>>...41