Home
last modified time | relevance | path

Searched refs:SMI (Results 1 – 25 of 36) sorted by relevance

12

/Linux-v4.19/drivers/gpu/drm/i915/
Di915_cmd_parser.c201 #define SMI STD_MI_OPCODE_SHIFT macro
215 CMD( MI_NOOP, SMI, F, 1, S ),
216 CMD( MI_USER_INTERRUPT, SMI, F, 1, R ),
217 CMD( MI_WAIT_FOR_EVENT, SMI, F, 1, M ),
218 CMD( MI_ARB_CHECK, SMI, F, 1, S ),
219 CMD( MI_REPORT_HEAD, SMI, F, 1, S ),
220 CMD( MI_SUSPEND_FLUSH, SMI, F, 1, S ),
221 CMD( MI_SEMAPHORE_MBOX, SMI, !F, 0xFF, R ),
222 CMD( MI_STORE_DWORD_INDEX, SMI, !F, 0xFF, R ),
223 CMD( MI_LOAD_REGISTER_IMM(1), SMI, !F, 0xFF, W,
[all …]
/Linux-v4.19/Documentation/
Ddcdbas.txt28 management information via a system management interrupt (SMI). The SMI data
30 buffer is required for the SMI. The driver maintains the memory required for
31 the SMI and provides a way for the application to generate the SMI.
41 a SMI using this driver:
45 3) Write "1" to smi_request to generate a calling interface SMI or
46 "2" to generate a raw SMI.
57 a driver perform a SMI after the OS has finished shutting down.
71 2) Write type of SMI that driver needs to perform to host_control_smi_type.
74 (Driver will perform host control SMI when it is notified that the OS
78 Host Control SMI Type
[all …]
DIPMI.txt244 view of the IPMI interfaces. It allows multiple SMI interfaces to be
246 and the user should not have to care what type of SMI is below them.
255 To handle this, and to allow for discovery, you register an SMI
264 ipmi_create_user. The interface number specifies which SMI you want
354 The Lower Layer (SMI) Interface
357 As mentioned before, multiple SMI interfaces may be registered to the
360 in the order they register, although if an SMI unregisters and then
626 The preaction may be "pre_smi" for an indication through the SMI
627 interface, "pre_int" for an indication through the SMI with an
/Linux-v4.19/Documentation/devicetree/bindings/memory-controllers/
Dmediatek,smi-common.txt1 SMI (Smart Multimedia Interface) Common
5 Mediatek SMI have two generations of HW architecture, mt2712 and mt8173 use
6 the second generation of SMI HW while mt2701 uses the first generation HW of
7 SMI.
9 There's slight differences between the two SMI, for generation 2, the
13 SMI generation 1 to transform the smi clock into emi clock domain, but that is
14 not needed for SMI generation 2.
21 - reg : the register and size of the SMI block.
Dmediatek,smi-larb.txt1 SMI (Smart Multimedia Interface) Local Arbiter
/Linux-v4.19/Documentation/devicetree/bindings/iommu/
Dmediatek,iommu.txt14 SMI Common(Smart Multimedia Interface Common)
19 SMI larb0 SMI larb1 ... SoCs have several SMI local arbiter(larb).
29 As above, The Multimedia HW will go through SMI and M4U while it
30 access EMI. SMI is a bridge between m4u and the Multimedia HW. It contain
33 directly with EMI. And also SMI help control the power domain and clocks for
/Linux-v4.19/Documentation/devicetree/bindings/net/dsa/
Drealtek-smi.txt1 Realtek SMI-based Switches
4 The SMI "Simple Management Interface" is a two-wire protocol using
7 SMI-based Realtek devices.
37 interrupt line coming out of one of the SMI-based chips. It most
50 This defines the internal MDIO bus of the SMI device, mostly for the
56 - compatible: should be set to "realtek,smi-mdio" for all SMI devices
/Linux-v4.19/drivers/media/pci/smipcie/
DKconfig2 tristate "SMI PCIe DVBSky cards"
12 Support for cards with SMI PCIe bridge:
/Linux-v4.19/Documentation/devicetree/bindings/mtd/
Dspear_smi.txt1 * SPEAr SMI
9 - clock-rate : Functional clock rate of SMI in Hz
/Linux-v4.19/arch/arm/mach-omap2/
Dsleep34xx.S110 smc #1 @ call SMI monitor (smi #1)
431 smc #1 @ call SMI monitor (smi #1)
442 smc #1 @ call SMI monitor (smi #1)
457 smc #1 @ call SMI monitor (smi #1)
467 smc #0 @ Call SMI monitor (smieq)
473 smc #0 @ Call SMI monitor (smieq)
478 smc #0 @ Call SMI monitor (smieq)
/Linux-v4.19/Documentation/devicetree/bindings/net/
Dmarvell-orion-mdio.txt13 not present, the length is the size of the SMI register (4 bytes)
18 - interrupts: interrupt line number for the SMI error/done interrupt
Dcavium-mdio.txt1 * System Management Interface (SMI) / MDIO
33 * System Management Interface (SMI) / MDIO Nexus
/Linux-v4.19/drivers/net/dsa/
DKconfig56 tristate "Realtek SMI Ethernet switch family support"
63 This enables support for the Realtek SMI-based switch
/Linux-v4.19/drivers/firmware/google/
DKconfig12 tristate "SMI interface for Google platforms"
16 Say Y here if you want to enable SMI callbacks for Google
/Linux-v4.19/Documentation/devicetree/bindings/display/
Dsm501fb.txt11 - interrupts : SMI interrupt to the cpu should be described here.
/Linux-v4.19/drivers/net/dsa/mv88e6xxx/
DKconfig16 This registers set at internal SMI address 0x1C provides extended
/Linux-v4.19/Documentation/hwmon/
Dnct790458 - SMI
/Linux-v4.19/arch/arm/boot/dts/
Ddove-cm-a510.dtsi56 * E1: PHY RTL8211D on internal GbE (SMI address 0x03)
126 /* Optional RTL8211D GbE PHY on SMI address 0x03 */
/Linux-v4.19/tools/perf/Documentation/
Dperf-stat.txt300 Measure SMI cost if msr/aperf/ and msr/smi/ events are supported.
303 freeze core counters on SMI.
305 The cost of SMI can be measured by (aperf - unhalted core cycles).
307 In practice, the percentages of SMI cycles is very useful for performance
309 The output is SMI cycles%, equals to (aperf - unhalted core cycles) / aperf
/Linux-v4.19/Documentation/ABI/testing/
Dsysfs-firmware-gsmi6 that provides callback functionality via explicit SMI
/Linux-v4.19/drivers/net/ethernet/marvell/
Dpxa168_eth.c58 #define SMI 0x0010 macro
1302 for (i = 0; rdl(pep, SMI) & SMI_BUSY; i++) { in smi_wait_ready()
1321 wrl(pep, SMI, (phy_addr << 16) | (regnum << 21) | SMI_OP_R); in pxa168_smi_read()
1323 for (i = 0; !((val = rdl(pep, SMI)) & SMI_R_VALID); i++) { in pxa168_smi_read()
1345 wrl(pep, SMI, (phy_addr << 16) | (regnum << 21) | in pxa168_smi_write()
/Linux-v4.19/Documentation/devicetree/bindings/interrupt-controller/
Dbrcm,bcm2835-armctrl-ic.txt95 16: SMI
/Linux-v4.19/drivers/mtd/devices/
DKconfig110 tristate "SPEAR MTD NOR Support through SMI controller"
114 This enable SNOR support on SPEAR platforms using SMI controller
/Linux-v4.19/Documentation/trace/
Dhwlat_detector.rst28 the only thing that could do that would be an SMI or other hardware hiccup
/Linux-v4.19/Documentation/watchdog/
Dwatchdog-parameters.txt116 1=SuperMicro Pent3, 2=SuperMicro Pent4+, 911=Broken SMI BIOS
169 0 = RESET(*) 1 = SMI 2 = NMI 3 = SCI

12