| /linux/Documentation/devicetree/bindings/pci/ |
| H A D | baikal,bt1-pcie.yaml | 17 control module, so the proper interface initialization is supposed to be
67 clock signal is supposed to be attached to the corresponding Ref-pad
81 A comprehensive controller reset logic is supposed to be implemented
|
| H A D | snps,dw-pcie.yaml | 129 signal is supposed to be specified for the host controller.
186 supposed to be unmasked in the Root Control register).
195 Status register (the event is supposed to be unmasked in the
200 Status register (the event is supposed to be unmasked in the
|
| /linux/drivers/usb/core/ |
| H A D | otg_productlist.h | 18 /* FIXME actually, printers are NOT supposed to use device classes;
19 * they're supposed to use interface classes...
|
| /linux/drivers/mtd/maps/ |
| H A D | physmap-bt1-rom.c | 107 /* It's supposed to be read-only MTD. */ in of_flash_probe_bt1_rom()
119 dev_warn(dev, "Bank width is supposed to be 32 bits wide\n"); in of_flash_probe_bt1_rom()
|
| /linux/Documentation/devicetree/bindings/net/pcs/ |
| H A D | snps,dw-xpcs.yaml | 56 the CSR address MMD+REG[20:8] is supposed to be written in there
80 The MCI and APB3 interfaces are supposed to be equipped with a clock
|
| /linux/net/core/ |
| H A D | of_net.c | 106 * checked first, because that is supposed to contain to "most recent" MAC
113 * Note that the 'address' property is supposed to contain a virtual address of
|
| /linux/arch/powerpc/platforms/52xx/ |
| H A D | lite5200.c | 48 * Firmware is supposed to be responsible for this. If you are creating a
82 * Firmware is supposed to be responsible for this. If you are creating a
|
| /linux/include/linux/mailbox/ |
| H A D | zynqmp-ipi-message.h | 13 * Client is supposed to be aware of this.
|
| /linux/drivers/i3c/ |
| H A D | Kconfig | 9 It's supposed to be backward compatible with I2C while providing
|
| /linux/Documentation/dev-tools/kunit/ |
| H A D | faq.rst | 12 A `unit test <https://martinfowler.com/bliki/UnitTest.html>`_ is supposed to
49 - A unit test is supposed to test a single unit of code in isolation. A unit
|
| /linux/include/linux/input/ |
| H A D | vivaldi-fmap.h | 16 * This structure is supposed to be used by ChromeOS keyboards using
|
| H A D | matrix_keypad.h | 29 * This structure is supposed to be used by platform code to supply
|
| /linux/Documentation/virt/kvm/x86/ |
| H A D | msr.rst | 227 supposed to clear 'flags' when it is done handling #PF exception so the
238 Guest is supposed to write '0' to 'token' when it is done handling
374 field in 'struct kvm_vcpu_pv_apf_data' is cleared it is supposed to
|
| /linux/include/linux/soc/ti/ |
| H A D | ti-msgmgr.h | 24 * on SoC. Client is supposed to be aware of this.
|
| /linux/include/linux/usb/ |
| H A D | iowarrior.h | 18 /* vendor id : supposed to be USB_VENDOR_ID_CODEMERCS in all cases */
|
| /linux/Documentation/devicetree/bindings/hsi/ |
| H A D | client-devices.txt | 1 Each HSI port is supposed to have one child node, which
|
| /linux/Documentation/driver-api/tty/ |
| H A D | tty_buffer.rst | 10 Drivers are supposed to fill the buffer by one of those functions below and
|
| /linux/drivers/pci/ |
| H A D | pci-pf-stub.c | 15 * This table provides the list of IDs this driver is supposed to bind
|
| /linux/arch/arm/boot/dts/allwinner/ |
| H A D | sun5i-gr8-evb.dts | 310 * pin supposed to control VBUS, an ID pin, a VBUS detect pin,
313 * Except that the pin supposed to control VBUS is not
|
| /linux/Documentation/input/ |
| H A D | gamepad.rst | 12 document defines how gamepads are supposed to report their data.
79 All new gamepads are supposed to comply with this mapping. Please report any
|
| /linux/Documentation/devicetree/bindings/power/supply/ |
| H A D | adc-battery.yaml | 20 least the temperature channel is supposed to measure the battery
|
| /linux/include/linux/ |
| H A D | drbd_genl_api.h | 18 * to know which volume number within the resource this is supposed to be.
|
| /linux/Documentation/devicetree/bindings/cache/ |
| H A D | baikal,bt1-l2-ctl.yaml | 18 supposed to be a child of the system controller.
|
| /linux/Documentation/wmi/ |
| H A D | driver-development-guide.rst | 9 as an introductory guide for WMI driver writers using this API. It is supposed
40 helps in understanding how the WMI device is supposed to work. The path of the ACPI
|
| /linux/include/uapi/linux/ |
| H A D | kcov.h | 32 * was supposed to be 0 in such a call. So, for reasons of backward
|