Searched refs:variants (Results 1 – 25 of 162) sorted by relevance
1234567
| /Linux-v5.10/scripts/atomic/ |
| D | atomics.tbl | 3 # Where meta contains a string of variants to generate.
4 # Upper-case implies _{acquire,release,relaxed} variants.
9 # * R - return: returns base type (has _return variants)
10 # * F/f - fetch: returns base type (has fetch_ variants)
|
| /Linux-v5.10/arch/xtensa/ |
| D | Makefile | 64 vardirs := $(patsubst %,arch/xtensa/variants/%/,$(variant-y))
73 …ldvar := $(shell test -e $(srctree)/arch/xtensa/variants/$(VARIANT)/Makefile && echo arch/xtensa/v…
|
| /Linux-v5.10/Documentation/devicetree/bindings/interrupt-controller/ |
| D | opencores,or1k-pic.txt | 5 - compatible : should be "opencores,or1k-pic-level" for variants with
6 level triggered interrupt lines, "opencores,or1k-pic-edge" for variants with
|
| D | cdns,xtensa-pic.txt | 12 core variants it may be mapped to different internal IRQ.
|
| /Linux-v5.10/Documentation/scheduler/ |
| D | completion.rst | 39 - the waiting part through a call to one of the variants of wait_for_completion(),
79 variants of wait_for_completion(), as it must be assured that memory de-allocation
125 To emphasise this again: in particular when using some of the waiting API variants
127 _killable() and _interruptible()) variants, the wait might complete
174 uninterruptible. wait_for_completion() and its variants are only safe
180 As all variants of wait_for_completion() can (obviously) block for a long
185 wait_for_completion*() variants available:
188 The below variants all return status and this status should be checked in
228 Further variants include _killable which uses TASK_KILLABLE as the
235 The _io variants wait_for_completion_io() behave the same as the non-_io
[all …]
|
| /Linux-v5.10/Documentation/fb/ |
| D | s3fb.rst | 10 S3 Trio64 (and variants V+, UV+, V2/DX, V2/GX)
11 S3 Virge (and variants VX, DX, GX and GX2+)
26 * 4 bpp pseudocolor modes (with 18bit palette, two variants)
|
| /Linux-v5.10/arch/arm/mach-bcm/ |
| D | Kconfig | 36 which includes the following variants:
46 which includes the following variants:
113 variants.
121 BCM21663 and BCM21664 variants.
|
| /Linux-v5.10/Documentation/hwmon/ |
| D | intel-m10-bmc-hwmon.rst | 28 reprogramed to some variants in order to support different Intel
30 variants, but now it only supports the BMC for Intel PAC N3000.
|
| /Linux-v5.10/Documentation/devicetree/bindings/usb/ |
| D | brcm,bcm3384-usb.txt | 11 - Figuring out which controllers are disabled on ASIC bondout variants
|
| D | ehci-orion.txt | 1 * EHCI controller, Orion Marvell variants
|
| /Linux-v5.10/drivers/gpu/drm/arm/display/ |
| D | Kconfig | 12 Processor driver. It supports the D71 variants of the hardware.
|
| /Linux-v5.10/drivers/gpu/drm/mgag200/ |
| D | Kconfig | 9 MGA G200 desktop chips and the server variants. It requires 0.3.0
|
| /Linux-v5.10/drivers/net/can/spi/mcp251xfd/ |
| D | Kconfig | 16 variants. This comes with a runtime overhead.
|
| /Linux-v5.10/Documentation/core-api/ |
| D | timekeeping.rst | 12 The recommended simplest form returns an opaque ktime_t, with variants
62 For all of the above, there are variants that return the time in a
100 Some additional variants exist for more specialized cases:
137 These variants are safe to call from any context, including from
|
| /Linux-v5.10/Documentation/x86/ |
| D | mds.rst | 10 on internal buffers in Intel CPUs. The variants are:
73 All variants have the same mitigation strategy at least for the single CPU
166 and not by any other MDS variant. The other MDS variants cannot be
168 the Load Ports are shared. So on CPUs affected by other variants, the
187 The mitigation is hooked into all variants of halt()/mwait(), but does
|
| /Linux-v5.10/Documentation/admin-guide/hw-vuln/ |
| D | mds.rst | 26 Not all processors are affected by all variants of MDS, but the mitigation
161 other variants cannot be protected against cross Hyper-Thread attacks.
219 cross Hyper-Threads when entering idle states. Some XEON PHI variants allow
224 XEON PHI is not affected by the other MDS variants and MSBDS is mitigated
233 All MDS variants except MSBDS can be attacked cross Hyper-Threads. That
|
| /Linux-v5.10/Documentation/ |
| D | asm-annotations.rst | 106 architecture specific ``__ALIGN`` bytes. There are also ``_NOALIGN`` variants
144 one. ``_NOALIGN`` variants exist too. The use is the same as for the ``FUNC``
189 * ``SYM_DATA`` and ``SYM_DATA_LOCAL`` are variants for simple, mostly one-line
206 symbol marked by them. They are used either in ``_LABEL`` variants of the
|
| /Linux-v5.10/arch/arm/boot/dts/ |
| D | kirkwood-db.dtsi | 9 * and 6282 variants of the Marvell Kirkwood Development Board.
|
| D | kirkwood-rd88f6192.dts | 8 * variants of the Marvell Kirkwood Development Board.
|
| D | kirkwood-rd88f6281.dtsi | 8 * variants of the Marvell Kirkwood Development Board.
|
| /Linux-v5.10/Documentation/devicetree/bindings/ |
| D | property-units.txt | 7 prefixes is due to selecting the most commonly used variants.
|
| /Linux-v5.10/Documentation/i2c/ |
| D | slave-eeprom-backend.rst | 13 variants are also supported. The name needed for instantiating has the form
|
| /Linux-v5.10/drivers/gpu/drm/arm/ |
| D | Kconfig | 35 Processor driver. It supports the DP500, DP550 and DP650 variants
|
| /Linux-v5.10/Documentation/devicetree/bindings/pinctrl/ |
| D | marvell,armada-xp-pinctrl.txt | 11 This driver supports all Armada XP variants, i.e. mv78230, mv78260, and mv78460.
17 * Marvell Armada XP (all variants)
|
| /Linux-v5.10/drivers/clk/samsung/ |
| D | Kconfig | 19 on some Exynos SoC variants. Choose M or Y here if you want to
|
1234567
