From: Neil Armstrong <narmstrong@baylibre.com>
To: gregkh@linuxfoundation.org,
Neil Armstrong <narmstrong@baylibre.com>,
jirislaby@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: (subset) [PATCH 0/3] tty: serial: meson: add amlogic, uart-fifosize property
Date: Tue, 1 Jun 2021 10:27:48 +0200 [thread overview]
Message-ID: <162253604769.258225.7812835099305638317.b4-ty@baylibre.com> (raw)
In-Reply-To: <20210518075833.3736038-1-narmstrong@baylibre.com>
Hi,
On Tue, 18 May 2021 09:58:30 +0200, Neil Armstrong wrote:
> On most of the Amlogic SoCs, the first UART controller in the "Everything-Else"
> power domain has 128bytes of RX & TX FIFO, so add an optional property to describe
> a different FIFO size from the other ports (64bytes).
>
> This adds a property in the bindings, reads the property from the driver and updates
> the DT with the new property.
>
> [...]
Thanks, Applied to https://git.kernel.org/pub/scm/linux/kernel/git/amlogic/linux.git (v5.14/dt64)
[3/3] arm64: dts: meson: set 128bytes FIFO size on uart A
https://git.kernel.org/amlogic/c/a270a2b24de5
--
Neil
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-06-01 8:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 7:58 [PATCH 0/3] tty: serial: meson: add amlogic,uart-fifosize property Neil Armstrong
2021-05-18 7:58 ` [PATCH 1/3] dt-bindings: serial: amlogic, meson-uart: add fifo-size property Neil Armstrong
2021-05-19 21:36 ` Rob Herring
2021-05-18 7:58 ` [PATCH 2/3] tty: serial: meson: retrieve port FIFO size from DT Neil Armstrong
2021-05-18 7:58 ` [PATCH 3/3] arm64: dts: meson: set 128bytes FIFO size on uart A Neil Armstrong
2021-05-20 13:55 ` [PATCH 0/3] tty: serial: meson: add amlogic,uart-fifosize property Neil Armstrong
2021-05-20 14:10 ` Greg KH
2021-05-20 16:02 ` Neil Armstrong
2021-06-01 8:27 ` Neil Armstrong [this message]
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=162253604769.258225.7812835099305638317.b4-ty@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--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 \
/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).