Searched full:explicitly (Results 1 – 25 of 366) sorted by relevance
12345678910>>...15
| /Documentation/hwmon/ |
| D | lm92.rst | 18 Addresses scanned: none, must be instantiated explicitly
26 Addresses scanned: none, must be instantiated explicitly
48 instantiated explicitly.
|
| D | adm1177.rst | 23 devices explicitly. Please see Documentation/i2c/instantiating-devices.rst
|
| D | ltc4215.rst | 31 instantiate the devices explicitly.
|
| D | ir36021.rst | 29 devices explicitly.
|
| D | ltc4151.rst | 30 the devices explicitly.
|
| D | menf21bmc.rst | 30 You will have to instantiate the MFD driver explicitly.
|
| D | adc128d818.rst | 49 the driver explicitly if the chip is configured for any of those addresses in
|
| D | q54sj108a2.rst | 35 devices explicitly. Please see Documentation/i2c/instantiating-devices.rst for
|
| /Documentation/ABI/stable/ |
| D | sysfs-firmware-opal-elog | 9 exist until explicitly acknowledged to firmware.
18 but not explicitly acknowledged them to firmware and
|
| /Documentation/i2c/ |
| D | instantiating-devices.rst | 8 reason, the kernel code must instantiate I2C devices explicitly. There are
107 Method 2: Instantiate the devices explicitly
115 you can instantiate your I2C devices explicitly. This is done by filling
191 explicitly. Instead, i2c-core will probe for such devices as soon as their
218 * I2C buses must now explicitly say which I2C driver classes can probe
|
| /Documentation/driver-api/ |
| D | zorro.rst | 79 explicitly using z_ioremap().
87 - Zorro III address space must be mapped explicitly using z_ioremap() first
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | ti,ina3221.yaml | 45 default to enabled in the chip. Unless channels are explicitly disabled
105 * to disable, must be explicitly disabled in device-tree.
|
| /Documentation/admin-guide/ |
| D | edid.rst | 7 In the good old days when graphics parameters were configured explicitly
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | ti,omap4-wugen-mpu | 21 are explicitly forbidden.
|
| D | nvidia,tegra20-ictlr.txt | 28 are explicitly forbidden.
|
| /Documentation/w1/masters/ |
| D | ds2482.rst | 34 detection is done. You should instantiate the device explicitly.
|
| /Documentation/ABI/removed/ |
| D | sysfs-selinux-checkreqprot | 19 explicitly writing a "0" to /sys/fs/selinux/checkreqprot during
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-bd9571mwv-regulator | 26 DDR Backup Mode must be explicitly enabled by the user,
|
| D | sysfs-devices-platform-ACPI-TAD | 39 is explicitly cleared via the ac_status attribute.
82 (and from S4/S5 too if supported) until its status is explicitly
|
| D | sysfs-driver-hid-picolcd | 42 to flush its tiny changes explicitly at higher than default rate.
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-decoder-cmd.rst | 148 *not* resume the decoder. You have to explicitly call
159 without the ``V4L2_DEC_CMD_STOP`` being called explicitly. See
198 So this command can be used to explicitly flush that final decoded
|
| /Documentation/virt/hyperv/ |
| D | coco.rst | 105 guest Linux does normal memory initialization, except for explicitly marking
120 Throughout the Linux kernel, explicitly testing these flags has mostly been
216 mode goes through send and receive buffer space that is explicitly allocated
219 the netvsc driver explicitly copies packets to/from these buffers, the
231 with arguments explicitly describing the access. See
|
| /Documentation/spi/ |
| D | spi-sc18is602.rst | 22 support Chip ID registers. You will have to instantiate the devices explicitly.
|
| /Documentation/virt/kvm/ |
| D | review-checklist.rst | 18 5. New features must default to off (userspace should explicitly request them).
|
| /Documentation/devicetree/bindings/clock/ |
| D | maxim,max9485.txt | 25 If not explicitly set, the output names are "mclkout", "clkout", "clkout1"
|
12345678910>>...15