| /linux-6.12.1/arch/x86/include/asm/ |
| D | bitops.h | 313 * AMD64 says BSFL won't clobber the dest reg if x==0; Intel64 says the in variable_ffs()
314 * dest reg is undefined if x==0, but their CPU architect says its in variable_ffs()
370 * AMD64 says BSRL won't clobber the dest reg if x==0; Intel64 says the in fls()
371 * dest reg is undefined if x==0, but their CPU architect says its in fls()
413 * AMD64 says BSRQ won't clobber the dest reg if x==0; Intel64 says the in fls64()
414 * dest reg is undefined if x==0, but their CPU architect says its in fls64()
|
| /linux-6.12.1/drivers/pcmcia/ |
| D | soc_common.h | 63 * The PC Card Standard, Release 7, section 4.13.4, says that twIORD
64 * has a minimum value of 165ns. Section 4.13.5 says that twIOWR has
66 * common and attribute memory write timing) says that twWE has a
69 * operation, also section 4.7.4). Section 4.7.3 says that taOE
|
| /linux-6.12.1/drivers/clk/mstar/ |
| D | clk-msc313-cpupll.c | 21 * 0x150 -- vendor code says "toggle lpf enable"
24 * 0x160 -- vendor code says "switch to LPF". Clock source config? Register bank?
25 * 0x164 -- vendor code says "from low to high" which seems to mean transition from LPF low to
|
| /linux-6.12.1/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.
|
| /linux-6.12.1/Documentation/devicetree/bindings/timer/ |
| D | arm,arch_timer.yaml | 79 description: Indicates the presence of QorIQ erratum A-008585, which says
87 says that reading the counters is unreliable in some cases, and reads may
|
| /linux-6.12.1/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()
|
| /linux-6.12.1/drivers/pwm/ |
| D | pwm-dwc-core.c | 64 * Specification says timer usage flow is to disable timer, then in __dwc_pwm_configure_timer()
65 * program it followed by enable. It also says Load Count is loaded in __dwc_pwm_configure_timer()
|
| /linux-6.12.1/drivers/net/can/spi/mcp251xfd/ |
| D | mcp251xfd-ram.c | 111 /* The ethtool doc says: in can_ram_get_layout()
134 /* The ethtool doc says: in can_ram_get_layout()
|
| /linux-6.12.1/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()
|
| /linux-6.12.1/drivers/mtd/maps/ |
| 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()
|
| D | physmap-versatile.c | 73 /* The manual says bit 2, the code says bit 3, trust the code */
|
| /linux-6.12.1/arch/x86/tools/ |
| D | insn_decoder_test.c | 161 pr_warn("objdump says %d bytes, but insn_get_length() " in main()
162 "says %d\n", nb, insn.length); in main()
|
| /linux-6.12.1/arch/alpha/include/uapi/asm/ |
| D | resource.h | 15 * SuS says limits have to be unsigned. Fine, it's unsigned, but
|
| /linux-6.12.1/arch/arm/vdso/ |
| D | vdsomunge.c | 10 * 0042E) says:
18 * And ELF for the ARM Architecture (ARM IHI 0044E) (Table 4-2) says:
|
| /linux-6.12.1/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()
|
| /linux-6.12.1/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
|
| /linux-6.12.1/arch/sparc/include/uapi/asm/ |
| D | resource.h | 22 * SuS says limits have to be unsigned.
|
| /linux-6.12.1/drivers/tty/serial/jsm/ |
| D | jsm_neo.c | 50 /* Why? Becuz Exar's spec says we have to zero it out before setting it */ in neo_set_cts_flow_control()
82 /* Why? Becuz Exar's spec says we have to zero it out before setting it */ in neo_set_rts_flow_control()
121 /* Why? Becuz Exar's spec says we have to zero it out before setting it */ in neo_set_ixon_flow_control()
159 /* Why? Becuz Exar's spec says we have to zero it out before setting it */ in neo_set_ixoff_flow_control()
200 /* Why? Becuz Exar's spec says we have to zero it out before setting it */ in neo_set_no_input_flow_control()
238 /* Why? Becuz Exar's spec says we have to zero it out before setting it */ in neo_set_no_output_flow_control()
857 * should encapsulate all 3... At least, thats what Exar says. in neo_parse_lsr()
881 * Rx Oruns. Exar says that an orun will NOT corrupt in neo_parse_lsr()
|
| /linux-6.12.1/tools/lib/subcmd/ |
| D | parse-options.h | 79 * PARSE_OPT_OPTARG: says that the argument is optional (not for BOOLEANs)
80 * PARSE_OPT_NOARG: says that this option takes no argument, for CALLBACKs
81 * PARSE_OPT_NONEG: says that this option cannot be negated
|
| /linux-6.12.1/drivers/gpu/drm/i915/display/ |
| D | intel_bios.h | 70 MIPI_SEQ_DEASSERT_RESET, /* Spec says MipiAssertResetPin */
74 MIPI_SEQ_ASSERT_RESET, /* Spec says MipiDeassertResetPin */
|
| /linux-6.12.1/arch/mips/include/uapi/asm/ |
| D | resource.h | 25 * SuS says limits have to be unsigned.
|
| /linux-6.12.1/drivers/hid/ |
| D | hid-macally.c | 18 * The Macally ikey keyboard says that its logical and usage maximums are both
|
| /linux-6.12.1/arch/powerpc/include/asm/ |
| D | papr-sysparm.h | 15 * Parameters Option. Where the spec says "characteristics", we use
|
| /linux-6.12.1/Documentation/devicetree/bindings/rtc/ |
| D | faraday,ftrtc010.yaml | 35 - description: EXTCLK clocks. Faraday calls it CLK1HZ and says the clock
|