Home
last modified time | relevance | path

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

12

/linux-6.6.21/drivers/pci/
Dvgaarb.c46 unsigned int owns; /* what it owns */ member
231 vgaarb_dbg(dev, "%s: owns: %d\n", __func__, vgadev->owns); in __vga_tryget()
234 wants = rsrc & ~vgadev->owns; in __vga_tryget()
281 match = lwants & conflict->owns; in __vga_tryget()
311 conflict->owns &= ~match; in __vga_tryget()
315 conflict->owns &= ~VGA_RSRC_NORMAL_MEM; in __vga_tryget()
317 conflict->owns &= ~VGA_RSRC_NORMAL_IO; in __vga_tryget()
342 vgadev->owns |= wants; in __vga_tryget()
641 (boot_vga->owns & VGA_RSRC_LEGACY_MASK) == VGA_RSRC_LEGACY_MASK) in vga_is_boot_device()
644 if ((vgadev->owns & VGA_RSRC_LEGACY_MASK) == VGA_RSRC_LEGACY_MASK) in vga_is_boot_device()
[all …]
/linux-6.6.21/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 …]
Dpi-futex.rst93 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-6.6.21/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-6.6.21/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-6.6.21/arch/arm/kernel/
Diwmmxt.S102 str r0, [r3] @ this task now owns Concan regs
276 1: @ this task owns Concan regs -- grab a copy from there
343 teq r2, r3 @ next task owns it?
/linux-6.6.21/Documentation/devicetree/bindings/soc/aspeed/
Duart-routing.yaml24 which owns the system configuration policy, to configure how UARTs and
/linux-6.6.21/Documentation/devicetree/bindings/i2c/
Dnvidia,tegra186-bpmp-i2c.yaml15 owns certain HW devices, such as the I2C controller for the power
/linux-6.6.21/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-6.6.21/Documentation/filesystems/
Dhfsplus.rst22 Specifies the user/group that owns all files on the filesystem
Dhfs.rst29 Specifies the user/group that owns all files on the filesystems.
/linux-6.6.21/Documentation/devicetree/bindings/soc/qcom/
Dqcom,rpm-master-stats.yaml42 The name of the RPM Master which owns the MSG RAM slice where this
/linux-6.6.21/Documentation/devicetree/bindings/mailbox/
Dxlnx,zynqmp-ipi-mailbox.yaml12 agent owns registers used for notification and buffers for message.
/linux-6.6.21/Documentation/i2c/busses/
Di2c-sis96x.rst47 chipsets as well: 635, and 635T. If anyone owns a board with those chips
/linux-6.6.21/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-6.6.21/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-6.6.21/Documentation/devicetree/bindings/bus/
Dfsl,imx8qxp-pixel-link-msi-bus.yaml28 The i.MX System Controller Firmware (SCFW) owns and uses the i.MX8qm/qxp
/linux-6.6.21/Documentation/ABI/testing/
Dsysfs-bus-i3c12 Expose the master that owns the bus (<bus-id>-<master-pid>) at
Dsysfs-bus-rapidio98 device that that owns this attribute
/linux-6.6.21/Documentation/devicetree/bindings/mmc/
Dmarvell,xenon-sdhci.yaml14 Each SDHC is independent and owns independent resources, such as register
/linux-6.6.21/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-6.6.21/Documentation/accel/qaic/
Dqaic.rst131 may contain sensitive information therefore only the client that owns the
/linux-6.6.21/fs/reiserfs/
DREADME85 funding for the first 5.5 years, and one of the programmers. He owns
/linux-6.6.21/Documentation/bpf/
Dringbuf.rst164 Each time a record is reserved, producer that "owns" the record will

12