Home
last modified time | relevance | path

Searched full:correctly (Results 1 – 25 of 284) sorted by relevance

12345678910>>...12

/Documentation/admin-guide/device-mapper/
Ddm-flakey.rst44 Write I/O is handled correctly.
48 Read I/O is handled correctly.
52 Read I/O is handled correctly.
/Documentation/devicetree/bindings/serial/
Darc-uart.txt20 Note: Each port should have an alias correctly numbered in "aliases" node.
Ddigicolor-usart.txt14 Note: Each UART port should have an alias correctly numbered
Dcirrus,clps711x-uart.txt14 Note: Each UART port should have an alias correctly numbered
/Documentation/devicetree/bindings/gpio/
Dgpio-clps711x.txt14 Note: Each GPIO port should have an alias correctly numbered in "aliases"
/Documentation/devicetree/bindings/timer/
Dcirrus,clps711x-timer.txt9 Note: Each timer should have an alias correctly numbered in "aliases" node.
/Documentation/admin-guide/
Dedid.rst11 either correctly working because all components follow the standards -
/Documentation/dev-tools/kunit/
Drun_manual.rst99 For test authors, to use this feature, tests will need to correctly initialise
100 and/or clean up any data, so the test runs correctly a second time.
/Documentation/devicetree/bindings/net/
Dti,dp83822.yaml45 correctly or not set at all then this boolean can be used to enable it.
92 If the strap pin is not set correctly or not set at all, then this can be
Dmdio-gpio.yaml36 # Note: Each gpio-mdio bus should have an alias correctly numbered in "aliases"
/Documentation/litmus-tests/locking/
DDCL-broken.litmus7 * correctly implement double-checked locking.
/Documentation/devicetree/bindings/phy/
Dbcm-ns-usb2-phy.yaml10 To initialize USB 2.0 PHY driver needs to setup PLL correctly.
/Documentation/filesystems/iomap/
Dporting.rst102 they should largely be debugged and working correctly after this step.
106 The mapping functions should all work correctly, so all that needs to be
/Documentation/i2c/
Dfault-codes.rst22 to respond correctly. Other code may need to rely on YOUR code reporting
23 the right fault code, so that it can (in turn) behave correctly.
/Documentation/devicetree/bindings/pinctrl/
Dbrcm,ns-pinmux.yaml16 system configure controller correctly.
/Documentation/arch/s390/
D3270.ChangeLog18 * Do read and write lengths correctly in fs3270_read()
/Documentation/driver-api/media/drivers/
Dbttv-devel.rst14 To handle the grabber boards correctly, there is a array tvcards[] in
39 Of course you need a correctly installed soundcard unless you have the
/Documentation/driver-api/
Dconsole.rst148 The current crop of console drivers should still work correctly, but binding
150 be made to work correctly.
/Documentation/PCI/
Dacpi-info.rst28 can work correctly even on a system with new devices unknown to the OS.
35 is defined, an old OS needs to operate correctly even though it ignores the
57 BIOSes didn't use that bit correctly. The result is that the current ACPI
/Documentation/devicetree/bindings/sound/
Dti,ts3a227e.yaml15 switches automatically to route the microphone correctly. It also
/Documentation/hwmon/
Dnsa320.rst35 that contains 0x55 as a marker to indicate that data is being read correctly,
/Documentation/ABI/testing/
Dconfigfs-usb-gadget-mass-storage10 correctly. You should set it to true.
/Documentation/arch/x86/
Dkernel-stacks.rst95 To handle nested #DB correctly there exist two instances of DB stacks. On
139 entries), regardless of whether the frame pointer was set up correctly
/Documentation/userspace-api/media/v4l/
Dext-ctrls-dv.rst85 standard correctly (unfortunately quite common for HDMI and DVI-D).
144 standard correctly (unfortunately quite common for HDMI and DVI-D).
/Documentation/trace/coresight/
Dcoresight-perf.rst19 is working correctly. You can dump the content of this file as
41 correctly.

12345678910>>...12