Searched +full:ssif +full:- +full:bmc (Results 1 – 9 of 9) sorted by relevance
/linux/Documentation/devicetree/bindings/ipmi/ |
H A D | ssif-bmc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/ipmi/ssif-bmc.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: SSIF IPMI BMC interface 9 description: SSIF IPMI BMC device bindings 12 - Quan Nguyen <quan@os.amperecomputing.com> 17 - ssif-bmc 23 - compatible 24 - reg [all …]
|
/linux/drivers/char/ipmi/ |
H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only 7 tristate 'IPMI top-level message handler' 17 See <file:Documentation/driver-api/ipmi.rst> for more details on the driver. 71 tristate 'IPMI SMBus handler (SSIF)' 74 Provides a driver for a SMBus interface to a BMC, meaning that you 83 It supports normal system interface messages to a BMC on the IPMB 91 Provides a driver for OPAL firmware-based IPMI interfaces. 113 tristate "Aspeed KCS IPMI BMC driver" 118 The driver implements the BMC side of the KCS contorller, it 119 provides the access of KCS IO space for BMC side. [all …]
|
H A D | ssif_bmc.c | 1 // SPDX-License-Identifier: GPL-2.0-only 3 * The driver for BMC side of SSIF interface 22 #define DEVICE_NAME "ipmi-ssif-host" 43 * IPMI 2.0 Spec, section 12.7 SSIF Timing, 44 * Request-to-Response Time is T6max(250ms) - T1max(20ms) - 3ms = 227ms 59 * SSIF internal states: 82 /* ssif bmc spinlock */ 90 /* Flag to identify a Multi-part Read Transaction */ 95 /* Block Number of a Multi-part Read Transaction */ 101 /* Buffer for SSIF Transaction part*/ [all …]
|
H A D | ipmi_ssif.c | 1 // SPDX-License-Identifier: GPL-2.0+ 6 * compliant device. Called SSIF by the IPMI spec. 12 * non-blocking I2C interface, add support for multi-part 20 * This file holds the "policy" for the interface to the SSIF state 22 * and drives the real SSIF state machine. 63 /* ssif_debug is a bit-field 64 * SSIF_DEBUG_MSG - commands and their responses 65 * SSIF_DEBUG_STATES - message states 66 * SSIF_DEBUG_TIMING - Measure times between events in the driver 103 /* FIXME - add watchdog stuff. */ [all …]
|
/linux/arch/arm/boot/dts/aspeed/ |
H A D | aspeed-bmc-ampere-mtjade.dts | 1 // SPDX-License-Identifier: GPL-2.0+ 2 /dts-v1/; 3 #include "aspeed-g5.dtsi" 4 #include <dt-bindings/gpio/aspeed-gpio.h> 7 model = "Ampere Mt. Jade BMC"; 8 compatible = "ampere,mtjade-bmc", "aspeed,ast2500"; 12 * i2c bus 50-57 assigned to NVMe slot 0-7 24 * i2c bus 60-67 assigned to NVMe slot 8-15 36 * i2c bus 70-77 assigned to NVMe slot 16-23 48 * i2c bus 80-81 assigned to NVMe M2 slot 0-1 [all …]
|
H A D | aspeed-bmc-ampere-mtmitchell.dts | 1 // SPDX-License-Identifier: GPL-2.0-only 4 /dts-v1/; 6 #include "aspeed-g6.dtsi" 7 #include <dt-bindings/i2c/i2c.h> 8 #include <dt-bindings/gpio/aspeed-gpio.h> 11 model = "Ampere Mt.Mitchell BMC"; 12 compatible = "ampere,mtmitchell-bmc", "aspeed,ast2600"; 27 * i2c bus 30-31 assigned to OCP slot 0-1 33 * i2c bus 32-33 assigned to Riser slot 0-1 39 * i2c bus 38-39 assigned to FRU on Riser slot 0-1 [all …]
|
H A D | aspeed-bmc-facebook-catalina.dts | 1 // SPDX-License-Identifier: GPL-2.0+ 3 /dts-v1/; 5 #include "aspeed-g6.dtsi" 6 #include <dt-bindings/gpio/aspeed-gpio.h> 7 #include <dt-bindings/usb/pd.h> 8 #include <dt-bindings/leds/leds-pca955x.h> 9 #include <dt-bindings/interrupt-controller/irq.h> 10 #include <dt-bindings/i2c/i2c.h> 13 model = "Facebook Catalina BMC"; 14 compatible = "facebook,catalina-bmc", "aspeed,ast2600"; [all …]
|
/linux/arch/arm/boot/dts/nuvoton/ |
H A D | nuvoton-npcm730-kudo.dts | 1 // SPDX-License-Identifier: GPL-2.0 4 /dts-v1/; 5 #include "nuvoton-npcm730.dtsi" 7 #include <dt-bindings/gpio/gpio.h> 41 stdout-path = &serial3; 48 iio-hwmon { 49 compatible = "iio-hwmon"; 50 io-channels = <&adc 0>, <&adc 1>, <&adc 2>, <&adc 3>, 55 compatible = "nuvoton,npcm750-jtag-master"; 56 #address-cells = <1>; [all …]
|
/linux/Documentation/driver-api/ |
H A D | ipmi.rst | 12 standardized database for field-replaceable units (FRUs) and a watchdog 16 system (called a Baseboard Management Controller, or BMC) and 25 ------------- 32 No matter what, you must pick 'IPMI top-level message handler' to use 35 The message handler does not provide any user-level interfaces. 50 these enabled and let the drivers auto-detect what is present. 61 "The SMBus Driver" on how to hand-configure your system. 65 the kernel, then via a kernel command-line option you can have the 74 'IPMI Poweroff' to do this. The driver will auto-detect if the system 89 ------------ [all …]
|