From: neil.armstrong@linaro.org
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-amlogic@lists.infradead.org
Cc: devicetree@vger.kernel.org, khilman@baylibre.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, jbrunet@baylibre.com
Subject: Re: [PATCH 0/7] dts: amlogic: enable UART RX and TX pull up by default
Date: Mon, 31 Mar 2025 08:42:04 +0200 [thread overview]
Message-ID: <04c47466-b1a3-4eb2-8f28-95faa29ff45f@linaro.org> (raw)
In-Reply-To: <20250329185855.854186-1-martin.blumenstingl@googlemail.com>
On 29/03/2025 19:58, Martin Blumenstingl wrote:
> On the LibreELEC forum there have been reports that Odroid-C2 does not
> boot when UART is left disconnected [0]. It turns out that this can be
> solved by enabling the SoCs pull-up resistor on the UART RX and TX
> pads [1].
> It's not clear whether that specific Odroid-C2 board has a broken
> resistor, the resistor is not populated (either by accident or on
> purpose) or if there's another reason.
>
> Testing on an SM1 X96-Air shows that pull-ups being enabled on UART
> RX and TX is actually the default (either set in vendor u-boot or an
> actual hardware default).
>
> This series enables the UART RX and TX pull up resistors in the
> default pin configuration on all supported SoCs.
>
> Testing has been done on:
> - GXBB Odroid-C1 on u-boot by a user in the LibreELEC forums [2]
> - Meson8b Odroid-C1 on Linux (with vendor u-boot)
> - SM1 X96-Air on Linux (with vendor u-boot)
>
> Please include this early so the various CI systems can test these
> patches.
>
>
> [0] https://forum.libreelec.tv/thread/28586-odroid-c2-gxbb-s905-and-le-11-06-or-12-does-not-boot/?postID=195481#post195481
> [1] https://forum.libreelec.tv/thread/28586-odroid-c2-gxbb-s905-and-le-11-06-or-12-does-not-boot/?postID=195667#post195667
> [2] https://forum.libreelec.tv/thread/28586-odroid-c2-gxbb-s905-and-le-11-06-or-12-does-not-boot/?postID=195674#post195674
>
>
> Martin Blumenstingl (7):
> ARM: dts: amlogic: meson8: enable UART RX and TX pull up by default
> ARM: dts: amlogic: meson8b: enable UART RX and TX pull up by default
> arm64: dts: amlogic: gxbb: enable UART RX and TX pull up by default
> arm64: dts: amlogic: gxl: enable UART RX and TX pull up by default
> arm64: dts: amlogic: g12: enable UART RX and TX pull up by default
> arm64: dts: amlogic: axg: enable UART RX and TX pull up by default
> arm64: dts: amlogic: a1: enable UART RX and TX pull up by default
>
> arch/arm/boot/dts/amlogic/meson8.dtsi | 4 ++--
> arch/arm/boot/dts/amlogic/meson8b.dtsi | 4 ++--
> arch/arm64/boot/dts/amlogic/meson-a1.dtsi | 1 +
> arch/arm64/boot/dts/amlogic/meson-axg.dtsi | 12 ++++++------
> arch/arm64/boot/dts/amlogic/meson-g12-common.dtsi | 10 +++++-----
> arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 10 +++++-----
> arch/arm64/boot/dts/amlogic/meson-gxl.dtsi | 12 ++++++------
> 7 files changed, 27 insertions(+), 26 deletions(-)
>
Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
I'll apply them now so they can be tested on -next for this whole cycle.
Thanks,
Neil
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2025-03-31 6:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-29 18:58 Martin Blumenstingl
2025-03-29 18:58 ` [PATCH 1/7] ARM: dts: amlogic: meson8: " Martin Blumenstingl
2025-03-29 18:58 ` [PATCH 2/7] ARM: dts: amlogic: meson8b: " Martin Blumenstingl
2025-03-29 18:58 ` [PATCH 3/7] arm64: dts: amlogic: gxbb: " Martin Blumenstingl
2025-03-29 18:58 ` [PATCH 4/7] arm64: dts: amlogic: gxl: " Martin Blumenstingl
2025-03-29 18:58 ` [PATCH 5/7] arm64: dts: amlogic: g12: " Martin Blumenstingl
2025-03-29 18:58 ` [PATCH 6/7] arm64: dts: amlogic: axg: " Martin Blumenstingl
2025-03-29 18:58 ` [PATCH 7/7] arm64: dts: amlogic: a1: " Martin Blumenstingl
2025-03-31 6:42 ` neil.armstrong [this message]
2025-03-31 7:01 ` [PATCH 0/7] dts: amlogic: " 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=04c47466-b1a3-4eb2-8f28-95faa29ff45f@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=devicetree@vger.kernel.org \
--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®