From: Neil Armstrong <narmstrong@baylibre.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-amlogic@lists.infradead.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, jbrunet@baylibre.com,
khilman@baylibre.com
Subject: Re: [PATCH] ARM: dts: meson: Set the fifo-size of uart_A to 128 bytes
Date: Mon, 14 Jun 2021 09:56:01 +0200 [thread overview]
Message-ID: <0e3b8d5b-756b-fefe-fbd3-8a786d7344ac@baylibre.com> (raw)
In-Reply-To: <20210604170844.2201229-1-martin.blumenstingl@googlemail.com>
On 04/06/2021 19:08, Martin Blumenstingl wrote:
> The first UART controller in the "Everything-Else" power domain is
> called uart_A. Unlike all other UARTs (which use a 64 byte fifo-size in
> hardware) uart_A has a fifo-size of 128 bytes. This UART controller is
> typically used for Bluetooth HCI.
> The fifo-size of 128 bytes is valid from all SoCs from Meson6 (or
> possibly even earlier) all the way up to the latest 64-bit ones.
>
> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> ---
> arch/arm/boot/dts/meson.dtsi | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/boot/dts/meson.dtsi b/arch/arm/boot/dts/meson.dtsi
> index 8bae6ed0abb2..bd0e864964e9 100644
> --- a/arch/arm/boot/dts/meson.dtsi
> +++ b/arch/arm/boot/dts/meson.dtsi
> @@ -50,6 +50,7 @@ uart_A: serial@84c0 {
> compatible = "amlogic,meson6-uart", "amlogic,meson-uart";
> reg = <0x84c0 0x18>;
> interrupts = <GIC_SPI 26 IRQ_TYPE_EDGE_RISING>;
> + fifo-size = <128>;
> status = "disabled";
> };
>
>
Acked-by: Neil Armstrong <narmstrong@baylibre.com>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2021-06-14 7:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 17:08 Martin Blumenstingl
2021-06-14 7:56 ` Neil Armstrong [this message]
2021-06-14 8:01 ` Neil Armstrong
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=0e3b8d5b-756b-fefe-fbd3-8a786d7344ac@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.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
all inboxes | Powered by JetHome®