From: Yu Tu <yu.tu@amlogic.com>
To: <linux-serial@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-amlogic@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Neil Armstrong <narmstrong@baylibre.com>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Yu Tu <yu.tu@amlogic.com>
Subject: [PATCH V7 6/6] tty: serial: meson: Added S4 SOC compatibility
Date: Fri, 25 Feb 2022 15:39:22 +0800 [thread overview]
Message-ID: <20220225073922.3947-7-yu.tu@amlogic.com> (raw)
In-Reply-To: <20220225073922.3947-1-yu.tu@amlogic.com>
Make UART driver compatible with S4 SOC UART.
Signed-off-by: Yu Tu <yu.tu@amlogic.com>
---
drivers/tty/serial/meson_uart.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/tty/serial/meson_uart.c b/drivers/tty/serial/meson_uart.c
index d19349ead738..bf6be5468aaf 100644
--- a/drivers/tty/serial/meson_uart.c
+++ b/drivers/tty/serial/meson_uart.c
@@ -865,6 +865,10 @@ static const struct of_device_id meson_uart_dt_match[] = {
.compatible = "amlogic,meson-gx-uart",
.data = (void *)true,
},
+ {
+ .compatible = "amlogic,meson-s4-uart",
+ .data = (void *)true,
+ },
{ /* sentinel */ },
};
MODULE_DEVICE_TABLE(of, meson_uart_dt_match);
--
2.33.1
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2022-02-25 7:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 7:39 [PATCH V7 0/6] Use CCF to describe the UART baud rate clock Yu Tu
2022-02-25 7:39 ` [PATCH V7 1/6] tty: serial: meson: Move request the register region to probe Yu Tu
2022-02-25 7:39 ` [PATCH V7 2/6] tty: serial: meson: Use devm_ioremap_resource to get register mapped memory Yu Tu
2022-02-25 7:39 ` [PATCH V7 3/6] tty: serial: meson: Describes the calculation of the UART baud rate clock using a clock frame Yu Tu
2022-02-28 11:10 ` Jerome Brunet
2022-03-01 6:49 ` Yu Tu
2022-03-01 8:26 ` Jerome Brunet
2022-03-01 9:13 ` Yu Tu
2022-03-01 13:17 ` Marek Szyprowski
2022-03-01 21:04 ` Greg Kroah-Hartman
2022-02-25 7:39 ` [PATCH V7 4/6] tty: serial: meson: Make some bit of the REG5 register writable Yu Tu
2022-02-25 7:39 ` [PATCH V7 5/6] tty: serial: meson: The system stuck when you run the stty command on the console to change the baud rate Yu Tu
2022-02-28 10:58 ` Jerome Brunet
2022-03-01 5:44 ` Yu Tu
2022-02-25 7:39 ` Yu Tu [this message]
2022-02-28 10:59 ` [PATCH V7 0/6] Use CCF to describe the UART baud rate clock Jerome Brunet
2022-03-01 5:54 ` Yu Tu
2022-03-01 8:36 ` Jerome Brunet
2022-03-01 9:01 ` Yu Tu
2022-03-01 9:27 ` Neil Armstrong
2022-03-01 10:12 ` Yu Tu
2022-03-02 2:15 ` Yu Tu
2022-03-01 7:25 ` Neil Armstrong
2022-03-01 7:57 ` Yu Tu
2022-03-01 8:37 ` Neil Armstrong
2022-03-01 8:47 ` Yu Tu
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=20220225073922.3947-7-yu.tu@amlogic.com \
--to=yu.tu@amlogic.com \
--cc=gregkh@linuxfoundation.org \
--cc=jbrunet@baylibre.com \
--cc=jirislaby@kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.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