Home
last modified time | relevance | path

Searched refs:EM (Results 26 – 46 of 46) sorted by relevance

12

/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-class-scsi_host104 (RW) Allows access to AHCI EM (enclosure management) buffer
105 directly if the host supports EM.
107 For eg. the AHCI driver supports SGPIO EM messages but the
108 SATA/AHCI specs do not define the SGPIO message format of the EM
/openbmc/u-boot/board/synopsys/emsdp/
H A DMAINTAINERS1 EM DEVELOPMENT KIT BOARD
/openbmc/linux/include/trace/events/
H A Dsunrpc.h793 #undef EM
799 EM( SS_FREE, "FREE" ) \
802 EM( SS_CONNECTED, "CONNECTED" ) \
812 EM( TCP_SYN_SENT, "SYN_SENT" ) \
813 EM( TCP_SYN_RECV, "SYN_RECV" ) \
814 EM( TCP_FIN_WAIT1, "FIN_WAIT1" ) \
817 EM( TCP_CLOSE, "CLOSE" ) \
819 EM( TCP_LAST_ACK, "LAST_ACK" ) \
820 EM( TCP_LISTEN, "LISTEN" ) \
835 #undef EM
[all …]
/openbmc/intel-ipmi-oem/
H A Dmeson.options4 option('using-entity-manager-decorators', type: 'feature', description: 'Enable using EM decorators…
/openbmc/linux/mm/
H A Ddebug.c25 #undef EM
27 #define EM(a, b) b, macro
/openbmc/linux/Documentation/devicetree/bindings/arm/tegra/
H A Dnvidia,tegra234-cbb.yaml22 fabric. Each Root MN contains a Error Monitor (EM) which detects and
23 logs error. Interrupts from various EM blocks are collated by Error
/openbmc/linux/Documentation/infiniband/
H A Dopa_vnic.rst21 Ethernet Manager (EM) which is part of the trusted Fabric Manager (FM)
125 Manager (EM) and the VNIC netdev. The VNIC netdev part allocates and frees
130 information required for encapsulation is configured by the EM via VEMA MAD
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Source/PLDM/
H A DEntity.interface.yaml8 converted to inventory D-Bus objects (by apps like EM and PIM), then the app
/openbmc/linux/Documentation/devicetree/bindings/rtc/
H A Dtrivial-rtc.yaml33 # EM Microelectronic EM3027 RTC
/openbmc/u-boot/arch/arc/
H A DKconfig160 bool "Synopsys EM Software Development Platform"
/openbmc/docs/designs/
H A Dpldm-stack.md439 and states D-Bus object paths, so the EM EID configuration or Terminus's
441 support sensors, effecters or status. When the EM EID configuration is not
473 Terminus's PDRs or the Terminus' EM JSON configuration files. This
511 interfaces to the D-Bus object path of PLDM sensor. The EM EID configuration or
513 `$SensorAuxName` can be found in the EM EID sensor configuration or the sensor
/openbmc/linux/Documentation/scsi/
H A Daacraid.rst126 9005:0285:108e:7aae SUN STK RAID EM (Narvi)
/openbmc/entity-manager/
H A DREADME.md70 answer to "Is X device supported". An EM configuration contains a number of
/openbmc/qemu/target/i386/tcg/
H A Ddecode-new.c.inc48 * operand. Therefore, M is often replaced by the more specific EM and WM
1170 [0xb2] = X86_OP_ENTRY3(LSS, G,v, EM,p, None, None),
1171 [0xb4] = X86_OP_ENTRY3(LFS, G,v, EM,p, None, None),
1172 [0xb5] = X86_OP_ENTRY3(LGS, G,v, EM,p, None, None),
1179 [0xc3] = X86_OP_ENTRY3(MOV, EM,y,G,y, None,None, cpuid(SSE2)), /* MOVNTI */
1611 [0xC4] = X86_OP_ENTRY3(LES, G,z, EM,p, None, None, chk(i64)),
1612 [0xC5] = X86_OP_ENTRY3(LDS, G,z, EM,p, None, None, chk(i64)),
/openbmc/linux/Documentation/devicetree/bindings/
H A Dvendor-prefixes.yaml422 description: EM Microelectronic
/openbmc/linux/drivers/rtc/
H A DKconfig662 tristate "EM Microelectronic EM3027"
664 If you say yes here you get support for the EM
/openbmc/linux/drivers/i2c/busses/
H A DKconfig637 I2C interface on the Renesas Electronics EM/EV family of processors.
/openbmc/linux/drivers/eisa/
H A Deisa.ids1073 KCI3202 "ET-32EM 32-bit EISA Bus Master Ethernet Adapter"
/openbmc/u-boot/doc/
H A DREADME.x86927 http://www.dediprog.com/pd/programmer-accessories/EM-TC-8
/openbmc/openbmc/poky/bitbake/lib/toaster/toastergui/static/css/
H A Dbootstrap.min.css.map1 …KZ,YAAA,KACA,WAAA,KP8tCH,gBOxtCC,QAAS,aACT,cAAA,IACA,aAAA,IAEF,GNiuCE,WAAY,EM/tCZ,cAAA,KAGA,GADF,G…
/openbmc/qemu/pc-bios/
H A Dqemu.rsrc173 $"00A8 00FF 00FF 00B0 000F 0812 2236 454D" /* .®.ˇ.ˇ.∞...."6EM */

12