[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VfQetCJJZ_U70xEduVBQHEx_GkHeKBs2uzNtvcq9H0BqQ@mail.gmail.com>
Date: Thu, 15 Apr 2021 13:44:34 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Al Cooper <alcooperx@...il.com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Florian Fainelli <f.fainelli@...il.com>,
bcm-kernel-feedback-list <bcm-kernel-feedback-list@...adcom.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jiri Slaby <jirislaby@...nel.org>,
"open list:SERIAL DRIVERS" <linux-serial@...r.kernel.org>
Subject: Re: [-next] serial: 8250: Match legacy NS16550A UARTs
On Wed, Apr 14, 2021 at 7:13 PM Al Cooper <alcooperx@...il.com> wrote:
>
> From: Florian Fainelli <f.fainelli@...il.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.
This sounds not correct to me, ns16550a is a national semiconductor product.
Why is it here and not in generic 8250_of?
> + {
> + .compatible = "ns16550a",
> + .data = brcmstb_rate_table_16550a,
> + },
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists