From: Al Cooper <alcooperx@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Al Cooper <alcooperx@gmail.com>,
bcm-kernel-feedback-list@broadcom.com,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
linux-serial@vger.kernel.org
Subject: [-next] serial: 8250: Match legacy NS16550A UARTs
Date: Wed, 14 Apr 2021 09:45:39 -0400 [thread overview]
Message-ID: <20210414134539.42332-1-alcooperx@gmail.com> (raw)
From: Florian Fainelli <f.fainelli@gmail.com>
Older 32-bit only Broadcom STB chips used a NS16550A compatible UART,
the 8250_bcm7271.c driver can drive those UARTs just fine provided that
we let it match the appropriate compatible string.
Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
Reviewed-by: Al Cooper <alcooperx@gmail.com>
---
drivers/tty/serial/8250/8250_bcm7271.c | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/drivers/tty/serial/8250/8250_bcm7271.c b/drivers/tty/serial/8250/8250_bcm7271.c
index 725a450058f8..023a2de8b2d6 100644
--- a/drivers/tty/serial/8250/8250_bcm7271.c
+++ b/drivers/tty/serial/8250/8250_bcm7271.c
@@ -204,6 +204,13 @@ static const u32 brcmstb_rate_table_7278[] = {
MHZ(48),
};
+static const u32 brcmstb_rate_table_16550a[] = {
+ MHZ(81),
+ 0,
+ 0,
+ 0,
+};
+
struct brcmuart_priv {
int line;
struct clk *baud_mux_clk;
@@ -865,6 +872,10 @@ static const struct of_device_id brcmuart_dt_ids[] = {
.compatible = "brcm,bcm7271-uart",
.data = brcmstb_rate_table,
},
+ {
+ .compatible = "ns16550a",
+ .data = brcmstb_rate_table_16550a,
+ },
{},
};
--
2.17.1
next reply other threads:[~2021-04-14 13:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 13:45 Al Cooper [this message]
2021-04-15 8:11 ` [-next] serial: 8250: Match legacy NS16550A UARTs Greg Kroah-Hartman
2021-04-15 10:44 ` Andy Shevchenko
2021-04-21 19:04 ` Alan Cooper
2021-04-21 19:57 ` Andy Shevchenko
2021-04-21 20:00 ` Florian Fainelli
2021-04-21 20:12 ` Andy Shevchenko
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=20210414134539.42332-1-alcooperx@gmail.com \
--to=alcooperx@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.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).