Home
last modified time | relevance | path

Searched refs:owns (Results 1 – 25 of 40) sorted by relevance

12

/Linux-v5.4/drivers/gpu/vga/
Dvgaarb.c67 unsigned int owns; /* what does it owns */ member
261 vgaarb_dbg(dev, "%s: owns: %d\n", __func__, vgadev->owns); in __vga_tryget()
264 wants = rsrc & ~vgadev->owns; in __vga_tryget()
313 match = lwants & conflict->owns; in __vga_tryget()
343 conflict->owns &= ~match; in __vga_tryget()
347 conflict->owns &= ~VGA_RSRC_NORMAL_MEM; in __vga_tryget()
349 conflict->owns &= ~VGA_RSRC_NORMAL_IO; in __vga_tryget()
376 vgadev->owns |= wants; in __vga_tryget()
696 vgadev->owns |= VGA_RSRC_LEGACY_IO; in vga_arbiter_add_pci_device()
698 vgadev->owns |= VGA_RSRC_LEGACY_MEM; in vga_arbiter_add_pci_device()
[all …]
/Linux-v5.4/Documentation/locking/
Drt-mutex-design.rst37 that C owns and must wait and lets C run to release the lock. But in the
121 that a specific process owns.
141 A owns: L1
143 B owns L2
145 C owns L3
147 D owns L4
155 another mutex L5 where B owns L5 and F is blocked on mutex L5.
279 D owns L3
281 C owns L2
283 B owns L1
[all …]
/Linux-v5.4/arch/arm/vfp/
Dvfphw.S96 cmp r4, r10 @ this thread owns the hw context?
98 @ For UP, checking that this thread owns the hw context is
/Linux-v5.4/Documentation/devicetree/bindings/gpio/
Dgpio-nmk.txt17 - gpio-bank : Specifies which bank a controller owns.
Dmicrochip,pic32-gpio.txt22 - microchip,gpio-bank: Specifies which bank a controller owns.
/Linux-v5.4/arch/arm/kernel/
Diwmmxt.S89 str r0, [r3] @ this task now owns Concan regs
265 1: @ this task owns Concan regs -- grab a copy from there
332 teq r2, r3 @ next task owns it?
/Linux-v5.4/Documentation/block/
Dpr.rst26 Only the initiator that owns the reservation can write to the
30 Only the initiator that owns the reservation can access the
/Linux-v5.4/Documentation/devicetree/bindings/i2c/
Dnvidia,tegra186-bpmp-i2c.txt3 In Tegra186, the BPMP (Boot and Power Management Processor) owns certain HW
/Linux-v5.4/Documentation/filesystems/
Dhfsplus.txt20 Specifies the user/group that owns all files on the filesystem
Dhfs.txt24 Specifies the user/group that owns all files on the filesystems.
/Linux-v5.4/Documentation/gpu/
Dvgaarbiter.rst44 "<card_ID>,decodes=<io_state>,owns=<io_state>,locks=<io_state> (ic,mc)"
49 decodes, "owns" indicates what is currently enabled on it, and
138 VGA memory and IO afaik). If the card already owns the resources, the function
/Linux-v5.4/arch/arm/mach-ep93xx/
Dcrunch-bits.S82 str r0, [r3] @ this task now owns crunch
272 1: @ this task owns crunch regs -- grab a copy from there
/Linux-v5.4/Documentation/devicetree/bindings/mailbox/
Dxlnx,zynqmp-ipi-mailbox.txt6 agent owns registers used for notification and buffers for message.
/Linux-v5.4/Documentation/i2c/busses/
Di2c-sis96x.rst47 chipsets as well: 635, and 635T. If anyone owns a board with those chips
/Linux-v5.4/Documentation/core-api/
Dlocal_ops.rst40 CPU which owns the data. Therefore, care must taken to make sure that only one
122 relatively to other memory writes happening on the CPU that owns the data::
/Linux-v5.4/Documentation/
Dpi-futex.txt93 yet then the code looks up the task that owns the futex [it has put its
101 perform - it now owns the lock, and futex value contains
/Linux-v5.4/Documentation/admin-guide/LSM/
DSafeSetID.rst75 Linux checks for capabilities based off of the user namespace that ???owns??? some
80 that owns the network namespace -- not necessarily the user namespace under
/Linux-v5.4/Documentation/ABI/testing/
Dsysfs-bus-i3c12 Expose the master that owns the bus (<bus-id>-<master-pid>) at
Dsysfs-bus-rapidio95 device that that owns this attribute
/Linux-v5.4/Documentation/devicetree/bindings/mmc/
Dmarvell,xenon-sdhci.txt6 Each SDHC is independent and owns independent resources, such as register sets,
/Linux-v5.4/Documentation/fpga/
Ddfl.rst307 #. The PF owns all AFU ports by default. Any port that needs to be
312 to enable SRIOV and VFs. Each VF owns only one Port with AFU.
/Linux-v5.4/drivers/staging/unisys/Documentation/
Doverview.txt230 partition that owns the shared SCSI adapter, using a channel between the
262 partition that owns the shared network interface, using a channel
/Linux-v5.4/Documentation/driver-api/
Dparport-lowlevel.rst647 A return value of zero indicates that the caller still owns the port
651 the caller still owns the port and the call blocked.
653 A return value of -EAGAIN indicates that the caller no longer owns the
/Linux-v5.4/fs/reiserfs/
DREADME85 funding for the first 5.5 years, and one of the programmers. He owns
/Linux-v5.4/Documentation/virt/kvm/
Dmsr.txt239 preempted: indicate the vCPU who owns this struct is running or

12