Home
last modified time | relevance | path

Searched full:knowing (Results 1 – 25 of 36) sorted by relevance

12

/Documentation/ABI/testing/
Ddebugfs-ec8 Knowing the EC GPE one can watch the amount of HW events related to
Dsysfs-bus-vfio-mdev71 Userspace applications interested in knowing the name of
84 Userspace applications interested in knowing the details of
Dsysfs-bus-pci185 Userspace applications interested in knowing the
197 Userspace applications interested in knowing the
213 Userspace applications interested in knowing the
/Documentation/devicetree/bindings/mailbox/
Damlogic,meson-gxbb-mhu.yaml17 received data. However, there is no specified way of knowing if the sent
Darm-mhu.txt7 received data. However, there is no specified way of knowing if the sent
/Documentation/devicetree/bindings/gpio/
Dgpio-pcf857x.txt8 low/high value, without knowing the last value written since the chip came out
/Documentation/arm/
Dporting.rst10 The following symbol definitions rely on you knowing the translation that
/Documentation/
Dindex.rst69 knowing how things are done will make the process of getting your changes
Dkref.txt125 data, the kref_put() handles knowing when the data is not referenced
/Documentation/driver-api/gpio/
Dintro.rst44 firmware knowing how they're used).
/Documentation/x86/
Dkernel-stacks.rst126 mark, knowing that it's part of the real backtrace.
/Documentation/power/
Denergy-model.rst8 The Energy Model (EM) framework serves as an interface between drivers knowing
Dvideo.rst86 (proper X, knowing your hardware, not XF68_FBcon) might have better
/Documentation/usb/
Dgadget_multi.rst123 Knowing how MacOS is based on BSD and BSD is an Open Source it is
/Documentation/filesystems/
Dxfs-self-describing-metadata.txt100 Another key information point in forensic analysis is knowing who the metadata
102 and/or corrupted, and how long ago that it was last modified. Knowing the owner
Dgfs2-glocks.txt185 Knowing both the time it takes a lock request to complete and
/Documentation/firmware-guide/acpi/
Dgpio-properties.rst198 knowing about which exact device they are servicing on. It implies that
/Documentation/fb/
Dsstfb.rst186 - The 24/32 is not likely to work anytime soon, knowing that the
/Documentation/hid/
Dhid-sensor.rst162 way to obfuscate the data being communicated by a sensor. Without knowing the
/Documentation/admin-guide/mm/
Duserfaultfd.rst158 usual with the UFFDIO_COPY|ZEROPAGE (without actually knowing if it
/Documentation/media/v4l-drivers/
Dphilips.rst179 Some points worth knowing:
/Documentation/media/uapi/mediactl/
Drequest-api.rst52 with different configurations in advance, knowing that the configuration will be
/Documentation/admin-guide/
Dthunderbolt.rst27 knowing about it. There are ways to prevent this by setting up an IOMMU but
/Documentation/driver-api/nfc/
Dnfc-hci.rst51 without knowing the pipe connected to it.
/Documentation/networking/
Dj1939.rst50 knowing it. The individual TP & ETP sessions _must_ be serialized

12