From: Bich HEMON <bich.hemon@st.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre TORGUE <alexandre.torgue@st.com>,
"Jiri Slaby" <jslaby@suse.com>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 00/20] Update STM32 usart driver
Date: Mon, 26 Jun 2017 15:50:56 +0000 [thread overview]
Message-ID: <24d52731f9974710a29dbd5151377bd7@SFHDAG3NODE1.st.com> (raw)
Dear all,
Please, do not take into account this patchset. A newer version is currently being prepared with typo/format corrections and will be sent later. The previous version has to be abandoned.
Sorry for the inconvenience,
Bich HEMON
-----Original Message-----
From: Bich HEMON
Sent: lundi 26 juin 2017 14:49
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>; Rob Herring <robh+dt@kernel.org>; Mark Rutland <mark.rutland@arm.com>; Maxime Coquelin <mcoquelin.stm32@gmail.com>; Alexandre TORGUE <alexandre.torgue@st.com>; Jiri Slaby <jslaby@suse.com>; linux-serial@vger.kernel.org; devicetree@vger.kernel.org; linux-arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org
Cc: Bich HEMON <bich.hemon@st.com>
Subject: [PATCH 00/20] Update STM32 usart driver
From: Bich Hemon <bich.hemon@st.com>
This patchset updates the stm32 usart driver. It mainly adds support for fifo, dma, debugfs anf fixes various bugs.
Bich Hemon (20):
serial: stm32: adding fifo support
dt-bindings: serial: each stm32 usart needs an alias
serial: stm32: fix multi ports management
serial: stm32: make fifoen as property for each port
serial: stm32: add debugfs
serial: stm32: fix pio transmit timeout
serial: stm32: less messages on dma alloc error
serial: stm32: timeout interrupt using with dma
serial: stm32: fix end of transfer
serial: stm32: fix dma receive
serial: stm32: add RTS support
serial: stm32: fix last_res value
serial: stm32: fix error handling in probe
dt-bindings: serial: document option wake-up interrupt for STM32 USART
serial: stm32: Add wakeup mechanism
serial: stm32: fix fifo usage
dt-bindings: serial: stm32: add dma using note
serial: stm32: update dma buffers length
serial: stm32: add dma rx callback
serial: stm32: fix rx interrupt handling in startup
.../devicetree/bindings/serial/st,stm32-usart.txt | 55 +++-
drivers/tty/serial/stm32-usart.c | 310 ++++++++++++++++++---
drivers/tty/serial/stm32-usart.h | 51 +++-
3 files changed, 375 insertions(+), 41 deletions(-)
--
1.9.1
next reply other threads:[~2017-06-26 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 15:50 Bich HEMON [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-06-26 12:49 Bich HEMON
2017-06-29 15:09 ` Alexandre Torgue
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=24d52731f9974710a29dbd5151377bd7@SFHDAG3NODE1.st.com \
--to=bich.hemon@st.com \
--cc=alexandre.torgue@st.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh+dt@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
all inboxes | Powered by JetHome®