ARM: aspeed: add support for the BT IPMI interface
Subsystems (4)
v2 cover ARM: aspeed: add support for the BT IPMI interface
Hello,
This serie adds support for the iBT interface on Aspeed SOCs (AST2400 and AST2500). The BT (Block Transfer) interface is used to perform in-band IPMI communication between a host and its BMC. This driver implements the BMC side.
Most noticeable changes in v2 are:
- the driver is now called 'bt-bmc' and the device node '/dev/ipmi-bt-host'
- the code is now under drivers/char/ipmi/. This required a change of the top Makefile in drivers/ to compile the bt-bmc driver with the ipmi handlers not being selected. That might be an issue.
- changed the read/write operations to use a temporary buffer and get rid of the {get,put}_user calls
Thanks,
C.
Alistair Popple (1):
misc: Add Aspeed BT IPMI BMC driver
C?dric Le Goater (2):
ARM: aspeed: Add defconfigs for CONFIG_ASPEED_BT_IPMI_BMC
ARM: dts: aspeed: Enable BT IPMI BMC device
.../bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt | 23 + arch/arm/boot/dts/aspeed-g4.dtsi | 6 + arch/arm/boot/dts/aspeed-g5.dtsi | 6 + arch/arm/configs/aspeed_g4_defconfig | 1 + arch/arm/configs/aspeed_g5_defconfig | 1 + drivers/Makefile | 2 +- drivers/char/ipmi/Kconfig | 7 + drivers/char/ipmi/Makefile | 1 + drivers/char/ipmi/bt-bmc.c | 486 +++++++++++++++++++++ include/uapi/linux/Kbuild | 1 + include/uapi/linux/bt-bmc.h | 18 + 11 files changed, 551 insertions(+), 1 deletion(-) create mode 100644 Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt create mode 100644 drivers/char/ipmi/bt-bmc.c create mode 100644 include/uapi/linux/bt-bmc.h
Signature · 1 line
2.7.4
PATCH v2 1/3 ipmi: add an Aspeed BT IPMI BMC driver
From: Alistair Popple <[email protected]>
This patch adds a simple device driver to expose the iBT interface on Aspeed SOCs (AST2400 and AST2500) as a character device. Such SOCs are commonly used as BMCs (BaseBoard Management Controllers) and this driver implements the BMC side of the BT interface.
The BT (Block Transfer) interface is used to perform in-band IPMI communication between a host and its BMC. Entire messages are buffered before sending a notification to the other end, host or BMC, that there is data to be read. Usually, the host emits requests and the BMC responses but the specification provides a mean for the BMC to send SMS Attention (BMC-to-Host attention or System Management Software attention) messages.
For this purpose, the driver introduces a specific ioctl on the
device: 'BT_BMC_IOCTL_SMS_ATN' that can be used by the system running on the BMC to signal the host of such an event.
The device name defaults to '/dev/ipmi-bt-host'
[clg: - checkpatch fixes
- added a devicetree binding documentation
- replace 'bt_host' by 'bt_bmc' to reflect that the driver is the BMC side of the IPMI BT interface
- renamed the device to 'ipmi-bt-host'
- introduced a temporary buffer to copy_{to,from}_user
- used platform_get_irq()
- moved the driver under drivers/char/ipmi/ but kept it as a misc device
- changed the compatible cell to "aspeed,ast2400-bt-bmc"
]
---
Changes since v1:
- replace 'bt_host' by 'bt_bmc' to reflect that the driver is the BMC side of the IPMI BT interface
- renamed the device to 'ipmi-bt-host'
- introduced a temporary buffer to copy_{to,from}_user
- used platform_get_irq()
- moved the driver under drivers/char/ipmi/ but kept it as a misc device
- changed the compatible cell to "aspeed,ast2400-bt-bmc"
.../bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt | 23 + drivers/Makefile | 2 +- drivers/char/ipmi/Kconfig | 7 + drivers/char/ipmi/Makefile | 1 + drivers/char/ipmi/bt-bmc.c | 486 +++++++++++++++++++++ include/uapi/linux/Kbuild | 1 + include/uapi/linux/bt-bmc.h | 18 + 7 files changed, 537 insertions(+), 1 deletion(-) create mode 100644 Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt create mode 100644 drivers/char/ipmi/bt-bmc.c create mode 100644 include/uapi/linux/bt-bmc.h
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt new file +23 -0
@@ -0,0 +1,23 @@ +* Aspeed BT (Block Transfer) IPMI interface + +The Aspeed SOCs (AST2400 and AST2500) are commonly used as BMCs +(BaseBoard Management Controllers) and the BT interface can be used to +perform in-band IPMI communication with their host. + +Required properties: + +- compatible : should be "aspeed,ast2400-bt-bmc" +- reg: physical address and size of the registers + +Optional properties: + +- interrupts: interrupt generated by the BT interface. without an + interrupt, the driver will operate in poll mode. + +Example: + + ibt at 1e789140 { + compatible = "aspeed,ast2400-bt-bmc"; + reg = <0x1e789140 0x18>; + interrupts = <8>; + };
drivers/Makefile +1 -1
@@ -21,7 +21,7 @@ obj-y += video/ obj-y += idle/ # IPMI must come before ACPI in order to provide IPMI opregion support -obj-$(CONFIG_IPMI_HANDLER) += char/ipmi/ +obj-y += char/ipmi/ obj-$(CONFIG_ACPI) += acpi/ obj-$(CONFIG_SFI) += sfi/
drivers/char/ipmi/Kconfig +7 -0
@@ -76,3 +76,10 @@ config IPMI_POWEROFF the IPMI management controller is capable of this. endif # IPMI_HANDLER + +config ASPEED_BT_IPMI_BMC + tristate "BT IPMI bmc driver" + help + Provides a driver for the BT (Block Transfer) IPMI interface + found on Aspeed SOCs (AST2400 and AST2500). The driver + implements the BMC side of the BT interface.
drivers/char/ipmi/Makefile +1 -0
@@ -11,3 +11,4 @@ obj-$(CONFIG_IPMI_SSIF) += ipmi_ssif.o obj-$(CONFIG_IPMI_POWERNV) += ipmi_powernv.o obj-$(CONFIG_IPMI_WATCHDOG) += ipmi_watchdog.o obj-$(CONFIG_IPMI_POWEROFF) += ipmi_poweroff.o +obj-$(CONFIG_ASPEED_BT_IPMI_BMC) += bt-bmc.o
drivers/char/ipmi/bt-bmc.c new file +486 -0
486 lines not on this page · raw message
include/uapi/linux/Kbuild +1 -0
@@ -74,6 +74,7 @@ header-y += bpf_common.h header-y += bpf.h header-y += bpqether.h header-y += bsg.h +header-y += bt-bmc.h header-y += btrfs.h header-y += can.h header-y += capability.h
include/uapi/linux/bt-bmc.h new file +18 -0
@@ -0,0 +1,18 @@ +/* +* Copyright (c) 2015-2016, IBM Corporation. +* +* This program is free software; you can redistribute it and/or +* modify it under the terms of the GNU General Public License +* as published by the Free Software Foundation; either version +* 2 of the License, or (at your option) any later version. +*/ + +#ifndef _UAPI_LINUX_BT_BMC_H +#define _UAPI_LINUX_BT_BMC_H + +#include <linux/ioctl.h> + +#define __BT_BMC_IOCTL_MAGIC 0xb1 +#define BT_BMC_IOCTL_SMS_ATN _IO(__BT_BMC_IOCTL_MAGIC, 0x00) + +#endif /* _UAPI_LINUX_BT_BMC_H */
Signature · 1 line
2.7.4
PATCH v2 1/3 ipmi: add an Aspeed BT IPMI BMC driver
Quoted 19 lines · CEST C?dric Le Goater
From: Alistair Popple <[email protected]>
This patch adds a simple device driver to expose the iBT interface on Aspeed SOCs (AST2400 and AST2500) as a character device. Such SOCs are commonly used as BMCs (BaseBoard Management Controllers) and this driver implements the BMC side of the BT interface.
The BT (Block Transfer) interface is used to perform in-band IPMI communication between a host and its BMC. Entire messages are buffered before sending a notification to the other end, host or BMC, that there is data to be read. Usually, the host emits requests and the BMC responses but the specification provides a mean for the BMC to send SMS Attention (BMC-to-Host attention or System Management Software attention) messages.
For this purpose, the driver introduces a specific ioctl on the
device: 'BT_BMC_IOCTL_SMS_ATN' that can be used by the system running on the BMC to signal the host of such an event.
Quoted 6 lines
The device name defaults to '
/dev/ipmi-bt-host'Signed-off-by Alistair Popple <[email protected]>Signed-off-by Jeremy Kerr <[email protected]>Signed-off-by Joel Stanley <[email protected]>
PATCH v2 1/3 ipmi: add an Aspeed BT IPMI BMC driver
In reply to Cédric Le GoaterHello
I have some minor comment below:
Quoted 65 lines · C?dric Le Goater
From: Alistair Popple <[email protected]>
This patch adds a simple device driver to expose the iBT interface on Aspeed SOCs (AST2400 and AST2500) as a character device. Such SOCs are commonly used as BMCs (BaseBoard Management Controllers) and this driver implements the BMC side of the BT interface.
The BT (Block Transfer) interface is used to perform in-band IPMI communication between a host and its BMC. Entire messages are buffered before sending a notification to the other end, host or BMC, that there is data to be read. Usually, the host emits requests and the BMC responses but the specification provides a mean for the BMC to send SMS Attention (BMC-to-Host attention or System Management Software attention) messages.
For this purpose, the driver introduces a specific ioctl on the
device: 'BT_BMC_IOCTL_SMS_ATN' that can be used by the system running on the BMC to signal the host of such an event.The device name defaults to '
/dev/ipmi-bt-host'Signed-off-by Alistair Popple <[email protected]>Signed-off-by Jeremy Kerr <[email protected]>Signed-off-by Joel Stanley <[email protected]>[clg: - checkpatch fixes
- added a devicetree binding documentation
- replace 'bt_host' by 'bt_bmc' to reflect that the driver is the BMC side of the IPMI BT interface
- renamed the device to 'ipmi-bt-host'
- introduced a temporary buffer to copy_{to,from}_user
- usedplatform_get_irq()
- moved the driver underdrivers/char/ipmi/but kept it as a misc device
- changed the compatible cell to "aspeed,ast2400-bt-bmc"
]Signed-off-by C?dric Le Goater <[email protected]>---
Changes since v1:
- replace '
bt_host' by 'bt_bmc' to reflect that the driver is the BMC side of the IPMI BT interface
- renamed the device to 'ipmi-bt-host'
- introduced a temporary buffer to copy_{to,from}_user
- usedplatform_get_irq()
- moved the driver underdrivers/char/ipmi/but kept it as a misc device
- changed the compatible cell to "aspeed,ast2400-bt-bmc".../bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt | 23 + drivers/Makefile | 2 +- drivers/char/ipmi/Kconfig | 7 + drivers/char/ipmi/Makefile | 1 + drivers/char/ipmi/bt-bmc.c | 486 +++++++++++++++++++++ include/uapi/linux/Kbuild | 1 + include/uapi/linux/bt-bmc.h | 18 + 7 files changed, 537 insertions(+), 1 deletion(-) create mode 100644 Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt create mode 100644 drivers/char/ipmi/bt-bmc.c create mode 100644 include/uapi/linux/bt-bmc.hDocumentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt new file +0
-1--- /dev/null
[..]
Quoted 9 lines
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt new file +9
-0+#include <linux/module.h> +#include <linux/moduleparam.h> +#include <linux/errno.h> +#include <linux/poll.h> +#include <linux/sched.h> +#include <linux/spinlock.h> +#include <linux/slab.h> +#include <linux/init.h> +#include <linux/device.h>
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt
Quoted 10 lines
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt new file +10
-0+#include <linux/of.h> +#include <linux/of_irq.h> +#include <linux/platform_device.h> +#include <linux/io.h> +#include <linux/interrupt.h> +#include <linux/delay.h> +#include <linux/miscdevice.h> +#include <linux/timer.h> +#include <linux/jiffies.h> +#include <linux/bt-bmc.h>
Please sort them in alphabetical order, some of them seems not needed also (like spinlock.h)
Quoted 26 lines
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt new file +26
-0+ +/* + * This is a BMC device used to communicate to the host + */ +#define DEVICE_NAME "ipmi-bt-host" + +#define BT_IO_BASE 0xe4 +#define BT_IRQ 10 + +#define BT_CR0 0x0 +#define BT_CR0_IO_BASE 16 +#define BT_CR0_IRQ 12 +#define BT_CR0_EN_CLR_SLV_RDP 0x8 +#define BT_CR0_EN_CLR_SLV_WRP 0x4 +#define BT_CR0_ENABLE_IBT 0x1 +#define BT_CR1 0x4 +#define BT_CR1_IRQ_H2B 0x01 +#define BT_CR1_IRQ_HBUSY 0x40 +#define BT_CR2 0x8 +#define BT_CR2_IRQ_H2B 0x01 +#define BT_CR2_IRQ_HBUSY 0x40 +#define BT_CR3 0xc +#define BT_CTRL 0x10 +#define BT_CTRL_B_BUSY 0x80 +#define BT_CTRL_H_BUSY 0x40 +#define BT_CTRL_OEM0 0x20
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt
Quoted 10 lines
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt new file +10
-0+#define BT_CTRL_SMS_ATN 0x10 +#define BT_CTRL_B2H_ATN 0x08 +#define BT_CTRL_H2B_ATN 0x04 +#define BT_CTRL_CLR_RD_PTR 0x02 +#define BT_CTRL_CLR_WR_PTR 0x01 +#define BT_BMC2HOST 0x14 +#define BT_INTMASK 0x18 +#define BT_INTMASK_B2H_IRQEN 0x01 +#define BT_INTMASK_B2H_IRQ 0x02 +#define BT_INTMASK_BMC_HWRST 0x80
Why to use 3 space after some define ?
[..]
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt
Quoted 2 lines
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt new file +2
-0+ +#define BT_BMC_BUFFER_SIZE 256
Put this define with others
[..]
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt
Quoted 5 lines
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt new file +5
-0+ +static irqreturn_t bt_bmc_irq(int irq, void *arg) +{ + struct bt_bmc *bt_bmc = arg; + uint32_t reg;
u32 is prefered other uint32_t, do you have run checkpatch --strict ?
Quoted 27 lines
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt new file +27
-0+ + reg = ioread32(bt_bmc->base + BT_CR2); + reg &= BT_CR2_IRQ_H2B | BT_CR2_IRQ_HBUSY; + if (!reg) + return IRQ_NONE; + + /* ack pending IRQs */ + iowrite32(reg, bt_bmc->base + BT_CR2); + + wake_up(&bt_bmc->queue); + return IRQ_HANDLED; +} + +static int bt_bmc_config_irq(struct bt_bmc *bt_bmc, + struct platform_device *pdev) +{ + struct device *dev = &pdev->dev; + uint32_t reg; + int rc; + + bt_bmc->irq = platform_get_irq(pdev, 0); + if (!bt_bmc->irq) + return -ENODEV; + + rc = devm_request_irq(dev, bt_bmc->irq, bt_bmc_irq, IRQF_SHARED, + DEVICE_NAME, bt_bmc); + if (rc < 0) {
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt
Quoted 10 lines
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt new file +10
-0+ dev_warn(dev, "Unable to request IRQ %d\n", bt_bmc->irq); + bt_bmc->irq = 0; + return rc; + } + + /* Configure IRQs on the bmc clearing the H2B and HBUSY bits; + * H2B will be asserted when the bmc has data for us; HBUSY + * will be cleared (along with B2H) when we can write the next + * message to the BT buffer + */
This comment doesnt have the style recommended for new driver.
Quoted 38 lines
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt new file +38
-0+ reg = ioread32(bt_bmc->base + BT_CR1); + reg |= BT_CR1_IRQ_H2B | BT_CR1_IRQ_HBUSY; + iowrite32(reg, bt_bmc->base + BT_CR1); + + return 0; +} + +static int bt_bmc_probe(struct platform_device *pdev) +{ + struct bt_bmc *bt_bmc; + struct device *dev; + struct resource *res; + int rc; + + if (!pdev || !pdev->dev.of_node) + return -ENODEV; + + dev = &pdev->dev; + dev_info(dev, "Found bt bmc device\n"); + + bt_bmc = devm_kzalloc(dev, sizeof(*bt_bmc), GFP_KERNEL); + if (!bt_bmc) + return -ENOMEM; + + dev_set_drvdata(&pdev->dev, bt_bmc); + + res = platform_get_resource(pdev, IORESOURCE_MEM, 0); + if (!res) { + dev_err(dev, "Unable to find resources\n"); + rc = -ENXIO; + goto out_free; + } + + bt_bmc->base = devm_ioremap_resource(&pdev->dev, res); + if (!bt_bmc->base) { + rc = -ENOMEM; + goto out_free; + }
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt
Quoted 10 lines
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt new file +10
-0+ + init_waitqueue_head(&bt_bmc->queue); + + bt_bmc->miscdev.minor = MISC_DYNAMIC_MINOR, + bt_bmc->miscdev.name = DEVICE_NAME, + bt_bmc->miscdev.fops = &bt_bmc_fops, + bt_bmc->miscdev.parent = dev; + rc = misc_register(&bt_bmc->miscdev); + if (rc) { + dev_err(dev, "Unable to register device\n");
Be more precise by saying misc device
Quoted 18 lines
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt new file +18
-0+ goto out_unmap; + } + + bt_bmc_config_irq(bt_bmc, pdev); + + if (bt_bmc->irq) { + dev_info(dev, "Using IRQ %d\n", bt_bmc->irq); + } else { + dev_info(dev, "No IRQ; using timer\n"); + setup_timer(&bt_bmc->poll_timer, poll_timer, + (unsigned long)bt_bmc); + bt_bmc->poll_timer.expires = jiffies + msecs_to_jiffies(10); + add_timer(&bt_bmc->poll_timer); + } + + iowrite32((BT_IO_BASE << BT_CR0_IO_BASE) | + (BT_IRQ << BT_CR0_IRQ) | + BT_CR0_EN_CLR_SLV_RDP |
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt
Quoted 10 lines
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt new file +10
-0+ BT_CR0_EN_CLR_SLV_WRP | + BT_CR0_ENABLE_IBT, + bt_bmc->base + BT_CR0); + + clr_b_busy(bt_bmc); + + return 0; + +out_unmap: + devm_iounmap(&pdev->dev, bt_bmc->base);
Why do you use devm_iounmap/devm_kfree since the interest with devm_ functions is that all cleanup is done when driver is removed.
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt
Quoted 4 lines
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt new file +4
-0+ +out_free: + devm_kfree(dev, bt_bmc); + return rc;
I think you should remove the space after this return
Regards
Corentin Labbe
PATCH v2 1/3 ipmi: add an Aspeed BT IPMI BMC driver
Quoted 86 lines · LABBE Corentin
Hello
I have some minor comment below:
Quoted 65 lines · C?dric Le Goater
From: Alistair Popple <[email protected]>
This patch adds a simple device driver to expose the iBT interface on Aspeed SOCs (AST2400 and AST2500) as a character device. Such SOCs are commonly used as BMCs (BaseBoard Management Controllers) and this driver implements the BMC side of the BT interface.
The BT (Block Transfer) interface is used to perform in-band IPMI communication between a host and its BMC. Entire messages are buffered before sending a notification to the other end, host or BMC, that there is data to be read. Usually, the host emits requests and the BMC responses but the specification provides a mean for the BMC to send SMS Attention (BMC-to-Host attention or System Management Software attention) messages.
For this purpose, the driver introduces a specific ioctl on the
device: 'BT_BMC_IOCTL_SMS_ATN' that can be used by the system running on the BMC to signal the host of such an event.The device name defaults to '
/dev/ipmi-bt-host'Signed-off-by Alistair Popple <[email protected]>Signed-off-by Jeremy Kerr <[email protected]>Signed-off-by Joel Stanley <[email protected]>[clg: - checkpatch fixes
- added a devicetree binding documentation
- replace 'bt_host' by 'bt_bmc' to reflect that the driver is the BMC side of the IPMI BT interface
- renamed the device to 'ipmi-bt-host'
- introduced a temporary buffer to copy_{to,from}_user
- usedplatform_get_irq()
- moved the driver underdrivers/char/ipmi/but kept it as a misc device
- changed the compatible cell to "aspeed,ast2400-bt-bmc"
]Signed-off-by C?dric Le Goater <[email protected]>---
Changes since v1:
- replace '
bt_host' by 'bt_bmc' to reflect that the driver is the BMC side of the IPMI BT interface
- renamed the device to 'ipmi-bt-host'
- introduced a temporary buffer to copy_{to,from}_user
- usedplatform_get_irq()
- moved the driver underdrivers/char/ipmi/but kept it as a misc device
- changed the compatible cell to "aspeed,ast2400-bt-bmc".../bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt | 23 + drivers/Makefile | 2 +- drivers/char/ipmi/Kconfig | 7 + drivers/char/ipmi/Makefile | 1 + drivers/char/ipmi/bt-bmc.c | 486 +++++++++++++++++++++ include/uapi/linux/Kbuild | 1 + include/uapi/linux/bt-bmc.h | 18 + 7 files changed, 537 insertions(+), 1 deletion(-) create mode 100644 Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt create mode 100644 drivers/char/ipmi/bt-bmc.c create mode 100644 include/uapi/linux/bt-bmc.hDocumentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt new file +0
-1--- /dev/null[..]
Quoted 13 lines
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt new file +13
-0+#include <linux/module.h> +#include <linux/moduleparam.h> +#include <linux/errno.h> +#include <linux/poll.h> +#include <linux/sched.h> +#include <linux/spinlock.h> +#include <linux/slab.h> +#include <linux/init.h> +#include <linux/device.h> +#include <linux/of.h> +#include <linux/of_irq.h> +#include <linux/platform_device.h> +#include <linux/io.h>
Quoted 8 lines
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt
Quoted 6 lines
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt new file +6
-0+#include <linux/interrupt.h> +#include <linux/delay.h> +#include <linux/miscdevice.h> +#include <linux/timer.h> +#include <linux/jiffies.h> +#include <linux/bt-bmc.h>Please sort them in alphabetical order, some of them seems not needed also (like
spinlock.h)
sure. I will clean them up.
Quoted 30 lines
Quoted 30 lines
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt new file +30
-0+ +/* + * This is a BMC device used to communicate to the host + */ +#define DEVICE_NAME "ipmi-bt-host" + +#define BT_IO_BASE 0xe4 +#define BT_IRQ 10 + +#define BT_CR0 0x0 +#define BT_CR0_IO_BASE 16 +#define BT_CR0_IRQ 12 +#define BT_CR0_EN_CLR_SLV_RDP 0x8 +#define BT_CR0_EN_CLR_SLV_WRP 0x4 +#define BT_CR0_ENABLE_IBT 0x1 +#define BT_CR1 0x4 +#define BT_CR1_IRQ_H2B 0x01 +#define BT_CR1_IRQ_HBUSY 0x40 +#define BT_CR2 0x8 +#define BT_CR2_IRQ_H2B 0x01 +#define BT_CR2_IRQ_HBUSY 0x40 +#define BT_CR3 0xc +#define BT_CTRL 0x10 +#define BT_CTRL_B_BUSY 0x80 +#define BT_CTRL_H_BUSY 0x40 +#define BT_CTRL_OEM0 0x20 +#define BT_CTRL_SMS_ATN 0x10 +#define BT_CTRL_B2H_ATN 0x08 +#define BT_CTRL_H2B_ATN 0x04 +#define BT_CTRL_CLR_RD_PTR 0x02
Quoted 8 lines
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt
Quoted 6 lines
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt new file +6
-0+#define BT_CTRL_CLR_WR_PTR 0x01 +#define BT_BMC2HOST 0x14 +#define BT_INTMASK 0x18 +#define BT_INTMASK_B2H_IRQEN 0x01 +#define BT_INTMASK_B2H_IRQ 0x02 +#define BT_INTMASK_BMC_HWRST 0x80Why to use 3 space after some define ?
The difference in alignment is to distinguish the register number from the bits signification. Is that OK ?
Quoted 8 lines
[..]
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt
Quoted 2 lines
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt new file +2
-0+ +#define BT_BMC_BUFFER_SIZE 256Put this define with others
[..]
ok
Quoted 7 lines
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt
Quoted 5 lines
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt new file +5
-0+ +static irqreturn_t bt_bmc_irq(int irq, void *arg) +{ + struct bt_bmc *bt_bmc = arg; + uint32_t reg;u32 is prefered other
uint32_t, do you have run checkpatch --strict ?
no. I just did and I see it is catching quite a few new issues. I will send a v3 with fixes.
Quoted 31 lines
Quoted 31 lines
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt new file +31
-0+ + reg = ioread32(bt_bmc->base + BT_CR2); + reg &= BT_CR2_IRQ_H2B | BT_CR2_IRQ_HBUSY; + if (!reg) + return IRQ_NONE; + + /* ack pending IRQs */ + iowrite32(reg, bt_bmc->base + BT_CR2); + + wake_up(&bt_bmc->queue); + return IRQ_HANDLED; +} + +static int bt_bmc_config_irq(struct bt_bmc *bt_bmc, + struct platform_device *pdev) +{ + struct device *dev = &pdev->dev; + uint32_t reg; + int rc; + + bt_bmc->irq = platform_get_irq(pdev, 0); + if (!bt_bmc->irq) + return -ENODEV; + + rc = devm_request_irq(dev, bt_bmc->irq, bt_bmc_irq, IRQF_SHARED, + DEVICE_NAME, bt_bmc); + if (rc < 0) { + dev_warn(dev, "Unable to request IRQ %d\n", bt_bmc->irq); + bt_bmc->irq = 0; + return rc; + }
Quoted 8 lines
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt
Quoted 6 lines
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt new file +6
-0+ + /* Configure IRQs on the bmc clearing the H2B and HBUSY bits; + * H2B will be asserted when the bmc has data for us; HBUSY + * will be cleared (along with B2H) when we can write the next + * message to the BT buffer + */This comment doesnt have the style recommended for new driver.
ah yes. I missed that one.
Quoted 42 lines
Quoted 42 lines
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt new file +42
-0+ reg = ioread32(bt_bmc->base + BT_CR1); + reg |= BT_CR1_IRQ_H2B | BT_CR1_IRQ_HBUSY; + iowrite32(reg, bt_bmc->base + BT_CR1); + + return 0; +} + +static int bt_bmc_probe(struct platform_device *pdev) +{ + struct bt_bmc *bt_bmc; + struct device *dev; + struct resource *res; + int rc; + + if (!pdev || !pdev->dev.of_node) + return -ENODEV; + + dev = &pdev->dev; + dev_info(dev, "Found bt bmc device\n"); + + bt_bmc = devm_kzalloc(dev, sizeof(*bt_bmc), GFP_KERNEL); + if (!bt_bmc) + return -ENOMEM; + + dev_set_drvdata(&pdev->dev, bt_bmc); + + res = platform_get_resource(pdev, IORESOURCE_MEM, 0); + if (!res) { + dev_err(dev, "Unable to find resources\n"); + rc = -ENXIO; + goto out_free; + } + + bt_bmc->base = devm_ioremap_resource(&pdev->dev, res); + if (!bt_bmc->base) { + rc = -ENOMEM; + goto out_free; + } + + init_waitqueue_head(&bt_bmc->queue); + + bt_bmc->miscdev.minor = MISC_DYNAMIC_MINOR,
Quoted 8 lines
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt
Quoted 6 lines
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt new file +6
-0+ bt_bmc->miscdev.name = DEVICE_NAME, + bt_bmc->miscdev.fops = &bt_bmc_fops, + bt_bmc->miscdev.parent = dev; + rc = misc_register(&bt_bmc->miscdev); + if (rc) { + dev_err(dev, "Unable to register device\n");Be more precise by saying misc device
ok
Quoted 24 lines
Quoted 24 lines
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt new file +23
-0+ goto out_unmap; + } + + bt_bmc_config_irq(bt_bmc, pdev); + + if (bt_bmc->irq) { + dev_info(dev, "Using IRQ %d\n", bt_bmc->irq); + } else { + dev_info(dev, "No IRQ; using timer\n"); + setup_timer(&bt_bmc->poll_timer, poll_timer, + (unsigned long)bt_bmc); + bt_bmc->poll_timer.expires = jiffies + msecs_to_jiffies(10); + add_timer(&bt_bmc->poll_timer); + } + + iowrite32((BT_IO_BASE << BT_CR0_IO_BASE) | + (BT_IRQ << BT_CR0_IRQ) | + BT_CR0_EN_CLR_SLV_RDP | + BT_CR0_EN_CLR_SLV_WRP | + BT_CR0_ENABLE_IBT, + bt_bmc->base + BT_CR0); + + clr_b_busy(bt_bmc);
Quoted 8 lines
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt
Quoted 5 lines
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt new file +5
-0+ + return 0; + +out_unmap: + devm_iounmap(&pdev->dev, bt_bmc->base);Why do you use devm_iounmap/devm_kfree since the interest with
devm_functions is that all cleanup is done when driver is removed.
Indeed. So I can cleanup bt_bmc_remove() also.
Quoted 6 lines
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt
Quoted 4 lines
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt new file +4
-0+ +out_free: + devm_kfree(dev, bt_bmc); + return rc;I think you should remove the space after this return
Thanks,
C.
Quoted 4 lines
Regards
Corentin Labbe
PATCH v2 1/3 ipmi: add an Aspeed BT IPMI BMC driver
In reply to Cédric Le GoaterQuoted 15 lines · C?dric Le Goater
From: Alistair Popple <[email protected]>
This patch adds a simple device driver to expose the iBT interface on Aspeed SOCs (AST2400 and AST2500) as a character device. Such SOCs are commonly used as BMCs (BaseBoard Management Controllers) and this driver implements the BMC side of the BT interface.
The BT (Block Transfer) interface is used to perform in-band IPMI communication between a host and its BMC. Entire messages are buffered before sending a notification to the other end, host or BMC, that there is data to be read. Usually, the host emits requests and the BMC responses but the specification provides a mean for the BMC to send SMS Attention (BMC-to-Host attention or System Management Software attention) messages.
Quoted 5 lines
For this purpose, the driver introduces a specific ioctl on the
device: 'BT_BMC_IOCTL_SMS_ATN' that can be used by the system running on the BMC to signal the host of such an event.The device name defaults to '
/dev/ipmi-bt-host'
Others have reviewed this for style and such, and I have looked at it from a protocol point of view. it looks to be sound for the most part. I have some higher level concerns:
There appears to be no handling for multiple simultaneous users. This interface can only be used by one task at a time, so you should probably only allow one opener. Well, I guess the BMC could be split into a reader and a writer task, so I'm not really sure about that, but I would think in most situations having more than one opener is a bug. You do call clr_b_busy() on open, for instance, which might be an issue for multiple openers. Maybe a module parameter for maximum number of openers? Just want to make sure this was thought about, at least.
There is also no mutex protecting reading or writing. If multiple threads call read or write at the same time, it probably wouldn't work correctly. I think you need a read and a write mutex on the interface to protect against this.
The spec says:
The BMC must not return a given response once the corresponding Request-to-Response interval has passed. The BMC can ensure this by maintaining its own internal list of outstanding requests through the interface. The BMC could age and expire the entries in the list by expiring the entries at an interval that is somewhat shorter than the specified Request-to-Response interval....
On the write side, though, there doesn't seem to be a way to handle a situation where the host side doesn't respond for a while and the pending message would need to be discarded.
The spec doesn't mention much about error recovery on this interface, but the way this is written should be fine, I think.
I'm copying Rocky Craig, who wrote the host side driver for Linux, in case he wants to comment on this.
This is easy to read and understand, so I think v3 should be good.
Thanks,
-corey
Quoted 634 lines
Signed-off-by Alistair Popple <[email protected]>Signed-off-by Jeremy Kerr <[email protected]>Signed-off-by Joel Stanley <[email protected]>[clg: - checkpatch fixes
- added a devicetree binding documentation
- replace 'bt_host' by 'bt_bmc' to reflect that the driver is the BMC side of the IPMI BT interface
- renamed the device to 'ipmi-bt-host'
- introduced a temporary buffer to copy_{to,from}_user
- usedplatform_get_irq()
- moved the driver underdrivers/char/ipmi/but kept it as a misc device
- changed the compatible cell to "aspeed,ast2400-bt-bmc"
]Signed-off-by C?dric Le Goater <[email protected]>---
Changes since v1:
- replace '
bt_host' by 'bt_bmc' to reflect that the driver is the BMC side of the IPMI BT interface
- renamed the device to 'ipmi-bt-host'
- introduced a temporary buffer to copy_{to,from}_user
- usedplatform_get_irq()
- moved the driver underdrivers/char/ipmi/but kept it as a misc device
- changed the compatible cell to "aspeed,ast2400-bt-bmc".../bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt | 23 + drivers/Makefile | 2 +- drivers/char/ipmi/Kconfig | 7 + drivers/char/ipmi/Makefile | 1 + drivers/char/ipmi/bt-bmc.c | 486 +++++++++++++++++++++ include/uapi/linux/Kbuild | 1 + include/uapi/linux/bt-bmc.h | 18 + 7 files changed, 537 insertions(+), 1 deletion(-)create mode 100644
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txtcreate mode 100644drivers/char/ipmi/bt-bmc.c
create mode 100644include/uapi/linux/bt-bmc.hDocumentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt new file +23
-0@@ -0,0 +1,23 @@ +* Aspeed BT (Block Transfer) IPMI interface + +The Aspeed SOCs (AST2400 and AST2500) are commonly used as BMCs +(BaseBoard Management Controllers) and the BT interface can be used to +perform in-band IPMI communication with their host. + +Required properties: + +- compatible : should be "aspeed,ast2400-bt-bmc" +- reg: physical address and size of the registers + +Optional properties: + +- interrupts: interrupt generated by the BT interface. without an + interrupt, the driver will operate in poll mode. + +Example: + + ibt at 1e789140 { + compatible = "aspeed,ast2400-bt-bmc"; + reg = <0x1e789140 0x18>; + interrupts = <8>; + };drivers/Makefile +1
-1@@ -21,7 +21,7 @@ obj-y += video/ obj-y += idle/ # IPMI must come before ACPI in order to provide IPMI opregion support -obj-$(CONFIG_IPMI_HANDLER) += char/ipmi/ +obj-y += char/ipmi/ obj-$(CONFIG_ACPI) += acpi/ obj-$(CONFIG_SFI) += sfi/drivers/char/ipmi/Kconfig +7
-0@@ -76,3 +76,10 @@ config IPMI_POWEROFF the IPMI management controller is capable of this. endif # IPMI_HANDLER + +config ASPEED_BT_IPMI_BMC + tristate "BT IPMI bmc driver" + help + Provides a driver for the BT (Block Transfer) IPMI interface + found on Aspeed SOCs (AST2400 and AST2500). The driver + implements the BMC side of the BT interface.drivers/char/ipmi/Makefile +1
-0@@ -11,3 +11,4 @@ obj-$(CONFIG_IPMI_SSIF) += ipmi_ssif.o obj-$(CONFIG_IPMI_POWERNV) += ipmi_powernv.o obj-$(CONFIG_IPMI_WATCHDOG) += ipmi_watchdog.o obj-$(CONFIG_IPMI_POWEROFF) += ipmi_poweroff.o +obj-$(CONFIG_ASPEED_BT_IPMI_BMC) += bt-bmc.odrivers/char/ipmi/bt-bmc.c new file +486
-0@@ -0,0 +1,486 @@ +/* +* Copyright (c) 2015-2016, IBM Corporation. +* +* This program is free software; you can redistribute it and/or +* modify it under the terms of the GNU General Public License +* as published by the Free Software Foundation; either version +* 2 of the License, or (at your option) any later version. +*/ + +#include <linux/module.h> +#include <linux/moduleparam.h> +#include <linux/errno.h> +#include <linux/poll.h> +#include <linux/sched.h> +#include <linux/spinlock.h> +#include <linux/slab.h> +#include <linux/init.h> +#include <linux/device.h> +#include <linux/of.h> +#include <linux/of_irq.h> +#include <linux/platform_device.h> +#include <linux/io.h> +#include <linux/interrupt.h> +#include <linux/delay.h> +#include <linux/miscdevice.h> +#include <linux/timer.h> +#include <linux/jiffies.h> +#include <linux/bt-bmc.h> + +/* +* This is a BMC device used to communicate to the host +*/ +#define DEVICE_NAME "ipmi-bt-host" + +#define BT_IO_BASE 0xe4 +#define BT_IRQ 10 + +#define BT_CR0 0x0 +#define BT_CR0_IO_BASE 16 +#define BT_CR0_IRQ 12 +#define BT_CR0_EN_CLR_SLV_RDP 0x8 +#define BT_CR0_EN_CLR_SLV_WRP 0x4 +#define BT_CR0_ENABLE_IBT 0x1 +#define BT_CR1 0x4 +#define BT_CR1_IRQ_H2B 0x01 +#define BT_CR1_IRQ_HBUSY 0x40 +#define BT_CR2 0x8 +#define BT_CR2_IRQ_H2B 0x01 +#define BT_CR2_IRQ_HBUSY 0x40 +#define BT_CR3 0xc +#define BT_CTRL 0x10 +#define BT_CTRL_B_BUSY 0x80 +#define BT_CTRL_H_BUSY 0x40 +#define BT_CTRL_OEM0 0x20 +#define BT_CTRL_SMS_ATN 0x10 +#define BT_CTRL_B2H_ATN 0x08 +#define BT_CTRL_H2B_ATN 0x04 +#define BT_CTRL_CLR_RD_PTR 0x02 +#define BT_CTRL_CLR_WR_PTR 0x01 +#define BT_BMC2HOST 0x14 +#define BT_INTMASK 0x18 +#define BT_INTMASK_B2H_IRQEN 0x01 +#define BT_INTMASK_B2H_IRQ 0x02 +#define BT_INTMASK_BMC_HWRST 0x80 + +struct bt_bmc { +struct device dev; +struct miscdevice miscdev; +void __iomem *base; +int open_count; +int irq; +wait_queue_head_t queue; +struct timer_list poll_timer; +}; + +static u8 bt_inb (struct bt_bmc *bt_bmc,int reg) +{ +return ioread8 (bt_bmc->base + reg); +} + +static void bt_outb (struct bt_bmc *bt_bmc,u8 data,int reg) +{ +iowrite8 (data, bt_bmc->base + reg); +} + +static void clr_rd_ptr (struct bt_bmc *bt_bmc) +{ +bt_outb (bt_bmc,BT_CTRL_CLR_RD_PTR ,BT_CTRL ); +} + +static void clr_wr_ptr (struct bt_bmc *bt_bmc) +{ +bt_outb (bt_bmc,BT_CTRL_CLR_WR_PTR ,BT_CTRL ); +} + +static void clr_h2b_atn (struct bt_bmc *bt_bmc) +{ +bt_outb (bt_bmc,BT_CTRL_H2B_ATN ,BT_CTRL ); +} + +static void set_b_busy (struct bt_bmc *bt_bmc) +{ +if (!(bt_inb (bt_bmc,BT_CTRL ) &BT_CTRL_B_BUSY )) +bt_outb (bt_bmc,BT_CTRL_B_BUSY ,BT_CTRL ); +} + +static void clr_b_busy (struct bt_bmc *bt_bmc) +{ +if (bt_inb (bt_bmc,BT_CTRL ) &BT_CTRL_B_BUSY ) +bt_outb (bt_bmc,BT_CTRL_B_BUSY ,BT_CTRL ); +} + +static void set_b2h_atn (struct bt_bmc *bt_bmc) +{ +bt_outb (bt_bmc,BT_CTRL_B2H_ATN ,BT_CTRL ); +} + +static u8 bt_read (struct bt_bmc *bt_bmc) +{ +return bt_inb (bt_bmc,BT_BMC2HOST ); +} + +static ssize_t bt_readn (struct bt_bmc *bt_bmc,u8 *buf,size_t n) +{ +int i; + +for (i =0 ; i < n; i++) + buf[i] =bt_read (bt_bmc); +return n; +} + +static void bt_write (struct bt_bmc *bt_bmc,u8 c) +{ +bt_outb (bt_bmc, c,BT_BMC2HOST ); +} + +static ssize_t bt_writen (struct bt_bmc *bt_bmc,u8 *buf,size_t n) +{ +int i; + +for (i =0 ; i < n; i++) +bt_write (bt_bmc, buf[i]); +return n; +} + +static void set_sms_atn (struct bt_bmc *bt_bmc) +{ +bt_outb (bt_bmc,BT_CTRL_SMS_ATN ,BT_CTRL ); +} + +static struct bt_bmc *file_bt_bmc (struct file *file) +{ + return container_of(file->private_data, struct bt_bmc, miscdev); +} + +static int bt_bmc_open (struct inode *inode,struct file *file) +{ +struct bt_bmc *bt_bmc =file_bt_bmc (file); + +clr_b_busy (bt_bmc); + +return 0 ; +} + +#define BT_BMC_BUFFER_SIZE 256 + +/* +* The BT (Block Transfer) interface means that entire messages are +* buffered by the host before a notification is sent to the BMC that +* there is data to be read. The first byte is the length and the +* message data follows. The read operation just tries to capture the +* whole before returning it to userspace. +*/ +static ssize_t bt_bmc_read (struct file *file,char __user *buf, +size_t count,loff_t *ppos) +{ +struct bt_bmc *bt_bmc =file_bt_bmc (file); +u8 len; +int len_byte =1 ; +u8 kbuffer[BT_BMC_BUFFER_SIZE ]; +ssize_t ret =0 ; +ssize_t nread; + +if (!access_ok (VERIFY_WRITE , buf, count)) +return -EFAULT ; + +WARN_ON (*ppos); + +if (wait_event_interruptible (bt_bmc->queue, +bt_inb (bt_bmc,BT_CTRL ) &BT_CTRL_H2B_ATN )) +return -ERESTARTSYS ; + +set_b_busy (bt_bmc); +clr_h2b_atn (bt_bmc); +clr_rd_ptr (bt_bmc); + +/* +* The BT frames start with the message length, which does not +* include the length byte. +*/ + kbuffer[0 ] =bt_read (bt_bmc); + len = kbuffer[0 ]; + +/* We pass the length back to userspace as well */ +if (len +1 > count) + len = count -1 ; + +while (len) { + nread =min_t (ssize_t, len,sizeof (kbuffer) - len_byte); + +bt_readn (bt_bmc, kbuffer + len_byte, nread); + +if (copy_to_user (buf, kbuffer, nread + len_byte)) { + ret = -EFAULT ; +break ; + } + len -= nread; + buf += nread + len_byte; + ret += nread + len_byte; + len_byte =0 ; + } + +clr_b_busy (bt_bmc); + +return ret; +} + +static ssize_t bt_bmc_write (struct file *file,const char __user *buf, +size_t count,loff_t *ppos) +{ +struct bt_bmc *bt_bmc =file_bt_bmc (file); +u8 kbuffer[BT_BMC_BUFFER_SIZE ]; +ssize_t ret =0 ; +ssize_t nwritten; + +if (!access_ok (VERIFY_READ , buf, count)) +return -EFAULT ; + +WARN_ON (*ppos); + +/* There's no interrupt for clearing bmc busy so we have to +* poll +*/ +if (wait_event_interruptible (bt_bmc->queue, + !(bt_inb (bt_bmc,BT_CTRL ) & + (BT_CTRL_H_BUSY |BT_CTRL_B2H_ATN )))) +return -ERESTARTSYS ; + +clr_wr_ptr (bt_bmc); + +while (count) { + nwritten =min_t (ssize_t, count,sizeof (kbuffer)); +if (copy_from_user (&kbuffer, buf, nwritten)) { + ret = -EFAULT ; +break ; + } + +bt_writen (bt_bmc, kbuffer, nwritten); + + count -= nwritten; + buf += nwritten; + ret += nwritten; + } + +set_b2h_atn (bt_bmc); + +return ret; +} + +static long bt_bmc_ioctl (struct file *file,unsigned int cmd, +unsigned long param) +{ +struct bt_bmc *bt_bmc =file_bt_bmc (file); + +switch (cmd) { +case BT_BMC_IOCTL_SMS_ATN : +set_sms_atn (bt_bmc); +return 0 ; + } +return -EINVAL ; +} + +static int bt_bmc_release (struct inode *inode,struct file *file) +{ +struct bt_bmc *bt_bmc =file_bt_bmc (file); + +set_b_busy (bt_bmc); +return 0 ; +} + +static unsigned int bt_bmc_poll (struct file *file,poll_table *wait) +{ +struct bt_bmc *bt_bmc =file_bt_bmc (file); +unsigned int mask =0 ; +uint8_t ctrl; + +poll_wait (file, &bt_bmc->queue, wait); + + ctrl =bt_inb (bt_bmc,BT_CTRL ); + +if (ctrl &BT_CTRL_H2B_ATN ) + mask |=POLLIN ; + +if (!(ctrl & (BT_CTRL_H_BUSY |BT_CTRL_B2H_ATN ))) + mask |=POLLOUT ; + +return mask; +} + +static const struct file_operations bt_bmc_fops = { + .owner =THIS_MODULE , + .open = bt_bmc_open, + .read = bt_bmc_read, + .write = bt_bmc_write, + .release = bt_bmc_release, + .poll = bt_bmc_poll, + .unlocked_ioctl = bt_bmc_ioctl, +}; + +static void poll_timer (unsigned long data) +{ +struct bt_bmc *bt_bmc = (void *)data; + + bt_bmc->poll_timer.expires +=msecs_to_jiffies (500 ); +wake_up (&bt_bmc->queue); +add_timer (&bt_bmc->poll_timer); +} + +static irqreturn_t bt_bmc_irq (int irq,void *arg) +{ +struct bt_bmc *bt_bmc = arg; +uint32_t reg; + + reg =ioread32 (bt_bmc->base +BT_CR2 ); + reg &=BT_CR2_IRQ_H2B |BT_CR2_IRQ_HBUSY ; +if (!reg) +return IRQ_NONE ; + +/* ack pending IRQs */ +iowrite32 (reg, bt_bmc->base +BT_CR2 ); + +wake_up (&bt_bmc->queue); +return IRQ_HANDLED ; +} + +static int bt_bmc_config_irq (struct bt_bmc *bt_bmc, +struct platform_device *pdev) +{ +struct device *dev = &pdev->dev; +uint32_t reg; +int rc; + + bt_bmc->irq =platform_get_irq (pdev,0 ); +if (!bt_bmc->irq) +return -ENODEV ; + + rc =devm_request_irq (dev, bt_bmc->irq, bt_bmc_irq,IRQF_SHARED , +DEVICE_NAME , bt_bmc); +if (rc <0 ) { +dev_warn (dev,"Unable to request IRQ %d\n" , bt_bmc->irq); + bt_bmc->irq =0 ; +return rc; + } + +/* Configure IRQs on the bmc clearing the H2B and HBUSY bits; +* H2B will be asserted when the bmc has data for us; HBUSY +* will be cleared (along with B2H) when we can write the next +* message to the BT buffer +*/ + reg =ioread32 (bt_bmc->base +BT_CR1 ); + reg |=BT_CR1_IRQ_H2B |BT_CR1_IRQ_HBUSY ; +iowrite32 (reg, bt_bmc->base +BT_CR1 ); + +return 0 ; +} + +static int bt_bmc_probe (struct platform_device *pdev) +{ +struct bt_bmc *bt_bmc; +struct device *dev; +struct resource *res; +int rc; + +if (!pdev || !pdev->dev.of_node) +return -ENODEV ; + + dev = &pdev->dev; +dev_info (dev,"Found bt bmc device\n" ); + + bt_bmc =devm_kzalloc (dev,sizeof (*bt_bmc),GFP_KERNEL ); +if (!bt_bmc) +return -ENOMEM ; + +dev_set_drvdata (&pdev->dev, bt_bmc); + + res =platform_get_resource (pdev,IORESOURCE_MEM ,0 ); +if (!res) { +dev_err (dev,"Unable to find resources\n" ); + rc = -ENXIO ; + goto out_free; + } + + bt_bmc->base =devm_ioremap_resource (&pdev->dev, res); +if (!bt_bmc->base) { + rc = -ENOMEM ; + goto out_free; + } + +init_waitqueue_head (&bt_bmc->queue); + + bt_bmc->miscdev.minor =MISC_DYNAMIC_MINOR , + bt_bmc->miscdev.name =DEVICE_NAME , + bt_bmc->miscdev.fops = &bt_bmc_fops, + bt_bmc->miscdev.parent = dev; + rc =misc_register (&bt_bmc->miscdev); +if (rc) { +dev_err (dev,"Unable to register device\n" ); + goto out_unmap; + } + +bt_bmc_config_irq (bt_bmc, pdev); + +if (bt_bmc->irq) { +dev_info (dev,"Using IRQ %d\n" , bt_bmc->irq); + }else { +dev_info (dev,"No IRQ; using timer\n" ); +setup_timer (&bt_bmc->poll_timer, poll_timer, + (unsigned long )bt_bmc); + bt_bmc->poll_timer.expires = jiffies +msecs_to_jiffies (10 ); +add_timer (&bt_bmc->poll_timer); + } + +iowrite32 ((BT_IO_BASE <<BT_CR0_IO_BASE ) | + (BT_IRQ <<BT_CR0_IRQ ) | +BT_CR0_EN_CLR_SLV_RDP | +BT_CR0_EN_CLR_SLV_WRP | +BT_CR0_ENABLE_IBT , + bt_bmc->base +BT_CR0 ); + +clr_b_busy (bt_bmc); + +return 0 ; + +out_unmap: +devm_iounmap (&pdev->dev, bt_bmc->base); + +out_free: +devm_kfree (dev, bt_bmc); +return rc; + +} + +static int bt_bmc_remove (struct platform_device *pdev) +{ +struct bt_bmc *bt_bmc =dev_get_drvdata (&pdev->dev); + +misc_deregister (&bt_bmc->miscdev); +if (!bt_bmc->irq) +del_timer_sync (&bt_bmc->poll_timer); +devm_iounmap (&pdev->dev, bt_bmc->base); +devm_kfree (&pdev->dev, bt_bmc); + bt_bmc =NULL ; + +return 0 ; +} + +static const struct of_device_id bt_bmc_match[] = { + { .compatible ="aspeed,ast2400-bt-bmc" }, + { }, +}; + +static struct platform_driver bt_bmc_driver = { + .driver = { + .name =DEVICE_NAME , + .of_match_table = bt_bmc_match, + }, + .probe = bt_bmc_probe, + .remove = bt_bmc_remove, +}; + +module_platform_driver (bt_bmc_driver); + +MODULE_DEVICE_TABLE (of, bt_bmc_match); +MODULE_LICENSE ("GPL" ); +MODULE_AUTHOR ("Alistair Popple <[email protected]>" ); +MODULE_DESCRIPTION ("Linux device interface to the BT interface" );include/uapi/linux/Kbuild +1
-0@@ -74,6 +74,7 @@ header-y += bpf_common.h header-y += bpf.h header-y += bpqether.h header-y += bsg.h +header-y += bt-bmc.h header-y += btrfs.h header-y += can.h header-y += capability.hinclude/uapi/linux/bt-bmc.h new file +18
-0@@ -0,0 +1,18 @@ +/* +* Copyright (c) 2015-2016, IBM Corporation. +* +* This program is free software; you can redistribute it and/or +* modify it under the terms of the GNU General Public License +* as published by the Free Software Foundation; either version +* 2 of the License, or (at your option) any later version. +*/ + +#ifndef _UAPI_LINUX_BT_BMC_H +#define _UAPI_LINUX_BT_BMC_H + +#include <linux/ioctl.h> + +#define __BT_BMC_IOCTL_MAGIC 0xb1 +#define BT_BMC_IOCTL_SMS_ATN _IO(__BT_BMC_IOCTL_MAGIC, 0x00) + +#endif /* _UAPI_LINUX_BT_BMC_H */
PATCH v2 1/3 ipmi: add an Aspeed BT IPMI BMC driver
Quoted 26 lines · Corey Minyard
Quoted 15 lines · C?dric Le Goater
From: Alistair Popple <[email protected]>
This patch adds a simple device driver to expose the iBT interface on Aspeed SOCs (AST2400 and AST2500) as a character device. Such SOCs are commonly used as BMCs (BaseBoard Management Controllers) and this driver implements the BMC side of the BT interface.
The BT (Block Transfer) interface is used to perform in-band IPMI communication between a host and its BMC. Entire messages are buffered before sending a notification to the other end, host or BMC, that there is data to be read. Usually, the host emits requests and the BMC responses but the specification provides a mean for the BMC to send SMS Attention (BMC-to-Host attention or System Management Software attention) messages.
Quoted 5 lines
For this purpose, the driver introduces a specific ioctl on the
device: 'BT_BMC_IOCTL_SMS_ATN' that can be used by the system running on the BMC to signal the host of such an event.The device name defaults to '
/dev/ipmi-bt-host'Others have reviewed this for style and such, and I have looked at it from a protocol point of view. it looks to be sound for the most part. I have some higher level concerns:
Quoted 9 lines
There appears to be no handling for multiple simultaneous users. This interface can only be used by one task at a time, so you should probably only allow one opener. Well, I guess the BMC could be split into a reader and a writer task, so I'm not really sure about that, but I would think in most situations having more than one opener is a bug. You do call
clr_b_busy()on open, for instance, which might be an issue for multiple openers. Maybe a module parameter for maximum number of openers? Just want to make sure this was thought about, at least.
yes but not implemented ... The open_count in the bt_bmc structure is unused. In v3, I will replace it with a global atomic_t tracked in the open and release operations.
Quoted 4 lines
There is also no mutex protecting reading or writing. If multiple threads call read or write at the same time, it probably wouldn't work correctly. I think you need a read and a write mutex on the interface to protect against this.
yes. I will add a mutex also in v3.
Quoted 8 lines
The spec says:
The BMC must not return a given response once the corresponding Request-to-Response interval has passed. The BMC can ensure this by maintaining its own internal list of outstanding requests through the interface. The BMC could age and expire the entries in the list by expiring the entries at an interval that is somewhat shorter than the specified Request-to-Response interval....
This is clearly not handled in the driver.
For this purpose, we could maintain a request expiry list using the seq field of the BT message. Update the list in the read and write operations and arm a timer to garbage collect any left overs. As for the errno in the write when a response had timeout'ed, may be ETIMEDOUT ?
For configuration of the maximum response time, a sysfs file would do I think.
Do you want that in v3 also ? I have some experimental patches for it, that I can send as follow ups.
Thanks,
C.
Quoted 649 lines
On the write side, though, there doesn't seem to be a way to handle a situation where the host side doesn't respond for a while and the pending message would need to be discarded.
The spec doesn't mention much about error recovery on this interface, but the way this is written should be fine, I think.
I'm copying Rocky Craig, who wrote the host side driver for Linux, in case he wants to comment on this.
This is easy to read and understand, so I think v3 should be good.
Thanks,
-corey
Quoted 631 lines
Signed-off-by Alistair Popple <[email protected]>Signed-off-by Jeremy Kerr <[email protected]>Signed-off-by Joel Stanley <[email protected]>[clg: - checkpatch fixes
- added a devicetree binding documentation
- replace 'bt_host' by 'bt_bmc' to reflect that the driver is the BMC side of the IPMI BT interface
- renamed the device to 'ipmi-bt-host'
- introduced a temporary buffer to copy_{to,from}_user
- usedplatform_get_irq()
- moved the driver underdrivers/char/ipmi/but kept it as a misc device
- changed the compatible cell to "aspeed,ast2400-bt-bmc"
]Signed-off-by C?dric Le Goater <[email protected]>---
Changes since v1:
- replace '
bt_host' by 'bt_bmc' to reflect that the driver is the BMC side of the IPMI BT interface
- renamed the device to 'ipmi-bt-host'
- introduced a temporary buffer to copy_{to,from}_user
- usedplatform_get_irq()
- moved the driver underdrivers/char/ipmi/but kept it as a misc device
- changed the compatible cell to "aspeed,ast2400-bt-bmc".../bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt | 23 + drivers/Makefile | 2 +- drivers/char/ipmi/Kconfig | 7 + drivers/char/ipmi/Makefile | 1 + drivers/char/ipmi/bt-bmc.c | 486 +++++++++++++++++++++ include/uapi/linux/Kbuild | 1 + include/uapi/linux/bt-bmc.h | 18 + 7 files changed, 537 insertions(+), 1 deletion(-)create mode 100644
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txtcreate mode 100644drivers/char/ipmi/bt-bmc.c
create mode 100644include/uapi/linux/bt-bmc.hDocumentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt new file +23
-0@@ -0,0 +1,23 @@ +* Aspeed BT (Block Transfer) IPMI interface + +The Aspeed SOCs (AST2400 and AST2500) are commonly used as BMCs +(BaseBoard Management Controllers) and the BT interface can be used to +perform in-band IPMI communication with their host. + +Required properties: + +- compatible : should be "aspeed,ast2400-bt-bmc" +- reg: physical address and size of the registers + +Optional properties: + +- interrupts: interrupt generated by the BT interface. without an + interrupt, the driver will operate in poll mode. + +Example: + + ibt at 1e789140 { + compatible = "aspeed,ast2400-bt-bmc"; + reg = <0x1e789140 0x18>; + interrupts = <8>; + };drivers/Makefile +1
-1@@ -21,7 +21,7 @@ obj-y += video/ obj-y += idle/ # IPMI must come before ACPI in order to provide IPMI opregion support -obj-$(CONFIG_IPMI_HANDLER) += char/ipmi/ +obj-y += char/ipmi/ obj-$(CONFIG_ACPI) += acpi/ obj-$(CONFIG_SFI) += sfi/drivers/char/ipmi/Kconfig +7
-0@@ -76,3 +76,10 @@ config IPMI_POWEROFF the IPMI management controller is capable of this. endif # IPMI_HANDLER + +config ASPEED_BT_IPMI_BMC + tristate "BT IPMI bmc driver" + help + Provides a driver for the BT (Block Transfer) IPMI interface + found on Aspeed SOCs (AST2400 and AST2500). The driver + implements the BMC side of the BT interface.drivers/char/ipmi/Makefile +1
-0@@ -11,3 +11,4 @@ obj-$(CONFIG_IPMI_SSIF) += ipmi_ssif.o obj-$(CONFIG_IPMI_POWERNV) += ipmi_powernv.o obj-$(CONFIG_IPMI_WATCHDOG) += ipmi_watchdog.o obj-$(CONFIG_IPMI_POWEROFF) += ipmi_poweroff.o +obj-$(CONFIG_ASPEED_BT_IPMI_BMC) += bt-bmc.odrivers/char/ipmi/bt-bmc.c new file +486
-0@@ -0,0 +1,486 @@ +/* +* Copyright (c) 2015-2016, IBM Corporation. +* +* This program is free software; you can redistribute it and/or +* modify it under the terms of the GNU General Public License +* as published by the Free Software Foundation; either version +* 2 of the License, or (at your option) any later version. +*/ + +#include <linux/module.h> +#include <linux/moduleparam.h> +#include <linux/errno.h> +#include <linux/poll.h> +#include <linux/sched.h> +#include <linux/spinlock.h> +#include <linux/slab.h> +#include <linux/init.h> +#include <linux/device.h> +#include <linux/of.h> +#include <linux/of_irq.h> +#include <linux/platform_device.h> +#include <linux/io.h> +#include <linux/interrupt.h> +#include <linux/delay.h> +#include <linux/miscdevice.h> +#include <linux/timer.h> +#include <linux/jiffies.h> +#include <linux/bt-bmc.h> + +/* +* This is a BMC device used to communicate to the host +*/ +#define DEVICE_NAME "ipmi-bt-host" + +#define BT_IO_BASE 0xe4 +#define BT_IRQ 10 + +#define BT_CR0 0x0 +#define BT_CR0_IO_BASE 16 +#define BT_CR0_IRQ 12 +#define BT_CR0_EN_CLR_SLV_RDP 0x8 +#define BT_CR0_EN_CLR_SLV_WRP 0x4 +#define BT_CR0_ENABLE_IBT 0x1 +#define BT_CR1 0x4 +#define BT_CR1_IRQ_H2B 0x01 +#define BT_CR1_IRQ_HBUSY 0x40 +#define BT_CR2 0x8 +#define BT_CR2_IRQ_H2B 0x01 +#define BT_CR2_IRQ_HBUSY 0x40 +#define BT_CR3 0xc +#define BT_CTRL 0x10 +#define BT_CTRL_B_BUSY 0x80 +#define BT_CTRL_H_BUSY 0x40 +#define BT_CTRL_OEM0 0x20 +#define BT_CTRL_SMS_ATN 0x10 +#define BT_CTRL_B2H_ATN 0x08 +#define BT_CTRL_H2B_ATN 0x04 +#define BT_CTRL_CLR_RD_PTR 0x02 +#define BT_CTRL_CLR_WR_PTR 0x01 +#define BT_BMC2HOST 0x14 +#define BT_INTMASK 0x18 +#define BT_INTMASK_B2H_IRQEN 0x01 +#define BT_INTMASK_B2H_IRQ 0x02 +#define BT_INTMASK_BMC_HWRST 0x80 + +struct bt_bmc { +struct device dev; +struct miscdevice miscdev; +void __iomem *base; +int open_count; +int irq; +wait_queue_head_t queue; +struct timer_list poll_timer; +}; + +static u8 bt_inb (struct bt_bmc *bt_bmc,int reg) +{ +return ioread8 (bt_bmc->base + reg); +} + +static void bt_outb (struct bt_bmc *bt_bmc,u8 data,int reg) +{ +iowrite8 (data, bt_bmc->base + reg); +} + +static void clr_rd_ptr (struct bt_bmc *bt_bmc) +{ +bt_outb (bt_bmc,BT_CTRL_CLR_RD_PTR ,BT_CTRL ); +} + +static void clr_wr_ptr (struct bt_bmc *bt_bmc) +{ +bt_outb (bt_bmc,BT_CTRL_CLR_WR_PTR ,BT_CTRL ); +} + +static void clr_h2b_atn (struct bt_bmc *bt_bmc) +{ +bt_outb (bt_bmc,BT_CTRL_H2B_ATN ,BT_CTRL ); +} + +static void set_b_busy (struct bt_bmc *bt_bmc) +{ +if (!(bt_inb (bt_bmc,BT_CTRL ) &BT_CTRL_B_BUSY )) +bt_outb (bt_bmc,BT_CTRL_B_BUSY ,BT_CTRL ); +} + +static void clr_b_busy (struct bt_bmc *bt_bmc) +{ +if (bt_inb (bt_bmc,BT_CTRL ) &BT_CTRL_B_BUSY ) +bt_outb (bt_bmc,BT_CTRL_B_BUSY ,BT_CTRL ); +} + +static void set_b2h_atn (struct bt_bmc *bt_bmc) +{ +bt_outb (bt_bmc,BT_CTRL_B2H_ATN ,BT_CTRL ); +} + +static u8 bt_read (struct bt_bmc *bt_bmc) +{ +return bt_inb (bt_bmc,BT_BMC2HOST ); +} + +static ssize_t bt_readn (struct bt_bmc *bt_bmc,u8 *buf,size_t n) +{ +int i; + +for (i =0 ; i < n; i++) + buf[i] =bt_read (bt_bmc); +return n; +} + +static void bt_write (struct bt_bmc *bt_bmc,u8 c) +{ +bt_outb (bt_bmc, c,BT_BMC2HOST ); +} + +static ssize_t bt_writen (struct bt_bmc *bt_bmc,u8 *buf,size_t n) +{ +int i; + +for (i =0 ; i < n; i++) +bt_write (bt_bmc, buf[i]); +return n; +} + +static void set_sms_atn (struct bt_bmc *bt_bmc) +{ +bt_outb (bt_bmc,BT_CTRL_SMS_ATN ,BT_CTRL ); +} + +static struct bt_bmc *file_bt_bmc (struct file *file) +{ + return container_of(file->private_data, struct bt_bmc, miscdev); +} + +static int bt_bmc_open (struct inode *inode,struct file *file) +{ +struct bt_bmc *bt_bmc =file_bt_bmc (file); + +clr_b_busy (bt_bmc); + +return 0 ; +} + +#define BT_BMC_BUFFER_SIZE 256 + +/* +* The BT (Block Transfer) interface means that entire messages are +* buffered by the host before a notification is sent to the BMC that +* there is data to be read. The first byte is the length and the +* message data follows. The read operation just tries to capture the +* whole before returning it to userspace. +*/ +static ssize_t bt_bmc_read (struct file *file,char __user *buf, +size_t count,loff_t *ppos) +{ +struct bt_bmc *bt_bmc =file_bt_bmc (file); +u8 len; +int len_byte =1 ; +u8 kbuffer[BT_BMC_BUFFER_SIZE ]; +ssize_t ret =0 ; +ssize_t nread; + +if (!access_ok (VERIFY_WRITE , buf, count)) +return -EFAULT ; + +WARN_ON (*ppos); + +if (wait_event_interruptible (bt_bmc->queue, +bt_inb (bt_bmc,BT_CTRL ) &BT_CTRL_H2B_ATN )) +return -ERESTARTSYS ; + +set_b_busy (bt_bmc); +clr_h2b_atn (bt_bmc); +clr_rd_ptr (bt_bmc); + +/* +* The BT frames start with the message length, which does not +* include the length byte. +*/ + kbuffer[0 ] =bt_read (bt_bmc); + len = kbuffer[0 ]; + +/* We pass the length back to userspace as well */ +if (len +1 > count) + len = count -1 ; + +while (len) { + nread =min_t (ssize_t, len,sizeof (kbuffer) - len_byte); + +bt_readn (bt_bmc, kbuffer + len_byte, nread); + +if (copy_to_user (buf, kbuffer, nread + len_byte)) { + ret = -EFAULT ; +break ; + } + len -= nread; + buf += nread + len_byte; + ret += nread + len_byte; + len_byte =0 ; + } + +clr_b_busy (bt_bmc); + +return ret; +} + +static ssize_t bt_bmc_write (struct file *file,const char __user *buf, +size_t count,loff_t *ppos) +{ +struct bt_bmc *bt_bmc =file_bt_bmc (file); +u8 kbuffer[BT_BMC_BUFFER_SIZE ]; +ssize_t ret =0 ; +ssize_t nwritten; + +if (!access_ok (VERIFY_READ , buf, count)) +return -EFAULT ; + +WARN_ON (*ppos); + +/* There's no interrupt for clearing bmc busy so we have to +* poll +*/ +if (wait_event_interruptible (bt_bmc->queue, + !(bt_inb (bt_bmc,BT_CTRL ) & + (BT_CTRL_H_BUSY |BT_CTRL_B2H_ATN )))) +return -ERESTARTSYS ; + +clr_wr_ptr (bt_bmc); + +while (count) { + nwritten =min_t (ssize_t, count,sizeof (kbuffer)); +if (copy_from_user (&kbuffer, buf, nwritten)) { + ret = -EFAULT ; +break ; + } + +bt_writen (bt_bmc, kbuffer, nwritten); + + count -= nwritten; + buf += nwritten; + ret += nwritten; + } + +set_b2h_atn (bt_bmc); + +return ret; +} + +static long bt_bmc_ioctl (struct file *file,unsigned int cmd, +unsigned long param) +{ +struct bt_bmc *bt_bmc =file_bt_bmc (file); + +switch (cmd) { +case BT_BMC_IOCTL_SMS_ATN : +set_sms_atn (bt_bmc); +return 0 ; + } +return -EINVAL ; +} + +static int bt_bmc_release (struct inode *inode,struct file *file) +{ +struct bt_bmc *bt_bmc =file_bt_bmc (file); + +set_b_busy (bt_bmc); +return 0 ; +} + +static unsigned int bt_bmc_poll (struct file *file,poll_table *wait) +{ +struct bt_bmc *bt_bmc =file_bt_bmc (file); +unsigned int mask =0 ; +uint8_t ctrl; + +poll_wait (file, &bt_bmc->queue, wait); + + ctrl =bt_inb (bt_bmc,BT_CTRL ); + +if (ctrl &BT_CTRL_H2B_ATN ) + mask |=POLLIN ; + +if (!(ctrl & (BT_CTRL_H_BUSY |BT_CTRL_B2H_ATN ))) + mask |=POLLOUT ; + +return mask; +} + +static const struct file_operations bt_bmc_fops = { + .owner =THIS_MODULE , + .open = bt_bmc_open, + .read = bt_bmc_read, + .write = bt_bmc_write, + .release = bt_bmc_release, + .poll = bt_bmc_poll, + .unlocked_ioctl = bt_bmc_ioctl, +}; + +static void poll_timer (unsigned long data) +{ +struct bt_bmc *bt_bmc = (void *)data; + + bt_bmc->poll_timer.expires +=msecs_to_jiffies (500 ); +wake_up (&bt_bmc->queue); +add_timer (&bt_bmc->poll_timer); +} + +static irqreturn_t bt_bmc_irq (int irq,void *arg) +{ +struct bt_bmc *bt_bmc = arg; +uint32_t reg; + + reg =ioread32 (bt_bmc->base +BT_CR2 ); + reg &=BT_CR2_IRQ_H2B |BT_CR2_IRQ_HBUSY ; +if (!reg) +return IRQ_NONE ; + +/* ack pending IRQs */ +iowrite32 (reg, bt_bmc->base +BT_CR2 ); + +wake_up (&bt_bmc->queue); +return IRQ_HANDLED ; +} + +static int bt_bmc_config_irq (struct bt_bmc *bt_bmc, +struct platform_device *pdev) +{ +struct device *dev = &pdev->dev; +uint32_t reg; +int rc; + + bt_bmc->irq =platform_get_irq (pdev,0 ); +if (!bt_bmc->irq) +return -ENODEV ; + + rc =devm_request_irq (dev, bt_bmc->irq, bt_bmc_irq,IRQF_SHARED , +DEVICE_NAME , bt_bmc); +if (rc <0 ) { +dev_warn (dev,"Unable to request IRQ %d\n" , bt_bmc->irq); + bt_bmc->irq =0 ; +return rc; + } + +/* Configure IRQs on the bmc clearing the H2B and HBUSY bits; +* H2B will be asserted when the bmc has data for us; HBUSY +* will be cleared (along with B2H) when we can write the next +* message to the BT buffer +*/ + reg =ioread32 (bt_bmc->base +BT_CR1 ); + reg |=BT_CR1_IRQ_H2B |BT_CR1_IRQ_HBUSY ; +iowrite32 (reg, bt_bmc->base +BT_CR1 ); + +return 0 ; +} + +static int bt_bmc_probe (struct platform_device *pdev) +{ +struct bt_bmc *bt_bmc; +struct device *dev; +struct resource *res; +int rc; + +if (!pdev || !pdev->dev.of_node) +return -ENODEV ; + + dev = &pdev->dev; +dev_info (dev,"Found bt bmc device\n" ); + + bt_bmc =devm_kzalloc (dev,sizeof (*bt_bmc),GFP_KERNEL ); +if (!bt_bmc) +return -ENOMEM ; + +dev_set_drvdata (&pdev->dev, bt_bmc); + + res =platform_get_resource (pdev,IORESOURCE_MEM ,0 ); +if (!res) { +dev_err (dev,"Unable to find resources\n" ); + rc = -ENXIO ; + goto out_free; + } + + bt_bmc->base =devm_ioremap_resource (&pdev->dev, res); +if (!bt_bmc->base) { + rc = -ENOMEM ; + goto out_free; + } + +init_waitqueue_head (&bt_bmc->queue); + + bt_bmc->miscdev.minor =MISC_DYNAMIC_MINOR , + bt_bmc->miscdev.name =DEVICE_NAME , + bt_bmc->miscdev.fops = &bt_bmc_fops, + bt_bmc->miscdev.parent = dev; + rc =misc_register (&bt_bmc->miscdev); +if (rc) { +dev_err (dev,"Unable to register device\n" ); + goto out_unmap; + } + +bt_bmc_config_irq (bt_bmc, pdev); + +if (bt_bmc->irq) { +dev_info (dev,"Using IRQ %d\n" , bt_bmc->irq); + }else { +dev_info (dev,"No IRQ; using timer\n" ); +setup_timer (&bt_bmc->poll_timer, poll_timer, + (unsigned long )bt_bmc); + bt_bmc->poll_timer.expires = jiffies +msecs_to_jiffies (10 ); +add_timer (&bt_bmc->poll_timer); + } + +iowrite32 ((BT_IO_BASE <<BT_CR0_IO_BASE ) | + (BT_IRQ <<BT_CR0_IRQ ) | +BT_CR0_EN_CLR_SLV_RDP | +BT_CR0_EN_CLR_SLV_WRP | +BT_CR0_ENABLE_IBT , + bt_bmc->base +BT_CR0 ); + +clr_b_busy (bt_bmc); + +return 0 ; + +out_unmap: +devm_iounmap (&pdev->dev, bt_bmc->base); + +out_free: +devm_kfree (dev, bt_bmc); +return rc; + +} + +static int bt_bmc_remove (struct platform_device *pdev) +{ +struct bt_bmc *bt_bmc =dev_get_drvdata (&pdev->dev); + +misc_deregister (&bt_bmc->miscdev); +if (!bt_bmc->irq) +del_timer_sync (&bt_bmc->poll_timer); +devm_iounmap (&pdev->dev, bt_bmc->base); +devm_kfree (&pdev->dev, bt_bmc); + bt_bmc =NULL ; + +return 0 ; +} + +static const struct of_device_id bt_bmc_match[] = { + { .compatible ="aspeed,ast2400-bt-bmc" }, + { }, +}; + +static struct platform_driver bt_bmc_driver = { + .driver = { + .name =DEVICE_NAME , + .of_match_table = bt_bmc_match, + }, + .probe = bt_bmc_probe, + .remove = bt_bmc_remove, +}; + +module_platform_driver (bt_bmc_driver); + +MODULE_DEVICE_TABLE (of, bt_bmc_match); +MODULE_LICENSE ("GPL" ); +MODULE_AUTHOR ("Alistair Popple <[email protected]>" ); +MODULE_DESCRIPTION ("Linux device interface to the BT interface" );include/uapi/linux/Kbuild +1
-0@@ -74,6 +74,7 @@ header-y += bpf_common.h header-y += bpf.h header-y += bpqether.h header-y += bsg.h +header-y += bt-bmc.h header-y += btrfs.h header-y += can.h header-y += capability.hinclude/uapi/linux/bt-bmc.h new file +18
-0@@ -0,0 +1,18 @@ +/* +* Copyright (c) 2015-2016, IBM Corporation. +* +* This program is free software; you can redistribute it and/or +* modify it under the terms of the GNU General Public License +* as published by the Free Software Foundation; either version +* 2 of the License, or (at your option) any later version. +*/ + +#ifndef _UAPI_LINUX_BT_BMC_H +#define _UAPI_LINUX_BT_BMC_H + +#include <linux/ioctl.h> + +#define __BT_BMC_IOCTL_MAGIC 0xb1 +#define BT_BMC_IOCTL_SMS_ATN _IO(__BT_BMC_IOCTL_MAGIC, 0x00) + +#endif /* _UAPI_LINUX_BT_BMC_H */
PATCH v2 1/3 ipmi: add an Aspeed BT IPMI BMC driver
Quoted 53 lines · C?dric Le Goater
Quoted 25 lines · Corey Minyard
Quoted 15 lines · C?dric Le Goater
From: Alistair Popple <[email protected]>
This patch adds a simple device driver to expose the iBT interface on Aspeed SOCs (AST2400 and AST2500) as a character device. Such SOCs are commonly used as BMCs (BaseBoard Management Controllers) and this driver implements the BMC side of the BT interface.
The BT (Block Transfer) interface is used to perform in-band IPMI communication between a host and its BMC. Entire messages are buffered before sending a notification to the other end, host or BMC, that there is data to be read. Usually, the host emits requests and the BMC responses but the specification provides a mean for the BMC to send SMS Attention (BMC-to-Host attention or System Management Software attention) messages.
Quoted 5 lines
For this purpose, the driver introduces a specific ioctl on the
device: 'BT_BMC_IOCTL_SMS_ATN' that can be used by the system running on the BMC to signal the host of such an event.The device name defaults to '
/dev/ipmi-bt-host'Others have reviewed this for style and such, and I have looked at it from a protocol point of view. it looks to be sound for the most part. I have some higher level concerns:
Quoted 9 lines
There appears to be no handling for multiple simultaneous users. This interface can only be used by one task at a time, so you should probably only allow one opener. Well, I guess the BMC could be split into a reader and a writer task, so I'm not really sure about that, but I would think in most situations having more than one opener is a bug. You do call
clr_b_busy()on open, for instance, which might be an issue for multiple openers. Maybe a module parameter for maximum number of openers? Just want to make sure this was thought about, at least.yes but not implemented ... The
open_countin thebt_bmcstructure is unused. In v3, I will replace it with a globalatomic_ttracked in the open and release operations.Quoted 4 lines
There is also no mutex protecting reading or writing. If multiple threads call read or write at the same time, it probably wouldn't work correctly. I think you need a read and a write mutex on the interface to protect against this.
yes. I will add a mutex also in v3.
Quoted 8 lines
The spec says:
The BMC must not return a given response once the corresponding Request-to-Response interval has passed. The BMC can ensure this by maintaining its own internal list of outstanding requests through the interface. The BMC could age and expire the entries in the list by expiring the entries at an interval that is somewhat shorter than the specified Request-to-Response interval....
Quoted 6 lines
This is clearly not handled in the driver.
For this purpose, we could maintain a request expiry list using the seq field of the BT message. Update the list in the read and write operations and arm a timer to garbage collect any left overs. As for the errno in the write when a response had timeout'ed, may be ETIMEDOUT ?
I think that would work, though I don't think you really need an error response in this case.
I was thinking more just a timeout in the write function. Ideally the timeout would be calculated at receive time and then be passed in on every write, to preserve the request-to-response time for slow messages. I like the simplicity of the driver the way it is.
The trouble is that there is no easy way to pass in a timeout in a write operation. You could pass in a structure where the first part is a 32-bit timeout, or something like that. Or maybe just a fixed timeout and assume every message is handled in a short enough time that it meets the spec requirement. But that doesn't handle slowness on the host side. You can send the message via an ioctl, which again isn't terribly ideal.
It would be nice if there was a write function which was able to pass metadata, but AFAIK that's only available on sockets.
Quoted 5 lines
For configuration of the maximum response time, a sysfs file would do I think.
Do you want that in v3 also ? I have some experimental patches for it, that I can send as follow ups.
I'm fine either way.
Thanks,
-corey
Quoted 653 lines
Thanks,
C.
Quoted 648 lines
On the write side, though, there doesn't seem to be a way to handle a situation where the host side doesn't respond for a while and the pending message would need to be discarded.
The spec doesn't mention much about error recovery on this interface, but the way this is written should be fine, I think.
I'm copying Rocky Craig, who wrote the host side driver for Linux, in case he wants to comment on this.
This is easy to read and understand, so I think v3 should be good.
Thanks,
-corey
Quoted 631 lines
Signed-off-by Alistair Popple <[email protected]>Signed-off-by Jeremy Kerr <[email protected]>Signed-off-by Joel Stanley <[email protected]>[clg: - checkpatch fixes
- added a devicetree binding documentation
- replace 'bt_host' by 'bt_bmc' to reflect that the driver is the BMC side of the IPMI BT interface
- renamed the device to 'ipmi-bt-host'
- introduced a temporary buffer to copy_{to,from}_user
- usedplatform_get_irq()
- moved the driver underdrivers/char/ipmi/but kept it as a misc device
- changed the compatible cell to "aspeed,ast2400-bt-bmc"
]Signed-off-by C?dric Le Goater <[email protected]>---
Changes since v1:
- replace '
bt_host' by 'bt_bmc' to reflect that the driver is the BMC side of the IPMI BT interface
- renamed the device to 'ipmi-bt-host'
- introduced a temporary buffer to copy_{to,from}_user
- usedplatform_get_irq()
- moved the driver underdrivers/char/ipmi/but kept it as a misc device
- changed the compatible cell to "aspeed,ast2400-bt-bmc".../bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt | 23 + drivers/Makefile | 2 +- drivers/char/ipmi/Kconfig | 7 + drivers/char/ipmi/Makefile | 1 + drivers/char/ipmi/bt-bmc.c | 486 +++++++++++++++++++++ include/uapi/linux/Kbuild | 1 + include/uapi/linux/bt-bmc.h | 18 + 7 files changed, 537 insertions(+), 1 deletion(-)create mode 100644
Documentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txtcreate mode 100644drivers/char/ipmi/bt-bmc.c
create mode 100644include/uapi/linux/bt-bmc.hDocumentation/devicetree/bindings/char/ipmi/aspeed,ast2400-bt-bmc.txt new file +23
-0@@ -0,0 +1,23 @@ +* Aspeed BT (Block Transfer) IPMI interface + +The Aspeed SOCs (AST2400 and AST2500) are commonly used as BMCs +(BaseBoard Management Controllers) and the BT interface can be used to +perform in-band IPMI communication with their host. + +Required properties: + +- compatible : should be "aspeed,ast2400-bt-bmc" +- reg: physical address and size of the registers + +Optional properties: + +- interrupts: interrupt generated by the BT interface. without an + interrupt, the driver will operate in poll mode. + +Example: + + ibt at 1e789140 { + compatible = "aspeed,ast2400-bt-bmc"; + reg = <0x1e789140 0x18>; + interrupts = <8>; + };drivers/Makefile +1
-1@@ -21,7 +21,7 @@ obj-y += video/ obj-y += idle/ # IPMI must come before ACPI in order to provide IPMI opregion support -obj-$(CONFIG_IPMI_HANDLER) += char/ipmi/ +obj-y += char/ipmi/ obj-$(CONFIG_ACPI) += acpi/ obj-$(CONFIG_SFI) += sfi/drivers/char/ipmi/Kconfig +7
-0@@ -76,3 +76,10 @@ config IPMI_POWEROFF the IPMI management controller is capable of this. endif # IPMI_HANDLER + +config ASPEED_BT_IPMI_BMC + tristate "BT IPMI bmc driver" + help + Provides a driver for the BT (Block Transfer) IPMI interface + found on Aspeed SOCs (AST2400 and AST2500). The driver + implements the BMC side of the BT interface.drivers/char/ipmi/Makefile +1
-0@@ -11,3 +11,4 @@ obj-$(CONFIG_IPMI_SSIF) += ipmi_ssif.o obj-$(CONFIG_IPMI_POWERNV) += ipmi_powernv.o obj-$(CONFIG_IPMI_WATCHDOG) += ipmi_watchdog.o obj-$(CONFIG_IPMI_POWEROFF) += ipmi_poweroff.o +obj-$(CONFIG_ASPEED_BT_IPMI_BMC) += bt-bmc.odrivers/char/ipmi/bt-bmc.c new file +486
-0@@ -0,0 +1,486 @@ +/* +* Copyright (c) 2015-2016, IBM Corporation. +* +* This program is free software; you can redistribute it and/or +* modify it under the terms of the GNU General Public License +* as published by the Free Software Foundation; either version +* 2 of the License, or (at your option) any later version. +*/ + +#include <linux/module.h> +#include <linux/moduleparam.h> +#include <linux/errno.h> +#include <linux/poll.h> +#include <linux/sched.h> +#include <linux/spinlock.h> +#include <linux/slab.h> +#include <linux/init.h> +#include <linux/device.h> +#include <linux/of.h> +#include <linux/of_irq.h> +#include <linux/platform_device.h> +#include <linux/io.h> +#include <linux/interrupt.h> +#include <linux/delay.h> +#include <linux/miscdevice.h> +#include <linux/timer.h> +#include <linux/jiffies.h> +#include <linux/bt-bmc.h> + +/* +* This is a BMC device used to communicate to the host +*/ +#define DEVICE_NAME "ipmi-bt-host" + +#define BT_IO_BASE 0xe4 +#define BT_IRQ 10 + +#define BT_CR0 0x0 +#define BT_CR0_IO_BASE 16 +#define BT_CR0_IRQ 12 +#define BT_CR0_EN_CLR_SLV_RDP 0x8 +#define BT_CR0_EN_CLR_SLV_WRP 0x4 +#define BT_CR0_ENABLE_IBT 0x1 +#define BT_CR1 0x4 +#define BT_CR1_IRQ_H2B 0x01 +#define BT_CR1_IRQ_HBUSY 0x40 +#define BT_CR2 0x8 +#define BT_CR2_IRQ_H2B 0x01 +#define BT_CR2_IRQ_HBUSY 0x40 +#define BT_CR3 0xc +#define BT_CTRL 0x10 +#define BT_CTRL_B_BUSY 0x80 +#define BT_CTRL_H_BUSY 0x40 +#define BT_CTRL_OEM0 0x20 +#define BT_CTRL_SMS_ATN 0x10 +#define BT_CTRL_B2H_ATN 0x08 +#define BT_CTRL_H2B_ATN 0x04 +#define BT_CTRL_CLR_RD_PTR 0x02 +#define BT_CTRL_CLR_WR_PTR 0x01 +#define BT_BMC2HOST 0x14 +#define BT_INTMASK 0x18 +#define BT_INTMASK_B2H_IRQEN 0x01 +#define BT_INTMASK_B2H_IRQ 0x02 +#define BT_INTMASK_BMC_HWRST 0x80 + +struct bt_bmc { +struct device dev; +struct miscdevice miscdev; +void __iomem *base; +int open_count; +int irq; +wait_queue_head_t queue; +struct timer_list poll_timer; +}; + +static u8 bt_inb (struct bt_bmc *bt_bmc,int reg) +{ +return ioread8 (bt_bmc->base + reg); +} + +static void bt_outb (struct bt_bmc *bt_bmc,u8 data,int reg) +{ +iowrite8 (data, bt_bmc->base + reg); +} + +static void clr_rd_ptr (struct bt_bmc *bt_bmc) +{ +bt_outb (bt_bmc,BT_CTRL_CLR_RD_PTR ,BT_CTRL ); +} + +static void clr_wr_ptr (struct bt_bmc *bt_bmc) +{ +bt_outb (bt_bmc,BT_CTRL_CLR_WR_PTR ,BT_CTRL ); +} + +static void clr_h2b_atn (struct bt_bmc *bt_bmc) +{ +bt_outb (bt_bmc,BT_CTRL_H2B_ATN ,BT_CTRL ); +} + +static void set_b_busy (struct bt_bmc *bt_bmc) +{ +if (!(bt_inb (bt_bmc,BT_CTRL ) &BT_CTRL_B_BUSY )) +bt_outb (bt_bmc,BT_CTRL_B_BUSY ,BT_CTRL ); +} + +static void clr_b_busy (struct bt_bmc *bt_bmc) +{ +if (bt_inb (bt_bmc,BT_CTRL ) &BT_CTRL_B_BUSY ) +bt_outb (bt_bmc,BT_CTRL_B_BUSY ,BT_CTRL ); +} + +static void set_b2h_atn (struct bt_bmc *bt_bmc) +{ +bt_outb (bt_bmc,BT_CTRL_B2H_ATN ,BT_CTRL ); +} + +static u8 bt_read (struct bt_bmc *bt_bmc) +{ +return bt_inb (bt_bmc,BT_BMC2HOST ); +} + +static ssize_t bt_readn (struct bt_bmc *bt_bmc,u8 *buf,size_t n) +{ +int i; + +for (i =0 ; i < n; i++) + buf[i] =bt_read (bt_bmc); +return n; +} + +static void bt_write (struct bt_bmc *bt_bmc,u8 c) +{ +bt_outb (bt_bmc, c,BT_BMC2HOST ); +} + +static ssize_t bt_writen (struct bt_bmc *bt_bmc,u8 *buf,size_t n) +{ +int i; + +for (i =0 ; i < n; i++) +bt_write (bt_bmc, buf[i]); +return n; +} + +static void set_sms_atn (struct bt_bmc *bt_bmc) +{ +bt_outb (bt_bmc,BT_CTRL_SMS_ATN ,BT_CTRL ); +} + +static struct bt_bmc *file_bt_bmc (struct file *file) +{ + return container_of(file->private_data, struct bt_bmc, miscdev); +} + +static int bt_bmc_open (struct inode *inode,struct file *file) +{ +struct bt_bmc *bt_bmc =file_bt_bmc (file); + +clr_b_busy (bt_bmc); + +return 0 ; +} + +#define BT_BMC_BUFFER_SIZE 256 + +/* +* The BT (Block Transfer) interface means that entire messages are +* buffered by the host before a notification is sent to the BMC that +* there is data to be read. The first byte is the length and the +* message data follows. The read operation just tries to capture the +* whole before returning it to userspace. +*/ +static ssize_t bt_bmc_read (struct file *file,char __user *buf, +size_t count,loff_t *ppos) +{ +struct bt_bmc *bt_bmc =file_bt_bmc (file); +u8 len; +int len_byte =1 ; +u8 kbuffer[BT_BMC_BUFFER_SIZE ]; +ssize_t ret =0 ; +ssize_t nread; + +if (!access_ok (VERIFY_WRITE , buf, count)) +return -EFAULT ; + +WARN_ON (*ppos); + +if (wait_event_interruptible (bt_bmc->queue, +bt_inb (bt_bmc,BT_CTRL ) &BT_CTRL_H2B_ATN )) +return -ERESTARTSYS ; + +set_b_busy (bt_bmc); +clr_h2b_atn (bt_bmc); +clr_rd_ptr (bt_bmc); + +/* +* The BT frames start with the message length, which does not +* include the length byte. +*/ + kbuffer[0 ] =bt_read (bt_bmc); + len = kbuffer[0 ]; + +/* We pass the length back to userspace as well */ +if (len +1 > count) + len = count -1 ; + +while (len) { + nread =min_t (ssize_t, len,sizeof (kbuffer) - len_byte); + +bt_readn (bt_bmc, kbuffer + len_byte, nread); + +if (copy_to_user (buf, kbuffer, nread + len_byte)) { + ret = -EFAULT ; +break ; + } + len -= nread; + buf += nread + len_byte; + ret += nread + len_byte; + len_byte =0 ; + } + +clr_b_busy (bt_bmc); + +return ret; +} + +static ssize_t bt_bmc_write (struct file *file,const char __user *buf, +size_t count,loff_t *ppos) +{ +struct bt_bmc *bt_bmc =file_bt_bmc (file); +u8 kbuffer[BT_BMC_BUFFER_SIZE ]; +ssize_t ret =0 ; +ssize_t nwritten; + +if (!access_ok (VERIFY_READ , buf, count)) +return -EFAULT ; + +WARN_ON (*ppos); + +/* There's no interrupt for clearing bmc busy so we have to +* poll +*/ +if (wait_event_interruptible (bt_bmc->queue, + !(bt_inb (bt_bmc,BT_CTRL ) & + (BT_CTRL_H_BUSY |BT_CTRL_B2H_ATN )))) +return -ERESTARTSYS ; + +clr_wr_ptr (bt_bmc); + +while (count) { + nwritten =min_t (ssize_t, count,sizeof (kbuffer)); +if (copy_from_user (&kbuffer, buf, nwritten)) { + ret = -EFAULT ; +break ; + } + +bt_writen (bt_bmc, kbuffer, nwritten); + + count -= nwritten; + buf += nwritten; + ret += nwritten; + } + +set_b2h_atn (bt_bmc); + +return ret; +} + +static long bt_bmc_ioctl (struct file *file,unsigned int cmd, +unsigned long param) +{ +struct bt_bmc *bt_bmc =file_bt_bmc (file); + +switch (cmd) { +case BT_BMC_IOCTL_SMS_ATN : +set_sms_atn (bt_bmc); +return 0 ; + } +return -EINVAL ; +} + +static int bt_bmc_release (struct inode *inode,struct file *file) +{ +struct bt_bmc *bt_bmc =file_bt_bmc (file); + +set_b_busy (bt_bmc); +return 0 ; +} + +static unsigned int bt_bmc_poll (struct file *file,poll_table *wait) +{ +struct bt_bmc *bt_bmc =file_bt_bmc (file); +unsigned int mask =0 ; +uint8_t ctrl; + +poll_wait (file, &bt_bmc->queue, wait); + + ctrl =bt_inb (bt_bmc,BT_CTRL ); + +if (ctrl &BT_CTRL_H2B_ATN ) + mask |=POLLIN ; + +if (!(ctrl & (BT_CTRL_H_BUSY |BT_CTRL_B2H_ATN ))) + mask |=POLLOUT ; + +return mask; +} + +static const struct file_operations bt_bmc_fops = { + .owner =THIS_MODULE , + .open = bt_bmc_open, + .read = bt_bmc_read, + .write = bt_bmc_write, + .release = bt_bmc_release, + .poll = bt_bmc_poll, + .unlocked_ioctl = bt_bmc_ioctl, +}; + +static void poll_timer (unsigned long data) +{ +struct bt_bmc *bt_bmc = (void *)data; + + bt_bmc->poll_timer.expires +=msecs_to_jiffies (500 ); +wake_up (&bt_bmc->queue); +add_timer (&bt_bmc->poll_timer); +} + +static irqreturn_t bt_bmc_irq (int irq,void *arg) +{ +struct bt_bmc *bt_bmc = arg; +uint32_t reg; + + reg =ioread32 (bt_bmc->base +BT_CR2 ); + reg &=BT_CR2_IRQ_H2B |BT_CR2_IRQ_HBUSY ; +if (!reg) +return IRQ_NONE ; + +/* ack pending IRQs */ +iowrite32 (reg, bt_bmc->base +BT_CR2 ); + +wake_up (&bt_bmc->queue); +return IRQ_HANDLED ; +} + +static int bt_bmc_config_irq (struct bt_bmc *bt_bmc, +struct platform_device *pdev) +{ +struct device *dev = &pdev->dev; +uint32_t reg; +int rc; + + bt_bmc->irq =platform_get_irq (pdev,0 ); +if (!bt_bmc->irq) +return -ENODEV ; + + rc =devm_request_irq (dev, bt_bmc->irq, bt_bmc_irq,IRQF_SHARED , +DEVICE_NAME , bt_bmc); +if (rc <0 ) { +dev_warn (dev,"Unable to request IRQ %d\n" , bt_bmc->irq); + bt_bmc->irq =0 ; +return rc; + } + +/* Configure IRQs on the bmc clearing the H2B and HBUSY bits; +* H2B will be asserted when the bmc has data for us; HBUSY +* will be cleared (along with B2H) when we can write the next +* message to the BT buffer +*/ + reg =ioread32 (bt_bmc->base +BT_CR1 ); + reg |=BT_CR1_IRQ_H2B |BT_CR1_IRQ_HBUSY ; +iowrite32 (reg, bt_bmc->base +BT_CR1 ); + +return 0 ; +} + +static int bt_bmc_probe (struct platform_device *pdev) +{ +struct bt_bmc *bt_bmc; +struct device *dev; +struct resource *res; +int rc; + +if (!pdev || !pdev->dev.of_node) +return -ENODEV ; + + dev = &pdev->dev; +dev_info (dev,"Found bt bmc device\n" ); + + bt_bmc =devm_kzalloc (dev,sizeof (*bt_bmc),GFP_KERNEL ); +if (!bt_bmc) +return -ENOMEM ; + +dev_set_drvdata (&pdev->dev, bt_bmc); + + res =platform_get_resource (pdev,IORESOURCE_MEM ,0 ); +if (!res) { +dev_err (dev,"Unable to find resources\n" ); + rc = -ENXIO ; + goto out_free; + } + + bt_bmc->base =devm_ioremap_resource (&pdev->dev, res); +if (!bt_bmc->base) { + rc = -ENOMEM ; + goto out_free; + } + +init_waitqueue_head (&bt_bmc->queue); + + bt_bmc->miscdev.minor =MISC_DYNAMIC_MINOR , + bt_bmc->miscdev.name =DEVICE_NAME , + bt_bmc->miscdev.fops = &bt_bmc_fops, + bt_bmc->miscdev.parent = dev; + rc =misc_register (&bt_bmc->miscdev); +if (rc) { +dev_err (dev,"Unable to register device\n" ); + goto out_unmap; + } + +bt_bmc_config_irq (bt_bmc, pdev); + +if (bt_bmc->irq) { +dev_info (dev,"Using IRQ %d\n" , bt_bmc->irq); + }else { +dev_info (dev,"No IRQ; using timer\n" ); +setup_timer (&bt_bmc->poll_timer, poll_timer, + (unsigned long )bt_bmc); + bt_bmc->poll_timer.expires = jiffies +msecs_to_jiffies (10 ); +add_timer (&bt_bmc->poll_timer); + } + +iowrite32 ((BT_IO_BASE <<BT_CR0_IO_BASE ) | + (BT_IRQ <<BT_CR0_IRQ ) | +BT_CR0_EN_CLR_SLV_RDP | +BT_CR0_EN_CLR_SLV_WRP | +BT_CR0_ENABLE_IBT , + bt_bmc->base +BT_CR0 ); + +clr_b_busy (bt_bmc); + +return 0 ; + +out_unmap: +devm_iounmap (&pdev->dev, bt_bmc->base); + +out_free: +devm_kfree (dev, bt_bmc); +return rc; + +} + +static int bt_bmc_remove (struct platform_device *pdev) +{ +struct bt_bmc *bt_bmc =dev_get_drvdata (&pdev->dev); + +misc_deregister (&bt_bmc->miscdev); +if (!bt_bmc->irq) +del_timer_sync (&bt_bmc->poll_timer); +devm_iounmap (&pdev->dev, bt_bmc->base); +devm_kfree (&pdev->dev, bt_bmc); + bt_bmc =NULL ; + +return 0 ; +} + +static const struct of_device_id bt_bmc_match[] = { + { .compatible ="aspeed,ast2400-bt-bmc" }, + { }, +}; + +static struct platform_driver bt_bmc_driver = { + .driver = { + .name =DEVICE_NAME , + .of_match_table = bt_bmc_match, + }, + .probe = bt_bmc_probe, + .remove = bt_bmc_remove, +}; + +module_platform_driver (bt_bmc_driver); + +MODULE_DEVICE_TABLE (of, bt_bmc_match); +MODULE_LICENSE ("GPL" ); +MODULE_AUTHOR ("Alistair Popple <[email protected]>" ); +MODULE_DESCRIPTION ("Linux device interface to the BT interface" );include/uapi/linux/Kbuild +1
-0@@ -74,6 +74,7 @@ header-y += bpf_common.h header-y += bpf.h header-y += bpqether.h header-y += bsg.h +header-y += bt-bmc.h header-y += btrfs.h header-y += can.h header-y += capability.hinclude/uapi/linux/bt-bmc.h new file +18
-0@@ -0,0 +1,18 @@ +/* +* Copyright (c) 2015-2016, IBM Corporation. +* +* This program is free software; you can redistribute it and/or +* modify it under the terms of the GNU General Public License +* as published by the Free Software Foundation; either version +* 2 of the License, or (at your option) any later version. +*/ + +#ifndef _UAPI_LINUX_BT_BMC_H +#define _UAPI_LINUX_BT_BMC_H + +#include <linux/ioctl.h> + +#define __BT_BMC_IOCTL_MAGIC 0xb1 +#define BT_BMC_IOCTL_SMS_ATN _IO(__BT_BMC_IOCTL_MAGIC, 0x00) + +#endif /* _UAPI_LINUX_BT_BMC_H */
PATCH v2 1/3 ipmi: add an Aspeed BT IPMI BMC driver
Quoted 37 lines
Quoted 8 lines
Quoted 8 lines
The spec says:
The BMC must not return a given response once the corresponding Request-to-Response interval has passed. The BMC can ensure this by maintaining its own internal list of outstanding requests through the interface. The BMC could age and expire the entries in the list by expiring the entries at an interval that is somewhat shorter than the specified Request-to-Response interval....
Quoted 6 lines
This is clearly not handled in the driver.
For this purpose, we could maintain a request expiry list using the seq field of the BT message. Update the list in the read and write operations and arm a timer to garbage collect any left overs. As for the errno in the write when a response had timeout'ed, may be ETIMEDOUT ?
I think that would work, though I don't think you really need an error response in this case.
I was thinking more just a timeout in the write function. Ideally the timeout would be calculated at receive time and then be passed in on every write, to preserve the request-to-response time for slow messages. I like the simplicity of the driver the way it is.
The trouble is that there is no easy way to pass in a timeout in a write operation. You could pass in a structure where the first part is a 32-bit timeout, or something like that. Or maybe just a fixed timeout and assume every message is handled in a short enough time that it meets the spec requirement. But that doesn't handle slowness on the host side. You can send the message via an ioctl, which again isn't terribly ideal.
It would be nice if there was a write function which was able to pass metadata, but AFAIK that's only available on sockets.
Quoted 7 lines
Quoted 5 lines
For configuration of the maximum response time, a sysfs file would do I think.
Do you want that in v3 also ? I have some experimental patches for it, that I can send as follow ups.
I'm fine either way.
OK. So I will send a v3 with minimal changes, as openbmc has been using this driver for a while now. We will discuss the response expiration on the next patchset.
I have pushed the patches here :
https://github.com/legoater/linux/commits/aspeed
Thanks,
C.
PATCH v2 2/3 ARM: aspeed: Add defconfigs for CONFIG_ASPEED_BT_IPMI_BMC
In reply to Cédric Le Goater---
Changes since v1:
- renamed config option
arch/arm/configs/aspeed_g4_defconfig | 1 + arch/arm/configs/aspeed_g5_defconfig | 1 + 2 files changed, 2 insertions(+)
arch/arm/configs/aspeed_g4_defconfig +1 -0
@@ -53,6 +53,7 @@ CONFIG_SERIAL_8250_RUNTIME_UARTS=6 CONFIG_SERIAL_8250_EXTENDED=y CONFIG_SERIAL_8250_SHARE_IRQ=y CONFIG_SERIAL_OF_PLATFORM=y +CONFIG_ASPEED_BT_IPMI_BMC=y # CONFIG_HW_RANDOM is not set # CONFIG_USB_SUPPORT is not set # CONFIG_IOMMU_SUPPORT is not set
arch/arm/configs/aspeed_g5_defconfig +1 -0
@@ -54,6 +54,7 @@ CONFIG_SERIAL_8250_RUNTIME_UARTS=6 CONFIG_SERIAL_8250_EXTENDED=y CONFIG_SERIAL_8250_SHARE_IRQ=y CONFIG_SERIAL_OF_PLATFORM=y +CONFIG_ASPEED_BT_IPMI_BMC=y # CONFIG_HW_RANDOM is not set # CONFIG_USB_SUPPORT is not set # CONFIG_IOMMU_SUPPORT is not set
Signature · 1 line
2.7.4
PATCH v2 3/3 ARM: dts: aspeed: Enable BT IPMI BMC device
In reply to Cédric Le Goater---
Changes since v1:
- added the soc name ast2400 in the compatible cell
arch/arm/boot/dts/aspeed-g4.dtsi | 6 ++++++ arch/arm/boot/dts/aspeed-g5.dtsi | 6 ++++++ 2 files changed, 12 insertions(+)
arch/arm/boot/dts/aspeed-g4.dtsi +6 -0
@@ -82,6 +82,12 @@ clocks = <&clk_apb>; }; + ibt: ibt at 1e789140 { + compatible = "aspeed,ast2400-bt-bmc"; + reg = <0x1e789140 0x18>; + interrupts = <8>; + }; + wdt1: wdt at 1e785000 { compatible = "aspeed,wdt"; reg = <0x1e785000 0x1c>;
arch/arm/boot/dts/aspeed-g5.dtsi +6 -0
@@ -86,6 +86,12 @@ clocks = <&clk_apb>; }; + ibt: ibt at 1e789140 { + compatible = "aspeed,ast2400-bt-bmc"; + reg = <0x1e789140 0x18>; + interrupts = <8>; + }; + wdt1: wdt at 1e785000 { compatible = "aspeed,wdt"; reg = <0x1e785000 0x1c>;
Signature · 1 line
2.7.4
v2 cover ARM: aspeed: add support for the BT IPMI interface
In reply to Cédric Le GoaterQuoted 4 lines · CEST C?dric Le Goater
C?dric Le Goater (2):
ARM: aspeed: Add defconfigs forCONFIG_ASPEED_BT_IPMI_BMC
ARM: dts: aspeed: Enable BT IPMI BMC device
These two should go through the arm-soc tree, I assume Joel will forward them to arm at kernel.org once the driver gets picked up into the ipmi tree.
Arnd