Home
last modified time | relevance | path

Searched full:supposed (Results 1 – 25 of 72) sorted by relevance

123

/Documentation/devicetree/bindings/hsi/
Dclient-devices.txt1 Each HSI port is supposed to have one child node, which
Domap-ssi.txt5 while the controller found inside OMAP4 is supposed to be fully compliant
/Documentation/devicetree/bindings/net/
Dmarvell-armada-370-neta.txt30 Obligatory, when the port is supposed to use hardware
/Documentation/vm/
Dzsmalloc.rst8 supposed to work well under low memory conditions. In particular, it
Dactive_mm.rst20 > the task_struct are supposed to be used? (My apologies if this was
/Documentation/admin-guide/device-mapper/
Dwritecache.rst6 doesn't cache reads because reads are supposed to be cached in page cache
/Documentation/input/
Dgamepad.rst12 document defines how gamepads are supposed to report their data.
79 All new gamepads are supposed to comply with this mapping. Please report any
/Documentation/
Dio-mapping.txt91 kmap_atomic_pfn isn't really supposed to be used with device pages, but it
Dxz.txt61 when encoding files that are supposed to be decoded by the kernel. With
/Documentation/driver-api/soundwire/
Derror_handling.rst43 ClockStopPrepare, the bus driver is supposed to poll a register field until
/Documentation/driver-api/
Dhsi.rst43 In the Linux kernel the hsi subsystem is supposed to be used for HSI devices.
/Documentation/ABI/testing/
Dsysfs-firmware-dmi-entries18 'handle' that is supposed to be unique amongst all
/Documentation/firmware-guide/acpi/
Dgpio-properties.rst131 available to the driver can be used to identify the device and that is supposed
134 the driver is supposed to know what to use the GpioIo()/GpioInt() resources for
/Documentation/driver-api/acpi/
Dscan_handlers.rst48 where ids is the list of IDs of device nodes the given handler is supposed to
/Documentation/filesystems/
Dxfs-self-describing-metadata.txt41 is supposed to be. We can't even identify if it is the right place. Put simply,
43 supposed to be there and the contents are valid".
127 For example, we can determine whether a metadata object is supposed to be free
/Documentation/x86/
Dmicrocode.rst10 The kernel has a x86 microcode loading facility which is supposed to
/Documentation/media/uapi/v4l/
Dformat.rst90 Drivers are not supposed to convert image formats in kernel space.
/Documentation/devicetree/bindings/display/panel/
Dpanel-common.yaml88 This panel is supposed to communicate that it's ready via HPD
/Documentation/devicetree/bindings/i3c/
Di3c.txt71 All I3C devices are supposed to support DAA (Dynamic Address Assignment), and
/Documentation/power/
Dpci.rst52 requiring the device to be active. After receiving a PME the kernel is supposed
145 majority of x86-based systems, it is supposed to implement device power
160 to be defined separately for each device supposed to be handled with the help of
175 3 inclusive) the kernel is supposed to (1) enable the power resources required
178 is going to be put into a low-power state (D1-D3) and is supposed to generate
191 into and the kernel is supposed to obtain this information by executing the
195 target state of the system. The kernel is then supposed to use the device's
196 _SxW control method to obtain the number of that state. It also is supposed to
/Documentation/admin-guide/gpio/
Dsysfs.rst8 ARE SUPPOSED TO USE THE CHARACTER DEVICE ABI. THIS OLD SYSFS ABI WILL
/Documentation/devicetree/
Doverlay-notes.txt105 Note that a notifier callback is not supposed to store pointers to a device
/Documentation/driver-api/early-userspace/
Dearly_userspace_support.rst138 initrd. The initrd must contain a binary '/linuxrc' which is supposed to
/Documentation/virt/kvm/
Dnested-vmx.txt62 this structure is *opaque* to its user, who is not supposed to know or care
/Documentation/arm/samsung-s3c24xx/
Dgpio.rst76 would return the value the pin is supposed to be outputting).

123