From: Kevin Hilman <khilman@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: gregkh@linuxfoundation.org, Helmut Klein <hgkr.klein@gmail.com>,
linux-serial@vger.kernel.org, linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v5 3/4] ARM64: dts: meson-gx: use stable UART bindings with correct gate clock
Date: Fri, 16 Jun 2017 13:57:51 -0700 [thread overview]
Message-ID: <m2vanvejlc.fsf@baylibre.com> (raw)
In-Reply-To: <1497428957-19942-4-git-send-email-narmstrong@baylibre.com> (Neil Armstrong's message of "Wed, 14 Jun 2017 10:29:16 +0200")
Neil Armstrong <narmstrong@baylibre.com> writes:
> From: Helmut Klein <hgkr.klein@gmail.com>
>
> This patch switches to the stable UART bindings but also add the correct
> gate clock to the non-AO UART nodes for GXBB and GXL SoCs.
>
> Acked-by: Jerome Brunet <jbrunet@baylibre.com>
> Signed-off-by: Helmut Klein <hgkr.klein@gmail.com>
> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
> ---
> arch/arm64/boot/dts/amlogic/meson-gx.dtsi | 12 +++++-------
> arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 25 +++++++++++++++++++++++++
> arch/arm64/boot/dts/amlogic/meson-gxl.dtsi | 25 +++++++++++++++++++++++++
> 3 files changed, 55 insertions(+), 7 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/amlogic/meson-gx.dtsi b/arch/arm64/boot/dts/amlogic/meson-gx.dtsi
> index 603491d..86a4018 100644
> --- a/arch/arm64/boot/dts/amlogic/meson-gx.dtsi
> +++ b/arch/arm64/boot/dts/amlogic/meson-gx.dtsi
> @@ -225,7 +225,7 @@
> };
>
> uart_A: serial@84c0 {
> - compatible = "amlogic,meson-uart";
> + compatible = "amlogic,meson-gx-uart";
IMO, we should keep both compatibles (the more specific one first.)
That would allow new DTs to continue to run on older kernels.
It would also allow this DT change to be completely independent of the
driver changes. Otherwise, if I merge this before the driver change are
merged, we'll have a bunch of boards with no more serial console output.
Kevin
next prev parent reply other threads:[~2017-06-16 20:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 8:29 [PATCH v5 0/4] tty/serial: meson_uart: add support for core clock handling Neil Armstrong
2017-06-14 8:29 ` [PATCH v5 3/4] ARM64: dts: meson-gx: use stable UART bindings with correct gate clock Neil Armstrong
2017-06-16 20:57 ` Kevin Hilman [this message]
2017-06-19 8:40 ` Neil Armstrong
[not found] ` <1497428957-19942-1-git-send-email-narmstrong-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
2017-06-14 8:29 ` [PATCH v5 1/4] dt-bindings: serial: Add bindings for the Amlogic Meson UARTs Neil Armstrong
2017-06-18 14:05 ` Rob Herring
2017-06-14 8:29 ` [PATCH v5 4/4] ARM: dts: meson6: use stable UART bindings Neil Armstrong
2017-06-19 8:43 ` [PATCH v5 0/4] tty/serial: meson_uart: add support for core clock handling Neil Armstrong
[not found] ` <f4179b26-54fc-30ee-2d8d-7659349ccb74-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
2017-06-20 2:51 ` Greg KH
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=m2vanvejlc.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hgkr.klein@gmail.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=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;
as well as URLs for NNTP newsgroup(s).