/linux-6.14.4/Documentation/devicetree/bindings/arm/aspeed/ |
D | aspeed.yaml | 20 - delta,ahe50dc-bmc 21 - facebook,galaxy100-bmc 22 - facebook,wedge100-bmc 23 - facebook,wedge40-bmc 24 - microsoft,olympus-bmc 25 - quanta,q71l-bmc 26 - tyan,palmetto-bmc 27 - yadro,vesnin-bmc 33 - amd,daytonax-bmc 34 - amd,ethanolx-bmc [all …]
|
/linux-6.14.4/arch/arm/boot/dts/aspeed/ |
D | Makefile | 6 aspeed-bmc-amd-daytonax.dtb \ 7 aspeed-bmc-amd-ethanolx.dtb \ 8 aspeed-bmc-ampere-mtjade.dtb \ 9 aspeed-bmc-ampere-mtjefferson.dtb \ 10 aspeed-bmc-ampere-mtmitchell.dtb \ 11 aspeed-bmc-arm-stardragon4800-rep2.dtb \ 12 aspeed-bmc-asrock-e3c246d4i.dtb \ 13 aspeed-bmc-asrock-e3c256d4i.dtb \ 14 aspeed-bmc-asrock-romed8hm3.dtb \ 15 aspeed-bmc-asrock-spc621d8hm3.dtb \ [all …]
|
D | aspeed-bmc-facebook-greatlakes.dts | 11 model = "Facebook Greatlakes BMC"; 12 compatible = "facebook,greatlakes-bmc", "aspeed,ast2600"; 87 label = "bmc"; 247 /*B0-B7*/ "power-bmc-nic","presence-ocp-debug", 248 "power-bmc-slot1","power-bmc-slot2", 249 "power-bmc-slot3","power-bmc-slot4","","", 254 /*F0-F7*/ "slot1-bmc-reset-button","slot2-bmc-reset-button", 255 "slot3-bmc-reset-button","slot4-bmc-reset-button", 261 /*I0-I7*/ "","","","","","","bb-bmc-button","", 265 /*M0-M7*/ "","power-nic-bmc-enable","","usb-bmc-enable","","reset-cause-usb-hub","","", [all …]
|
/linux-6.14.4/drivers/char/ipmi/ |
D | Kconfig | 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 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. 125 tristate "NPCM KCS IPMI BMC driver" 130 The driver implements the BMC side of the KCS contorller, it 131 provides the access of KCS IO space for BMC side. 138 tristate "IPMI character device interface for BMC KCS devices" 140 Provides a BMC-side character device implementing IPMI [all …]
|
D | ipmi_msghandler.c | 311 * accessing those. If those change on a BMC, a new BMC is allocated. 315 struct list_head intfs; /* Interfaces on this BMC. */ 330 static int bmc_get_device_id(struct ipmi_smi *intf, struct bmc_device *bmc, 469 * interface is used by being looked up through the BMC 475 struct bmc_device *bmc; member 553 * The event receiver for my BMC, only really used at panic 627 * This mutex keeps us from adding the same BMC twice. 2502 intf->bmc->dyn_id_set = 0; in bmc_device_id_handler() 2507 msg->msg.data, msg->msg.data_len, &intf->bmc->fetch_id); in bmc_device_id_handler() 2511 intf->bmc->cc = msg->msg.data[0]; in bmc_device_id_handler() [all …]
|
D | kcs_bmc_cdev_ipmi.c | 6 #define pr_fmt(fmt) "kcs-bmc: " fmt 22 /* Different phases of the KCS BMC module. 24 * BMC should not be expecting nor sending any data. 26 * BMC is receiving a WRITE_START command from system software. 28 * BMC is receiving a data byte from system software. 30 * BMC is waiting a last data byte from system software. 32 * BMC has received the whole request from system software. 34 * BMC is waiting the response from the upper IPMI service. 36 * BMC is transferring the response to system software. 38 * BMC is waiting error status request from system software. [all …]
|
D | bt-bmc.c | 7 #include <linux/bt-bmc.h> 20 * This is a BMC device used to communicate to the host 164 * buffered by the host before a notification is sent to the BMC that 258 * There's no interrupt for clearing bmc busy so we have to in bt_bmc_write() 395 * Configure IRQs on the bmc clearing the H2B and HBUSY bits; in bt_bmc_config_irq() 396 * H2B will be asserted when the bmc has data for us; HBUSY in bt_bmc_config_irq() 414 dev_info(dev, "Found bt bmc device\n"); in bt_bmc_probe() 472 { .compatible = "aspeed,ast2400-ibt-bmc" }, 473 { .compatible = "aspeed,ast2500-ibt-bmc" }, 474 { .compatible = "aspeed,ast2600-ibt-bmc" },
|
/linux-6.14.4/Documentation/devicetree/bindings/ipmi/ |
D | aspeed,ast2400-kcs-bmc.yaml | 4 $id: http://devicetree.org/schemas/ipmi/aspeed,ast2400-kcs-bmc.yaml# 7 title: ASPEED BMC KCS Devices 13 The Aspeed BMC SoCs typically use the Keyboard-Controller-Style (KCS) 22 - aspeed,ast2400-kcs-bmc-v2 23 - aspeed,ast2500-kcs-bmc-v2 24 - aspeed,ast2600-kcs-bmc 30 - aspeed,ast2400-kcs-bmc 31 - aspeed,ast2500-kcs-bmc 60 Note that the generated interrupt is issued from the BMC to the host, and 61 thus the target interrupt controller is not captured by the BMC's [all …]
|
D | ssif-bmc.yaml | 4 $id: http://devicetree.org/schemas/ipmi/ssif-bmc.yaml# 7 title: SSIF IPMI BMC interface 9 description: SSIF IPMI BMC device bindings 17 - ssif-bmc 34 ssif-bmc@10 { 35 compatible = "ssif-bmc";
|
D | npcm7xx-kcs-bmc.txt | 9 "nuvoton,npcm750-kcs-bmc" 10 "nuvoton,npcm845-kcs-bmc", "nuvoton,npcm750-kcs-bmc" 26 compatible = "nuvoton,npcm750-kcs-bmc"; 34 compatible = "nuvoton,npcm750-kcs-bmc";
|
D | aspeed,ast2400-ibt-bmc.txt | 10 "aspeed,ast2400-ibt-bmc" 11 "aspeed,ast2500-ibt-bmc" 12 "aspeed,ast2600-ibt-bmc" 24 compatible = "aspeed,ast2400-ibt-bmc";
|
/linux-6.14.4/Documentation/ABI/testing/ |
D | sysfs-driver-intel-m10-bmc | 1 What: /sys/bus/.../drivers/intel-m10-bmc/.../bmc_version 6 MAX10 BMC chip. 9 What: /sys/bus/.../drivers/intel-m10-bmc/.../bmcfw_version 14 BMC chip. 17 What: /sys/bus/.../drivers/intel-m10-bmc/.../mac_address 23 that is managed by the Intel MAX10 BMC. It is stored in 24 FLASH storage and is mirrored in the MAX10 BMC register 28 What: /sys/bus/.../drivers/intel-m10-bmc/.../mac_count 34 MAX10 BMC. This value is stored in FLASH and is mirrored 35 in the MAX10 BMC register space.
|
/linux-6.14.4/arch/arm/mach-npcm/ |
D | Kconfig | 10 bool "Support for WPCM450 BMC (Hermon)" 16 General support for WPCM450 BMC (Hermon). 18 Winbond/Nuvoton WPCM450 BMC based on the ARM926EJ-S. 21 bool "Support for NPCM7xx BMC (Poleg)" 38 General support for NPCM7xx BMC (Poleg). 40 Nuvoton NPCM7xx BMC based on the Cortex A9.
|
/linux-6.14.4/Documentation/hwmon/ |
D | intel-m10-bmc-hwmon.rst | 3 Kernel driver intel-m10-bmc-hwmon 8 * Intel MAX 10 BMC for Intel PAC N3000 19 support for the Intel MAX 10 Board Management Controller (BMC) chip. 20 The BMC chip is integrated in some Intel Programmable Acceleration 22 sensor data of different components on the board. The BMC firmware is 27 The BMC chip is implemented using the Intel MAX 10 CPLD. It could be 30 variants, but now it only supports the BMC for Intel PAC N3000. 38 - Intel MAX 10 BMC for Intel PAC N3000:
|
D | ftsteutates.rst | 18 The BMC Teutates is the Eleventh generation of Superior System 20 functionality of the BMC Theseus and contains several new features and 30 The 4 voltages require a board-specific multiplier, since the BMC can 42 /Services/Software_Tools/Linux_SystemMonitoring_Watchdog_GPIO/BMC-Teutates_Specification_V1.21.pdf
|
/linux-6.14.4/drivers/mfd/ |
D | menf21bmc.c | 3 * MEN 14F021P00 Board Management Controller (BMC) MFD Core Driver. 41 "BMC in production mode. Exit production mode\n"); in menf21bmc_wdt_exit_prod_mode() 66 dev_err(&client->dev, "failed to get BMC major revision\n"); in menf21bmc_probe() 72 dev_err(&client->dev, "failed to get BMC minor revision\n"); in menf21bmc_probe() 78 dev_err(&client->dev, "failed to get BMC main revision\n"); in menf21bmc_probe() 86 * We have to exit the Production Mode of the BMC to activate the in menf21bmc_probe() 98 dev_err(&client->dev, "failed to add BMC sub-devices\n"); in menf21bmc_probe() 119 MODULE_DESCRIPTION("MEN 14F021P00 BMC mfd core driver");
|
D | intel-m10-bmc-spi.c | 11 #include <linux/mfd/intel-m10-bmc.h> 42 * This check is to filter out the very old legacy BMC versions. In the in check_m10bmc_version() 43 * old BMC chips, the BMC version info is stored in the old version in check_m10bmc_version() 45 * not been M10BMC_N3000_VER_LEGACY_INVALID (0xffffffff). But in new BMC in check_m10bmc_version() 172 .name = "intel-m10-bmc", 180 MODULE_DESCRIPTION("Intel MAX 10 BMC SPI bus interface"); 183 MODULE_ALIAS("spi:intel-m10-bmc");
|
/linux-6.14.4/drivers/net/ethernet/meta/fbnic/ |
D | fbnic_rpc.c | 111 * shared between the host and the BMC they can be directed to in fbnic_bmc_rpc_all_multi_config() 113 * BMC. in fbnic_bmc_rpc_all_multi_config() 140 * BMC may have an all-multi rule already in place. As such in fbnic_bmc_rpc_all_multi_config() 142 * to modify the rules for the ALL MULTI below if the BMC in fbnic_bmc_rpc_all_multi_config() 156 /* Rewrite TCAM rule 23 to handle BMC all-multi traffic */ in fbnic_bmc_rpc_all_multi_config() 161 /* MACDA 0 - 3 is reserved for the BMC MAC address */ in fbnic_bmc_rpc_all_multi_config() 183 /* Check if BMC is present */ in fbnic_bmc_rpc_init() 187 /* Fetch BMC MAC addresses from firmware capabilities */ in fbnic_bmc_rpc_init() 191 /* Validate BMC MAC addresses */ in fbnic_bmc_rpc_init() 202 "No slot for BMC MAC address[%d]\n", j); in fbnic_bmc_rpc_init() [all …]
|
D | fbnic_rpc.h | 78 /* Reserve the first 2 entries for the use by the BMC so that we can 79 * avoid allowing rules to get in the way of BMC unicast traffic. 84 /* We reserve the last 14 entries for RSS rules on the host. The BMC 86 * use MACDA TCAM entry 23 to store the BMC MAC address. 126 /* TCAM 0 - 3 reserved for BMC MAC addresses */ 137 * for the ALL MULTI address if the list is full, or the BMC has requested
|
/linux-6.14.4/include/uapi/linux/ |
D | aspeed-lpc-ctrl.h | 22 * This driver provides a window for the host to access a BMC resource 23 * across the BMC <-> Host LPC bus. 25 * window_type: The BMC resource that the host will access through the 26 * window. BMC flash and BMC RAM. 37 * offset: Offset into the BMC window that should be mapped to the
|
D | aspeed-p2a-ctrl.h | 11 * the host to read and write to various regions of the BMC's memory. 25 * property of specific windows into the ASPEED BMC's memory. 27 * A user can map a region of the BMC's memory as read-only or read-write, with 33 * Unlock a region of BMC physical memory for access from the host.
|
/linux-6.14.4/drivers/soc/aspeed/ |
D | Kconfig | 14 also provides a read/write interface to a BMC ram region where the 24 allows the BMC to listen on and save the data written by 38 tristate "ASPEED P2A (VGA MMIO to BMC) bridge control" 43 Control ASPEED P2A VGA MMIO to BMC mappings through ioctl()s. The 53 Say yes to support decoding of ASPEED BMC information.
|
/linux-6.14.4/drivers/watchdog/ |
D | menf21bmc_wdt.c | 3 * MEN 14F021P00 Board Management Controller (BMC) Watchdog Driver. 80 * BMC Watchdog does have a resolution of 100ms. in menf21bmc_wdt_settimeout() 133 * Get the current wdt timeout value from the BMC because in menf21bmc_wdt_probe() 134 * the BMC will save the value set before if the system restarts. in menf21bmc_wdt_probe() 158 dev_info(dev, "MEN 14F021P00 BMC Watchdog device enabled\n"); in menf21bmc_wdt_probe() 181 MODULE_DESCRIPTION("MEN 14F021P00 BMC Watchdog driver");
|
/linux-6.14.4/include/linux/mfd/ |
D | intel-m10-bmc.h | 188 * struct m10bmc_csr_map - Intel MAX 10 BMC CSR register map 212 * struct intel_m10bmc_platform_info - Intel MAX 10 BMC platform specific information 217 * @csr_map: the mappings for register definition of MAX10 BMC 254 * struct intel_m10bmc - Intel MAX 10 BMC parent driver data structure 257 * @info: the platform information for MAX10 BMC 259 * @bmcfw_lock: read/write semaphore to BMC firmware running state 260 * @bmcfw_state: BMC firmware running state. Available only when 304 * MAX10 BMC Core support
|
/linux-6.14.4/Documentation/devicetree/bindings/spi/ |
D | nuvoton,npcm-fiu.txt | 14 - compatible : "nuvoton,npcm750-fiu" for Poleg NPCM7XX BMC 15 "nuvoton,npcm845-fiu" for Arbel NPCM8XX BMC 33 In the NPCM7XX BMC: 38 In the NPCM8XX BMC:
|