Home
last modified time | relevance | path

Searched full:managing (Results 1 – 25 of 285) sorted by relevance

12345678910>>...12

/linux/include/video/
H A Dtgafb.h69 * Useful defines for managing the registers
110 * Useful defines for managing the ICS1562 PLL clock
118 * Useful defines for managing the BT485 on the 8-plane TGA
144 * Useful defines for managing the BT463 on the 24-plane TGAs/SFB+s
172 * Useful defines for managing the BT459 on the 8-plane SFB+s
/linux/tools/virtio/virtio-trace/
H A Dtrace-agent.h11 * agent_info - structure managing total information of guest agent
16 * @rw_ti: structure managing information of read/write threads
27 * rw_thread_info - structure managing a read/write thread a cpu
/linux/Documentation/admin-guide/device-mapper/
H A Dpersistent-data.rst64 implementations: a simpler one for managing blocks on a different
65 device (eg. thinly-provisioned data blocks); and one for managing
67 its own data within the space it's managing.
/linux/drivers/net/pcs/
H A DKconfig18 This module provides helpers to phylink for managing the Lynx PCS
25 This module provides helpers to phylink for managing the LynxI PCS
/linux/net/
H A Ddevres.c59 * @dev: managing device for this netdev - usually the parent device
63 * function will be called automatically when the managing device is
/linux/drivers/net/ethernet/altera/
H A Daltera_sgdma.c441 * assumes the caller is managing and holding a mutual exclusion
452 * assumes the caller is managing and holding a mutual exclusion
463 * assumes the caller is managing and holding a mutual exclusion
476 * assumes the caller is managing and holding a mutual exclusion
489 * assumes the caller is managing and holding a mutual exclusion
/linux/drivers/cpufreq/
H A Dcpufreq_userspace.c84 pr_debug("started managing cpu %u\n", policy->cpu); in cpufreq_userspace_policy_start()
97 pr_debug("managing cpu %u stopped\n", policy->cpu); in cpufreq_userspace_policy_stop()
/linux/arch/riscv/include/asm/
H A Dbugs.h3 * Interface for managing mitigations for riscv vulnerabilities.
/linux/drivers/pmdomain/rockchip/
H A DKconfig14 mode. The RK3288 PMU is dedicated for managing the power of the whole chip.
/linux/drivers/interconnect/
H A DKconfig8 managing the interconnects in a SoC.
/linux/Documentation/driver-api/
H A Daperture.rst3 Managing Ownership of the Framebuffer Aperture
/linux/Documentation/devicetree/bindings/interconnect/
H A Dqcom,rpm-common.yaml13 RPM interconnect providers support for managing system bandwidth requirements
/linux/Documentation/tee/
H A Dtee.rst20 - Managing shared memory between Linux and the TEE
/linux/drivers/bcma/
H A DREADME12 devices is used for managing Broadcom specific core.
/linux/drivers/virt/
H A DKconfig34 1) An ioctl interface for querying and managing partitions.
/linux/Documentation/admin-guide/mm/
H A Dindex.rst6 for managing the memory in the system. This includes implementation of
/linux/drivers/net/ipa/
H A Dipa_smp2p.h46 * for managing this notification.
/linux/Documentation/devicetree/bindings/clock/
H A Drockchip,rv1126-cru.yaml42 Phandle to the syscon managing the "general register files" (GRF),
H A Dhi6220-clock.txt28 - hisilicon,hi6220-clk-sram: phandle to the syscon managing the SoC internal sram;
H A Drockchip,rk3588-cru.yaml48 phandle to the syscon managing the "general register files". It is used
/linux/Documentation/devicetree/bindings/devfreq/event/
H A Drockchip,dfi.yaml36 Phandle to the syscon managing the "PMU general register files".
/linux/drivers/dma/qcom/
H A DKconfig42 start managing the channels. In a virtualized environment,
/linux/drivers/platform/surface/
H A DKconfig84 SSAM subsystems. In some subsystems, notably the BAS subsystem managing
86 managing type-cover devices in the Surface Pro 8 and Surface Pro X,
/linux/Documentation/devicetree/bindings/arm/keystone/
H A Dti,k3-sci-common.yaml14 that is responsible for managing various SoC-level resources like clocks,
/linux/Documentation/target/
H A Dtcmu-design.rst22 c) Managing the command ring
291 c) Managing the command ring: Parsing operations and commands,
346 c) Managing the command ring::

12345678910>>...12