From: Max Filippov <jcmvbkbc@gmail.com>
To: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
devicetree@vger.kernel.org
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jiri Slaby" <jirislaby@kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Max Filippov" <jcmvbkbc@gmail.com>
Subject: [PATCH v4 0/5] serial: add drivers for the ESP32xx serial devices
Date: Thu, 28 Sep 2023 08:16:26 -0700 [thread overview]
Message-ID: <20230928151631.149333-1-jcmvbkbc@gmail.com> (raw)
Hello,
this series adds drivers for the UART and ACM controllers found in the
Espressif ESP32 and ESP32S3 SoCs.
Changes v3->v4:
- address review comments, listed in each patch
- add reviewed-by tags
Changes v2->v3:
- address review comments, listed in each patch
Changes v1->v2:
- address review comments, listed in each patch
- add cleanup for the uart_get_baud_rate function
Max Filippov (5):
serial: core: tidy invalid baudrate handling in uart_get_baud_rate
dt-bindings: serial: document esp32-uart
drivers/tty/serial: add driver for the ESP32 UART
dt-bindings: serial: document esp32s3-acm
drivers/tty/serial: add ESP32S3 ACM device driver
.../bindings/serial/esp,esp32-acm.yaml | 42 +
.../bindings/serial/esp,esp32-uart.yaml | 51 ++
drivers/tty/serial/Kconfig | 27 +
drivers/tty/serial/Makefile | 2 +
drivers/tty/serial/esp32_acm.c | 459 +++++++++++
drivers/tty/serial/esp32_uart.c | 741 ++++++++++++++++++
drivers/tty/serial/serial_core.c | 4 +-
include/uapi/linux/serial_core.h | 6 +
8 files changed, 1329 insertions(+), 3 deletions(-)
create mode 100644 Documentation/devicetree/bindings/serial/esp,esp32-acm.yaml
create mode 100644 Documentation/devicetree/bindings/serial/esp,esp32-uart.yaml
create mode 100644 drivers/tty/serial/esp32_acm.c
create mode 100644 drivers/tty/serial/esp32_uart.c
--
2.30.2
next reply other threads:[~2023-09-28 15:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 15:16 Max Filippov [this message]
2023-09-28 15:16 ` [PATCH v4 1/5] serial: core: tidy invalid baudrate handling in uart_get_baud_rate Max Filippov
2023-09-29 6:34 ` Ilpo Järvinen
2023-09-29 19:26 ` Max Filippov
2023-10-03 12:39 ` Greg Kroah-Hartman
2023-09-28 15:16 ` [PATCH v4 2/5] dt-bindings: serial: document esp32-uart Max Filippov
2023-09-28 15:16 ` [PATCH v4 3/5] drivers/tty/serial: add driver for the ESP32 UART Max Filippov
2023-10-03 12:56 ` Greg Kroah-Hartman
2023-09-28 15:16 ` [PATCH v4 4/5] dt-bindings: serial: document esp32s3-acm Max Filippov
2023-09-28 15:16 ` [PATCH v4 5/5] drivers/tty/serial: add ESP32S3 ACM device driver Max Filippov
2023-10-03 12:55 ` Greg Kroah-Hartman
2023-10-03 19:46 ` Max Filippov
2023-10-05 18:57 ` Greg Kroah-Hartman
2023-10-05 21:21 ` Max Filippov
2023-10-06 9:34 ` Greg Kroah-Hartman
2023-10-06 10:27 ` Max Filippov
2023-10-06 11:04 ` Greg Kroah-Hartman
2023-10-06 14:11 ` Rob Herring
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=20230928151631.149333-1-jcmvbkbc@gmail.com \
--to=jcmvbkbc@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).