| /openbmc/linux/arch/sh/include/cpu-sh2a/cpu/ |
| H A D | cache.h | 21 * Most of the SH-2A CCR1 definitions resemble the SH-4 ones. All others not
|
| /openbmc/linux/Documentation/devicetree/bindings/display/panel/ |
| H A D | tpo,tpg110.yaml | 38 The serial protocol has line names that resemble I2C but the
|
| /openbmc/linux/Documentation/devicetree/bindings/display/mediatek/ |
| H A D | mediatek,color.yaml | 16 resemble the other in their output characteristics.
|
| /openbmc/linux/arch/mips/bmips/ |
| H A D | setup.c | 182 * intended to somewhat resemble ARM; see in plat_mem_setup()
|
| /openbmc/linux/kernel/locking/ |
| H A D | spinlock_rt.c | 6 * resemble the non RT semantics:
|
| /openbmc/linux/Documentation/maintainer/ |
| H A D | feature-and-driver-maintainers.rst | 123 To an outsider the Linux kernel may resemble a hierarchical organization
|
| /openbmc/openpower-hw-diags/attn/ |
| H A D | attn_common.cpp | 58 // (Format should resemble FSP: HostBoot Reg:0000283C Data:AA801504 in addHbStatusRegs()
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | affs.rst | 150 Although the Amiga and Linux file systems resemble each other, there
|
| /openbmc/linux/arch/hexagon/kernel/ |
| H A D | traps.c | 32 /* Maybe should resemble arch/sh/kernel/traps.c ?? */
|
| /openbmc/linux/Documentation/userspace-api/netlink/ |
| H A D | specs.rst | 155 Note that the spec is "flattened" and is not meant to visually resemble
|
| /openbmc/linux/drivers/usb/gadget/legacy/ |
| H A D | ether.c | 50 * those MS-Windows drivers. Those added descriptors make it resemble a
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | xillybus.rst | 90 Xillybus presents independent data streams, which resemble pipes or TCP/IP
|
| /openbmc/linux/arch/alpha/kernel/ |
| H A D | sys_dp264.c | 636 /* Sharks strongly resemble Clipper, at least as far
|
| /openbmc/linux/drivers/gpu/drm/panel/ |
| H A D | panel-sitronix-st7703.c | 86 * resemble the ST7703 but the number of parameters often don't match in jh057n_init_sequence()
|
| /openbmc/linux/Documentation/spi/ |
| H A D | spi-summary.rst | 346 SPI protocol drivers somewhat resemble platform device drivers::
|
| /openbmc/linux/drivers/pci/controller/dwc/ |
| H A D | pcie-designware.c | 205 * These interfaces resemble the pci_find_*capability() interfaces, but these
|
| /openbmc/qemu/docs/devel/ |
| H A D | qapi-code-gen.rst | 737 them for munging QMP names that resemble C keywords or other
1345 resemble the element type; however, clients should examine member
|
| /openbmc/qemu/docs/interop/ |
| H A D | bitmaps.rst | 1485 will be backup chains that resemble the following:
|
| /openbmc/linux/Documentation/driver-api/usb/ |
| H A D | usb.rst | 188 resemble OHCI (hardware does much more work) as well as UHCI (some parts
|
| /openbmc/linux/net/sched/ |
| H A D | sch_htb.c | 1181 /* Resemble qdisc_graft behavior. */ in htb_attach_software()
|
| /openbmc/u-boot/drivers/usb/gadget/ |
| H A D | ether.c | 65 * those MS-Windows drivers. Those added descriptors make it resemble a
|
| /openbmc/linux/Documentation/networking/ |
| H A D | bonding.rst | 2004 For just a single target the options would resemble::
|
| /openbmc/linux/sound/pci/ac97/ |
| H A D | ac97_patch.c | 2946 * (also do some renaming, to resemble Windows driver naming) in patch_aztech_azf3328_specific()
|
| /openbmc/linux/net/ipv4/ |
| H A D | tcp.c | 156 * resemble the RFC.
|