| /linux/scripts/atomic/ |
| H A 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/Documentation/devicetree/bindings/interrupt-controller/ |
| H A 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
|
| H A D | cdns,xtensa-pic.txt | 12 core variants it may be mapped to different internal IRQ.
|
| /linux/Documentation/scheduler/ |
| H A 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/Documentation/fb/ |
| H A 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/arch/arm/mach-pxa/ |
| H A D | Kconfig | 124 Select code specific to PXA21x/25x/26x variants
130 Select code specific to PXA27x variants
136 Select code specific to PXA3xx variants
|
| /linux/arch/arm64/boot/dts/freescale/ |
| H A D | fsl-ls1043a-rdb.dts | 109 * variants below.
123 * variants below.
137 * variants below.
|
| /linux/Documentation/driver-api/ |
| H A D | vfio-pci-device-specific-driver-acceptance.rst | 3 Acceptance criteria for vfio-pci device specific driver variants
19 variants may interact with parent devices (ex. SR-IOV PF in support of
|
| /linux/drivers/soc/renesas/ |
| H A D | Kconfig | 320 This enables support for the Renesas RZ/G2UL SoC variants.
326 This enables support for the Renesas RZ/G2L SoC variants.
332 This enables support for the Renesas RZ/V2L SoC variants.
338 This enables support for the Renesas RZ/G3S SoC variants.
351 This enables support for the Renesas RZ/V2H(P) SoC variants.
|
| /linux/Documentation/hwmon/ |
| H A 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/Documentation/core-api/ |
| H A 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:
138 These variants are safe to call from any context, including from
|
| H A D | asm-annotations.rst | 112 architecture specific ``__ALIGN`` bytes. There are also ``_NOALIGN`` variants
149 one. ``_NOALIGN`` variants exist too. The use is the same as for the ``FUNC``
194 * ``SYM_DATA`` and ``SYM_DATA_LOCAL`` are variants for simple, mostly one-line
211 symbol marked by them. They are used either in ``_LABEL`` variants of the
|
| /linux/arch/arm/mach-bcm/ |
| H A D | Kconfig | 36 which includes the following variants:
46 which includes the following variants:
110 variants.
118 BCM21663 and BCM21664 variants.
|
| /linux/drivers/gpu/drm/arm/display/ |
| H A D | Kconfig | 11 Processor driver. It supports the D71 variants of the hardware.
|
| /linux/drivers/net/can/spi/mcp251xfd/ |
| H A D | Kconfig | 18 variants. This comes with a runtime overhead.
|
| /linux/arch/arm64/boot/dts/ti/ |
| H A D | k3-am65-iot2050-usb3.dtsi | 8 * Common bits for IOT2050 variants with USB3 support
|
| H A D | k3-am65-iot2050-common-pg2.dtsi | 9 * Common bits of the IOT2050 Basic and Advanced variants, PG2
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| H A D | mds.rst | 26 Not all processors are affected by all variants of MDS, but the mitigation
153 other variants cannot be protected against cross Hyper-Thread attacks.
211 cross Hyper-Threads when entering idle states. Some XEON PHI variants allow
216 XEON PHI is not affected by the other MDS variants and MSBDS is mitigated
225 All MDS variants except MSBDS can be attacked cross Hyper-Threads. That
|
| /linux/Documentation/arch/x86/ |
| H A 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
182 and not by any other MDS variant. The other MDS variants cannot be
184 the Load Ports are shared. So on CPUs affected by other variants, the
203 The mitigation is hooked into all variants of halt()/mwait(), but does
|
| /linux/drivers/gpu/drm/mgag200/ |
| H A D | Kconfig | 11 MGA G200 desktop chips and the server variants. It requires 0.3.0
|
| /linux/drivers/clk/samsung/ |
| H A D | Kconfig | 85 on some Samsung Exynos SoC variants. Choose M or Y here if you want
94 Exynos SoC variants. Usually the XCLKOUT is used to monitor the
|
| /linux/arch/xtensa/ |
| H A D | Makefile | 55 vardirs := $(patsubst %,arch/xtensa/variants/%/,$(variant-y))
|
| /linux/arch/arm/boot/dts/marvell/ |
| H A D | kirkwood-db.dtsi | 9 * and 6282 variants of the Marvell Kirkwood Development Board.
|
| /linux/arch/arm64/boot/dts/qcom/ |
| H A D | msm8916-samsung-e7.dts | 9 * variants.
|
| /linux/Documentation/i2c/ |
| H A D | slave-eeprom-backend.rst | 13 variants are also supported. The name needed for instantiating has the form
|