From: Chia-Wei Wang <chiawei_wang@aspeedtech.com>
To: <vkoul@kernel.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <joel@jms.id.au>,
<andrew@aj.id.au>, <gregkh@linuxfoundation.org>,
<jirislaby@kernel.org>, <pmenzel@molgen.mpg.de>,
<ilpo.jarvinen@linux.intel.com>, <dmaengine@vger.kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-aspeed@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>,
<linux-serial@vger.kernel.org>, <openbmc@lists.ozlabs.org>
Subject: [PATCH v2 0/5] arm: aspeed: Add UART DMA support
Date: Tue, 14 Mar 2023 10:18:12 +0800 [thread overview]
Message-ID: <20230314021817.30446-1-chiawei_wang@aspeedtech.com> (raw)
This patch serias adds the 8250 driver with DMA support for AST26xx UART devices
v2 change:
- re-write UDMA driver based on the DMAEngine framework
- re-write 8250_aspeed driver with DMA support based on the 8250_dma implementation
- remove virtual UART part as there is already a 8250_aspeed_vuart driver
Chia-Wei Wang (5):
dt-bindings: serial: 8250: Add aspeed,ast2600-uart
dt-bindings: dmaengine: Add AST2600 UDMA bindings
dmaengine: aspeed: Add AST2600 UART DMA driver
serial: 8250: Add AST2600 UART driver
ARM: dts: aspeed-g6: Add UDMA node
.../bindings/dma/aspeed,ast2600-udma.yaml | 56 ++
.../devicetree/bindings/serial/8250.yaml | 1 +
arch/arm/boot/dts/aspeed-g6.dtsi | 9 +
drivers/dma/Kconfig | 9 +
drivers/dma/Makefile | 1 +
drivers/dma/ast2600-udma.c | 528 ++++++++++++++++++
drivers/tty/serial/8250/8250_aspeed.c | 224 ++++++++
drivers/tty/serial/8250/Kconfig | 8 +
drivers/tty/serial/8250/Makefile | 1 +
include/dt-bindings/dma/ast2600-udma.h | 40 ++
10 files changed, 877 insertions(+)
create mode 100644 Documentation/devicetree/bindings/dma/aspeed,ast2600-udma.yaml
create mode 100644 drivers/dma/ast2600-udma.c
create mode 100644 drivers/tty/serial/8250/8250_aspeed.c
create mode 100644 include/dt-bindings/dma/ast2600-udma.h
--
2.25.1
next reply other threads:[~2023-03-14 2:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 2:18 Chia-Wei Wang [this message]
2023-03-14 2:18 ` [PATCH v2 1/5] dt-bindings: serial: 8250: Add aspeed,ast2600-uart Chia-Wei Wang
2023-03-17 20:58 ` Rob Herring
2023-03-14 2:18 ` [PATCH v2 2/5] dt-bindings: dmaengine: Add AST2600 UDMA bindings Chia-Wei Wang
2023-03-17 21:05 ` Rob Herring
2023-03-20 2:56 ` ChiaWei Wang
2023-03-14 2:18 ` [PATCH v2 3/5] dmaengine: aspeed: Add AST2600 UART DMA driver Chia-Wei Wang
2023-03-17 21:00 ` Rob Herring
2023-03-20 2:58 ` ChiaWei Wang
2023-03-14 2:18 ` [PATCH v2 4/5] serial: 8250: Add AST2600 UART driver Chia-Wei Wang
2023-03-14 2:18 ` [PATCH v2 5/5] ARM: dts: aspeed-g6: Add UDMA node Chia-Wei Wang
[not found] ` <20230318030113.2024-1-hdanton@sina.com>
2023-03-20 2:54 ` [PATCH v2 3/5] dmaengine: aspeed: Add AST2600 UART DMA driver ChiaWei Wang
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=20230314021817.30446-1-chiawei_wang@aspeedtech.com \
--to=chiawei_wang@aspeedtech.com \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=pmenzel@molgen.mpg.de \
--cc=robh+dt@kernel.org \
--cc=vkoul@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox