From: Eddie James <eajames@linux.ibm.com>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH v10 0/7] soc: aspeed: Add XDMA engine driver
Date: Mon, 20 Apr 2020 15:26:04 -0500 [thread overview]
Message-ID: <20200420202611.17776-1-eajames@linux.ibm.com> (raw)
This series adds a driver to control the Aspeed XDMA engine embedded in the
AST2500 and AST2600. The XDMA engine performs automatic DMA operations
over PCI-E between the Aspeed SOC (acting as a BMC) and a host processor.
Changes since v9:
- Remove the kernel command queue
- Use memcpy_toio instead to copy commands to the buffer
- Free the client's genalloc'd memory in the release method
- Switch the bindings documentation to yaml
- Add patches to fix SCU interrupt controller include
Changes since v8:
- Use DMA API to allocate memory from reserved region.
- Fix the driver for the AST2500 by keeping the command queue in kernel
memory and copying the whole buffer to the reserved memory area before
starting the operation.
- Add krefs to the client structure to prevent use-after-free.
- Switch reset-names binding to "device", "root-complex"
Eddie James (7):
dt-bindings: soc: Add Aspeed XDMA Engine
soc: aspeed: Add XDMA Engine Driver
soc: aspeed: xdma: Add user interface
soc: aspeed: xdma: Add reset ioctl
ARM: dts: Aspeed: AST2600: Add XDMA PCI-E root control reset
ARM: dts: Aspeed: AST2500: Add missing SCU interrupt controller
include
ARM: dts: Aspeed: AST2600: Add missing SCU interrupt controller
include
.../devicetree/bindings/soc/aspeed/xdma.yaml | 108 ++
MAINTAINERS | 8 +
arch/arm/boot/dts/aspeed-g5.dtsi | 1 +
arch/arm/boot/dts/aspeed-g6.dtsi | 4 +-
drivers/soc/aspeed/Kconfig | 8 +
drivers/soc/aspeed/Makefile | 1 +
drivers/soc/aspeed/aspeed-xdma.c | 1106 +++++++++++++++++
include/uapi/linux/aspeed-xdma.h | 42 +
8 files changed, 1277 insertions(+), 1 deletion(-)
create mode 100644 Documentation/devicetree/bindings/soc/aspeed/xdma.yaml
create mode 100644 drivers/soc/aspeed/aspeed-xdma.c
create mode 100644 include/uapi/linux/aspeed-xdma.h
--
2.24.0
WARNING: multiple messages have this Message-ID (diff)
From: Eddie James <eajames@linux.ibm.com>
To: linux-aspeed@lists.ozlabs.org
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
robh+dt@kernel.org, joel@jms.id.au, andrew@aj.id.au,
eajames@linux.ibm.com
Subject: [PATCH v10 0/7] soc: aspeed: Add XDMA engine driver
Date: Mon, 20 Apr 2020 15:26:04 -0500 [thread overview]
Message-ID: <20200420202611.17776-1-eajames@linux.ibm.com> (raw)
This series adds a driver to control the Aspeed XDMA engine embedded in the
AST2500 and AST2600. The XDMA engine performs automatic DMA operations
over PCI-E between the Aspeed SOC (acting as a BMC) and a host processor.
Changes since v9:
- Remove the kernel command queue
- Use memcpy_toio instead to copy commands to the buffer
- Free the client's genalloc'd memory in the release method
- Switch the bindings documentation to yaml
- Add patches to fix SCU interrupt controller include
Changes since v8:
- Use DMA API to allocate memory from reserved region.
- Fix the driver for the AST2500 by keeping the command queue in kernel
memory and copying the whole buffer to the reserved memory area before
starting the operation.
- Add krefs to the client structure to prevent use-after-free.
- Switch reset-names binding to "device", "root-complex"
Eddie James (7):
dt-bindings: soc: Add Aspeed XDMA Engine
soc: aspeed: Add XDMA Engine Driver
soc: aspeed: xdma: Add user interface
soc: aspeed: xdma: Add reset ioctl
ARM: dts: Aspeed: AST2600: Add XDMA PCI-E root control reset
ARM: dts: Aspeed: AST2500: Add missing SCU interrupt controller
include
ARM: dts: Aspeed: AST2600: Add missing SCU interrupt controller
include
.../devicetree/bindings/soc/aspeed/xdma.yaml | 108 ++
MAINTAINERS | 8 +
arch/arm/boot/dts/aspeed-g5.dtsi | 1 +
arch/arm/boot/dts/aspeed-g6.dtsi | 4 +-
drivers/soc/aspeed/Kconfig | 8 +
drivers/soc/aspeed/Makefile | 1 +
drivers/soc/aspeed/aspeed-xdma.c | 1106 +++++++++++++++++
include/uapi/linux/aspeed-xdma.h | 42 +
8 files changed, 1277 insertions(+), 1 deletion(-)
create mode 100644 Documentation/devicetree/bindings/soc/aspeed/xdma.yaml
create mode 100644 drivers/soc/aspeed/aspeed-xdma.c
create mode 100644 include/uapi/linux/aspeed-xdma.h
--
2.24.0
next reply other threads:[~2020-04-20 20:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 20:26 Eddie James [this message]
2020-04-20 20:26 ` [PATCH v10 0/7] soc: aspeed: Add XDMA engine driver Eddie James
2020-04-20 20:26 ` [PATCH v10 1/7] dt-bindings: soc: Add Aspeed XDMA Engine Eddie James
2020-04-20 20:26 ` Eddie James
2020-04-22 20:13 ` Rob Herring
2020-04-22 20:13 ` Rob Herring
2020-04-20 20:26 ` [PATCH v10 2/7] soc: aspeed: Add XDMA Engine Driver Eddie James
2020-04-20 20:26 ` Eddie James
2020-04-20 20:26 ` [PATCH v10 3/7] soc: aspeed: xdma: Add user interface Eddie James
2020-04-20 20:26 ` Eddie James
2020-04-20 20:26 ` [PATCH v10 4/7] soc: aspeed: xdma: Add reset ioctl Eddie James
2020-04-20 20:26 ` Eddie James
2020-04-20 20:26 ` [PATCH v10 5/7] ARM: dts: Aspeed: AST2600: Add XDMA PCI-E root control reset Eddie James
2020-04-20 20:26 ` Eddie James
2020-04-20 20:26 ` [PATCH v10 6/7] ARM: dts: Aspeed: AST2500: Add missing SCU interrupt controller include Eddie James
2020-04-20 20:26 ` Eddie James
2020-04-20 20:26 ` [PATCH v10 7/7] ARM: dts: Aspeed: AST2600: " Eddie James
2020-04-20 20:26 ` Eddie James
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200420202611.17776-1-eajames@linux.ibm.com \
--to=eajames@linux.ibm.com \
--cc=linux-aspeed@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.