Home
last modified time | relevance | path

Searched full:appears (Results 1 – 25 of 663) sorted by relevance

12345678910>>...27

/linux-5.10/Documentation/sound/hd-audio/
Dcontrols.rst13 appears only when the surround channels are available.
22 appears.
40 appears only when "loopback" is set to true in a codec hint
113 appears only when the surround channels are available.
/linux-5.10/arch/arm/include/asm/
Dtlb.h7 * Experimentation shows that on a StrongARM, it appears to be faster
11 * This appears true for both the process fork+exit case, as well as
/linux-5.10/Documentation/ABI/testing/
Dsysfs-uevent24 listeners. The UUID value appears in uevent as
34 delimited by a space character ' '. Each pair appears in
Dsysfs-bus-counter155 respective channel as it appears in the device datasheet.
202 appears in its respective datasheet.
230 respective signal as it appears in the device datasheet.
Dsysfs-bus-pci150 This symbolic link appears when hardware supports the SR-IOV
159 This symbolic link appears when hardware supports the SR-IOV
169 This symbolic link appears when a device is a Virtual Function.
240 This file appears when a physical PCIe device supports SR-IOV.
253 This file appears when a physical PCIe device supports SR-IOV.
/linux-5.10/drivers/mtd/nand/raw/gpmi-nand/
Dgpmi-nand.h40 * the ECC status appears.
42 * which the underlying physical block mark appears.
44 * which the underlying physical block mark appears.
/linux-5.10/arch/m68k/include/asm/
Dmac_psc.h168 * Appears to be a read-only status register.
178 * value. The value appears to be the
202 * Appears to e a read-only status register.
/linux-5.10/Documentation/sound/designs/
Dprocfile.rst36 Appears only when ``CONFIG_SND_DEBUG=y``.
79 oss_mixer file appears here, too. This shows the current mapping of
93 This file appears when ``CONFIG_SND_DEBUG=y`` and
/linux-5.10/drivers/leds/
Dleds-ipaq-micro.c29 * Byte 1 = duration (flags?) appears to be ignored in micro_leds_brightness_set()
66 * Byte 1 = duration (flags?) appears to be ignored in micro_leds_blink_set()
/linux-5.10/arch/x86/math-emu/
Dpoly_l2.c96 set_precision_flag_up(); /* 80486 appears to always do this */ in poly_l2()
133 set_precision_flag_up(); /* 80486 appears to always do this */ in poly_l2p1()
147 /* 80486 appears to do this */ in poly_l2p1()
/linux-5.10/include/asm-generic/
Dcache.h5 * 32 bytes appears to be the most common cache line size,
/linux-5.10/drivers/gpu/drm/i915/gt/
Dselftest_gt_pm.c93 * XXX CS_TIMESTAMP appears gibberish in live_gt_clocks()
95 * Ville's experiments indicate that it mostly appears 'stuck' in live_gt_clocks()
/linux-5.10/scripts/dummy-tools/
Dnm6 # Check if the first parameter appears in the rest. Succeeds if found.
Dobjcopy6 # Check if the first parameter appears in the rest. Succeeds if found.
Dld6 # Check if the first parameter appears in the rest. Succeeds if found.
/linux-5.10/Documentation/devicetree/bindings/rtc/
Dfaraday,ftrtc010.txt3 This RTC appears in for example the Storlink Gemini family of
/linux-5.10/drivers/media/usb/pvrusb2/
Dpvrusb2-debugifc.h19 driver. This should work even if the driver appears to be
/linux-5.10/arch/mips/vdso/
DKconfig10 # GCC (at least up to version 9.2) appears to emit function calls that make use
/linux-5.10/Documentation/ABI/obsolete/
Dsysfs-selinux-disable18 Thankfully, the need for the SELinux runtime disable appears to be
/linux-5.10/Documentation/admin-guide/
Dthunderbolt.rst87 (e.g the PCIe device appears).
196 Thunderbolt device so that the host controller appears. It does not
217 After a while the host controller appears again and this time it should
/linux-5.10/arch/sh/lib/
Ddelay.c15 * ST40-300 appears to have an issue with this code, in __delay()
/linux-5.10/fs/quota/
Dquotaio_v1.h18 * (as it appears on disk) - the file is an array of these structures
/linux-5.10/drivers/net/wireless/intel/iwlwifi/fw/api/
Dcmdhdr.h117 * This header format appears in the beginning of each command sent from the
158 * This header format appears in the beginning of each command sent from the
/linux-5.10/include/linux/
Dcounter.h51 * as it appears in the datasheet documentation
180 * the name as it appears in the datasheet documentation
417 * @name: name of the device as it appears in the datasheet
/linux-5.10/Documentation/filesystems/ext4/
Djournal.rst405 - This field appears to be open coded. It always comes at the end of the
411 - A UUID to go with this tag. This field appears to be copied from the
476 - This field appears to be open coded. It always comes at the end of the
482 - A UUID to go with this tag. This field appears to be copied from the

12345678910>>...27