Searched full:possibly (Results 1 – 25 of 187) sorted by relevance
12345678
| /Documentation/driver-api/80211/ |
| D | introduction.rst | 16 published by the IEEE in 802.11-2007 (or possibly later versions).
|
| /Documentation/devicetree/bindings/reset/ |
| D | brcm,brcmstb-reset.yaml | 11 SET/CLEAR/STATUS registers and possibly multiple banks, each of 32 bit
|
| /Documentation/sound/hd-audio/ |
| D | realtek-pc-beep.rst | 30 jack (or possibly Line In on some machines) input instead. If PC Beep is
42 When zero, mix 1Ah (possibly with amplification, depending on L and R bits)
47 When one, mix 1Ah (possibly with amplification, depending on L and R bits)
|
| /Documentation/devicetree/bindings/soc/fsl/cpm_qe/ |
| D | fsl,qe-firmware.yaml | 24 The fsl,firmware property can be specified in the DTS (possibly using incbin)
|
| /Documentation/ABI/testing/ |
| D | pstore | 39 data saved on each oops/panic. Pstore saves (possibly
|
| /Documentation/devicetree/bindings/serio/ |
| D | ps2-gpio.yaml | 40 Indicates whether write function is provided to serio device. Possibly
|
| /Documentation/mm/ |
| D | balance.rst | 41 zone size (and possibly of the size of lower class zones), we can decide
45 due to ignoring possibly lower usage in the lower class zones. Also,
|
| D | ksm.rst | 70 the ksmd CPU usage and possibly slowdown the readonly computations on
|
| /Documentation/userspace-api/media/v4l/ |
| D | dev-radio.rst | 44 :ref:`control`) such as a volume control, possibly custom controls.
|
| D | metafmt-uvc.rst | 51 - The rest of the header, possibly including UVC PTS and SCR fields
|
| D | vidioc-g-ctrl.rst | 92 The control is temporarily not changeable, possibly because another
|
| /Documentation/devicetree/bindings/iio/proximity/ |
| D | ams,as3935.yaml | 43 need to set according to the noise from the MCU board, and possibly
|
| /Documentation/devicetree/bindings/rtc/ |
| D | isil,isl12057.txt | 4 consisting of a compatible field, an address and possibly an interrupt
|
| D | trivial-rtc.yaml | 15 possibly an interrupt line.
|
| /Documentation/filesystems/nfs/ |
| D | exporting.rst | 131 create a dentry for it (possibly with d_obtain_alias).
135 implied object and create a dentry for it (possibly with
140 the parent. Quite possibly the parent dentry will have been allocated
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | gpio-charger.yaml | 14 autonomously, only providing some status GPIOs and possibly some
|
| /Documentation/admin-guide/ |
| D | init.rst | 18 3) **Broken console device**: Possibly a conflict in ``console= setup``
|
| /Documentation/i2c/ |
| D | i2c-topology.rst | 84 of the entire operation. But accesses to D3 are possibly interleaved
233 are locked). But accesses to D3 and D4 are possibly interleaved at
236 Accesses to D3 locks out D1 and D2, but accesses to D4 are still possibly
256 root adapter). But accesses to D4 are possibly interleaved at any
290 are locked). Accesses to D3 and D4 are possibly interleaved at
|
| /Documentation/driver-api/ |
| D | xillybus.rst | 70 a quicker and possibly less elegant solution is sought: The driver is
125 possibly pressing CTRL-C as some stage, even though the xillybus_* pipes have
259 Each of the (possibly bidirectional) pipes presented to the user is allocated
364 (except possibly for the last) are 100% utilized this way.
|
| /Documentation/admin-guide/media/ |
| D | omap3isp.rst | 63 All the blocks in the ISP, excluding the CSI-2 and possibly the CCP2 receiver,
|
| /Documentation/admin-guide/hw-vuln/ |
| D | multihit.rst | 5 error, possibly resulting in an unrecoverable CPU lockup, when an
98 IA32_ARCH_CAPABILITIES MSR Not present Possibly vulnerable,check model
|
| /Documentation/watchdog/ |
| D | hpwdt.rst | 55 non-zero values will be rounded, possibly to zero. Users should verify
|
| /Documentation/networking/ |
| D | msg_zerocopy.rst | 30 return without possibly modifying the data in flight. Kernel integrity
31 is not affected, but a buggy program can possibly corrupt its own data
|
| /Documentation/timers/ |
| D | timers-howto.rst | 104 * Use msleep or possibly msleep_interruptible
|
| /Documentation/filesystems/ |
| D | romfs.rst | 40 drivers (and possibly the SCSI drivers), and the ISO 9660 filesystem
178 boundary, it is currently possibly suboptimal to read or execute files
|
12345678