From: neil.armstrong@linaro.org
To: hfdevel@gmx.net, khilman@baylibre.com, jbrunet@baylibre.com,
martin.blumenstingl@googlemail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] correct uart_B and uart_C clock references for meson8b
Date: Thu, 6 Apr 2023 17:28:54 +0200 [thread overview]
Message-ID: <00165b3e-42e4-7be6-bd80-9f0bd26c78e2@linaro.org> (raw)
In-Reply-To: <trinity-3aa9784a-714a-47cd-866b-3ae77ecca0fb-1680773596235@3c-app-gmx-bap56>
Hi,
On 06/04/2023 11:33, hfdevel@gmx.net wrote:
> commit b3b6a88d2347d2ec9075603920e616836cb46750
> Author: Hans-Frieder Vogt <hfdevel@gmx.net>
> Date: Thu Apr 6 10:21:49 2023 +0200
>
> [PATCH] correct uart_B and uart_C clock references for meson8b
The subject is wrong, should be: "ARM: dts: meson8b: " and you should also CC the linux-amlogic & linux-arm-kernel MLs likes get_maintainers indicates.
Neil
>
> with the current device tree for meson8b, uarts B (e.g. available on pins 8/10 on Odroid-C1) and C (pins 3/5 on Odroid-C1) do not work, because they are relying on incorrect clocks.
> This trivial patch changes the references of pclk to the correct CLKID, which allows to use the two uarts.
>
> Signed-off-by: Hans-Frieder Vogt <hfdevel@gmx.net>
> ---
> meson8b.dtsi | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/boot/dts/meson8b.dtsi b/arch/arm/boot/dts/meson8b.dtsi
> index d5a3fe21e8e7..25f7c985f9ea 100644
> --- a/arch/arm/boot/dts/meson8b.dtsi
> +++ b/arch/arm/boot/dts/meson8b.dtsi
> @@ -740,13 +740,13 @@ &uart_A {
>
> &uart_B {
> compatible = "amlogic,meson8b-uart";
> - clocks = <&xtal>, <&clkc CLKID_UART0>, <&clkc CLKID_CLK81>;
> + clocks = <&xtal>, <&clkc CLKID_UART1>, <&clkc CLKID_CLK81>;
> clock-names = "xtal", "pclk", "baud";
> };
>
> &uart_C {
> compatible = "amlogic,meson8b-uart";
> - clocks = <&xtal>, <&clkc CLKID_UART0>, <&clkc CLKID_CLK81>;
> + clocks = <&xtal>, <&clkc CLKID_UART2>, <&clkc CLKID_CLK81>;
> clock-names = "xtal", "pclk", "baud";
> };
>
next prev parent reply other threads:[~2023-04-06 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 9:33 hfdevel
2023-04-06 15:28 ` neil.armstrong [this message]
2023-04-06 19:08 ` Martin Blumenstingl
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=00165b3e-42e4-7be6-bd80-9f0bd26c78e2@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=hfdevel@gmx.net \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--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®