From: "sudheer.v" <open.sudheer@gmail.com>
To: gregkh@linuxfoundation.org, jslaby@suse.com, joel@jms.id.au,
andrew@aj.id.au, benh@kernel.crashing.org, robh+dt@kernel.org,
mark.rutland@arm.com,
shivahshankar.shankarnarayanrao@aspeedtech.com,
shivahshankar@gmail.com, sudheer.veliseti@aspeedtech.com
Cc: sudheer veliseti <sudheer.open@gmail.com>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
devicetree@vger.kernel.org, linux-aspeed@lists.ozlabs.org
Subject: [patch v3 0/5] *** DMA based UART driver for AST2500 ***
Date: Tue, 25 Jun 2019 16:14:31 +0530 [thread overview]
Message-ID: <1561459476-14268-1-git-send-email-open.sudheer@gmail.com> (raw)
From: sudheer veliseti <sudheer.open@gmail.com>
Hi,
AST2500 has dedicated Uart DMA controller which has 12 sets of
Tx and RX channels connected to UART controller directly.
Since the DMA controller have dedicated buffers and registers,
there would be little benifit in adding DMA framework overhead.
So the software for DMA controller is included within the UART driver itself.
Thanks and Regards
Sudheer.V
changes in v3:
- custom debugs replaced with pr_debug in 8250_ast2500_uart_dma.c
- change logs added in patches
sudheer veliseti (5):
AST2500 DMA UART driver
build configuration for AST2500 DMA UART driver
DT nodes for AST2500 DMA UART driver
defconfig and MAINTAINERS updated for AST2500 DMA UART driver
Documentation: DT bindings AST2500 DMA UART driver
.../bindings/serial/ast2500-dma-uart.txt | 40 +
MAINTAINERS | 13 +
arch/arm/boot/dts/aspeed-ast2500-evb.dts | 21 +
arch/arm/boot/dts/aspeed-g5.dtsi | 71 +-
arch/arm/configs/aspeed_g5_defconfig | 1 +
.../tty/serial/8250/8250_ast2500_uart_dma.c | 1879 +++++++++++++++++
drivers/tty/serial/8250/Kconfig | 35 +-
drivers/tty/serial/8250/Makefile | 1 +
8 files changed, 2056 insertions(+), 5 deletions(-)
create mode 100644 Documentation/devicetree/bindings/serial/ast2500-dma-uart.txt
create mode 100644 drivers/tty/serial/8250/8250_ast2500_uart_dma.c
--
2.17.1
next reply other threads:[~2019-06-25 10:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 10:44 sudheer.v [this message]
2019-06-25 10:44 ` [patch v3 1/5] AST2500 DMA UART driver sudheer.v
2019-07-03 17:49 ` Greg KH
2019-07-03 19:16 ` Joe Perches
2019-07-03 23:04 ` Benjamin Herrenschmidt
2019-06-25 10:44 ` [patch v3 2/5] build configuration for " sudheer.v
2019-07-03 17:50 ` Greg KH
2019-06-25 10:44 ` [patch v3 3/5] DT nodes " sudheer.v
2019-07-03 17:50 ` Greg KH
2019-06-25 10:44 ` [patch v3 4/5] defconfig and MAINTAINERS updated " sudheer.v
2019-07-03 17:51 ` Greg KH
2019-06-25 10:44 ` [patch v3 5/5] Documentation: DT bindings " sudheer.v
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=1561459476-14268-1-git-send-email-open.sudheer@gmail.com \
--to=open.sudheer@gmail.com \
--cc=andrew@aj.id.au \
--cc=benh@kernel.crashing.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=joel@jms.id.au \
--cc=jslaby@suse.com \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=shivahshankar.shankarnarayanrao@aspeedtech.com \
--cc=shivahshankar@gmail.com \
--cc=sudheer.open@gmail.com \
--cc=sudheer.veliseti@aspeedtech.com \
/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;
as well as URLs for NNTP newsgroup(s).