| /kernel/linux/linux-5.10/arch/x86/include/asm/ |
| D | bitops.h | 289 * AMD64 says BSFL won't clobber the dest reg if x==0; Intel64 says the in ffs()
290 * dest reg is undefined if x==0, but their CPU architect says its in ffs()
330 * AMD64 says BSRL won't clobber the dest reg if x==0; Intel64 says the in fls()
331 * dest reg is undefined if x==0, but their CPU architect says its in fls()
370 * AMD64 says BSRQ won't clobber the dest reg if x==0; Intel64 says the in fls64()
371 * dest reg is undefined if x==0, but their CPU architect says its in fls64()
|
| D | mmu.h | 47 * One bit per protection key says whether userspace can
|
| /kernel/linux/linux-5.10/drivers/pcmcia/ |
| D | soc_common.h | 181 * The PC Card Standard, Release 7, section 4.13.4, says that twIORD
182 * has a minimum value of 165ns. Section 4.13.5 says that twIOWR has
184 * common and attribute memory write timing) says that twWE has a
187 * operation, also section 4.7.4). Section 4.7.3 says that taOE
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | kernel-docs.rst | 168 :Description: The title says it all.
177 :Description: The title says it all.
202 :Description: The title says it all.
210 :Description: The title says it all.
218 :Description: The title says it all.
226 :Description: The title says it all.
234 :Description: The title still says it all.
242 :Description: The title says it all.
566 :Description: The title says it all. There's a fixed kernel section
|
| /kernel/linux/linux-5.10/Documentation/fb/ |
| D | tridentfb.rst | 55 look at the driver output to see what it says when initializing.
59 detection says in all three BIOS selectable situations 2M, 4M, 8M.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/timer/ |
| D | arm,arch_timer.yaml | 62 description: Indicates the presence of QorIQ erratum A-008585, which says
70 says that reading the counters is unreliable in some cases, and reads may
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/nouveau/nvkm/subdev/mxm/ |
| D | nv50.c | 127 /* override dcb sorconf.link, based on what mxm data says */ in mxm_dcb_sanitise_entry()
140 * the descriptor says the connector type should be. in mxm_dcb_sanitise_entry()
143 * and the mxm data says the connector is really HDMI. another in mxm_dcb_sanitise_entry()
|
| /kernel/linux/linux-5.10/arch/x86/math-emu/ |
| D | reg_mul.c | 84 /* The 80486 book says that the answer is +0, but a real in FPU_mul()
86 IEEE-754 apparently says it should be this way. */ in FPU_mul()
|
| /kernel/linux/linux-5.10/arch/ia64/include/asm/ |
| D | shmparam.h | 7 * get attached. The IA-64 architecture says that there may be a
|
| /kernel/linux/linux-5.10/arch/x86/tools/ |
| D | insn_decoder_test.c | 159 pr_warn("objdump says %d bytes, but insn_get_length() " in main()
160 "says %d\n", nb, insn.length); in main()
|
| /kernel/linux/linux-5.10/drivers/mtd/maps/ |
| D | physmap-versatile.c | 73 /* The manual says bit 2, the code says bit 3, trust the code */
|
| D | physmap-gemini.c | 164 dev_warn(dev, "flash hardware say flash is 16 bit wide but DT says it is %d bits wide\n", in of_flash_probe_gemini()
168 dev_warn(dev, "flash hardware say flash is 8 bit wide but DT says it is %d bits wide\n", in of_flash_probe_gemini()
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/rtc/ |
| D | faraday,ftrtc010.txt | 14 says the clock should be 1 Hz, but implementers actually seem
|
| /kernel/linux/linux-5.10/arch/alpha/include/uapi/asm/ |
| D | resource.h | 15 * SuS says limits have to be unsigned. Fine, it's unsigned, but
|
| /kernel/linux/linux-5.10/Documentation/litmus-tests/rcu/ |
| D | RCU+sync+read.litmus | 10 * This is one implication of the RCU grace-period guarantee, which says (among
|
| D | RCU+sync+free.litmus | 14 * This is one implication of the RCU grace-period guarantee, which says (among
|
| /kernel/linux/linux-5.10/arch/sparc/include/uapi/asm/ |
| D | resource.h | 22 * SuS says limits have to be unsigned.
|
| /kernel/linux/linux-5.10/arch/arm/vdso/ |
| D | vdsomunge.c | 10 * 0042E) says:
18 * And ELF for the ARM Architecture (ARM IHI 0044E) (Table 4-2) says:
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/i915/display/ |
| D | intel_bios.h | 66 MIPI_SEQ_DEASSERT_RESET, /* Spec says MipiAssertResetPin */
70 MIPI_SEQ_ASSERT_RESET, /* Spec says MipiDeassertResetPin */
|
| /kernel/linux/linux-5.10/drivers/staging/greybus/Documentation/firmware/ |
| D | firmware.c | 78 printf("Load status says loading failed: %d\n", in update_intf_firmware()
150 printf("Load status says loading failed: %d\n", in update_backend_firmware()
|
| /kernel/linux/linux-5.10/arch/mips/include/uapi/asm/ |
| D | resource.h | 25 * SuS says limits have to be unsigned.
|
| /kernel/linux/linux-5.10/drivers/hid/ |
| D | hid-macally.c | 18 * The Macally ikey keyboard says that its logical and usage maximums are both
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/leds/backlight/ |
| D | common.yaml | 31 on the brightness apart from what the driver says, as it could happen
|
| /kernel/linux/linux-5.10/tools/lib/subcmd/ |
| D | parse-options.h | 83 * PARSE_OPT_OPTARG: says that the argument is optional (not for BOOLEANs)
84 * PARSE_OPT_NOARG: says that this option takes no argument, for CALLBACKs
85 * PARSE_OPT_NONEG: says that this option cannot be negated
|
| /kernel/linux/linux-5.10/include/linux/reset/ |
| D | reset-simple.h | 25 * are set to assert the reset. Note that this says nothing about
|